Show simple item record

dc.contributor.author Donaldson, Devan Ray
dc.contributor.author Conway, Paul
dc.coverage.temporal June 2009 en
dc.date.accessioned 2018-10-03T19:43:50Z
dc.date.available 2018-10-03T19:43:50Z
dc.date.issued 2010
dc.identifier.citation Donaldson, D. R., & Conway, P. (2010). Implementing PREMIS: a case study of the Florida Digital Archive. Library Hi Tech, 28(2), 273-289. en
dc.identifier.uri http://hdl.handle.net/2022/22463
dc.description.abstract Purpose – The purpose of this case study is to describe and interpret the PREservation Metadata: Implementation Strategies (PREMIS) implementation process, to gain more insight into why barriers to the adoption of PREMIS exist as well as how to overcome them. Design/methodology/approach – This qualitative case study analysis highlights the Florida Digital Archive as an exemplar of an organization in the throes of deciding just how to implement the PREMIS metadata model in a working repository system. Findings – Findings from this study suggest that use of PREMIS requires adaptation in which an organization must make changes in order to use PREMIS, and vice versa. Findings also suggest that there are clearly defined steps involved in the PREMIS implementation process, and that the nature of this process is iterative. Research limitations/implications – This study is limited by a short data collection period. It is also limited by investigating only one institution during its implementation process. Future studies could test the validity of the model proposed in this study and include multiple institutions. Practical implications – By providing context for the implementation process, this paper can help cultural heritage institutions interested in fully adopting PREMIS. Originality/value – Exploring PREMIS implementation using DOI/MIS literature is novel in the digital preservation community and is proposed as particularly useful to digital preservationists who are considering adopting PREMIS. The paper suggests that seemingly innocuous decisions by developers have real implications for preservation. en
dc.description.sponsorship Graduate Student Research Grant, Horace H. Rackham School of Graduate Studies, University of Michigan, Ann Arbor en
dc.language.iso en en
dc.publisher Library Hi Tech en
dc.relation.isversionof https://doi.org/10.1108/07378831011047677
dc.subject Preservation Metadata, PREMIS, Digital Preservation en
dc.title Implementing PREMIS: A Case Study of the Florida Digital Archive en
dc.type Preprint en
dc.description.methodology The research conducted on PREMIS implementation utilized the qualitative case study analysis method (Yin, 2003). The approach involves the investigation of a specific case, “with the intent of examining an issue with the case illustrating the complexity of an issue” (Creswell 2007, p. 93). Qualitative case study analysis also involves a bounded system, the use of multiple sources of information in data collection, and the creation of a detailed and contextualized picture of a particular issue (Creswell, 2007). As a case for study, the Florida Digital Archive is an exemplar of an organization in the throes of deciding just how to implement the PREMIS metadata model in a working system. The mission of the Florida Digital Archive is to provide a cost-effective, long-term preservation repository for digital materials in support of teaching and learning, scholarship, and research in the state of Florida. During the time this study was conducted, the FDA was fully engaged in the implementation process and attuned to the complexities of adapting the PREMIS metadata scheme. Previous studies have included FDA in the set of organizations implementing PREMIS, providing important background information for the case study (FCLA, 2006; Woodyard-Robinson, 2007; Fischer et al., 2008). The Florida Digital Archive is rich in technical expertise and human resources dedicated to PREMIS implementation, including four full-time programmers, a project manager, and a director who is in charge of implementing PREMIS. The FDA has unique expertise in PREMIS – given that the FDA’s Director served on the PREMIS Working Group and is a current member of the PREMIS Editorial Committee. The use of FDA as a case informally controls for some of the major known barriers to implementation, including the lack of technical expertise, resources, and knowledge of PREMIS (Alemneh, 2008), freeing the investigation to focus on decision-making strategies. This case study is bounded by time (two full weeks in residence during early June 2009) and place (at the Florida Digital Archive in Gainesville, Florida). Sources of information used in data collection include in-person semi-structured interviews, field observations, and prototype examples of specific implementation outcomes. The major advantage of field observations, carried out in tandem with interviews, is the opportunity to compare developers’ answers with observed behavior. In addition, conducting field observations in the midst of FDA decision-making allows for the assessment of the combination of observed behavior and answers to interview questions against Diffusion of Innovations (DOI) and Management and Information Systems (MIS) literature and models – in an effort to better understand the PREMIS implementation process in the context of the FDA. Interviews with the Director of the Florida Digital Archive established the parameters of the technical expertise marshaled for PREMIS implementation. Three of four systems developers assigned to PREMIS implementation were interviewed for the study. Even though four developers shared implementation responsibilities and exchanged information through implementation working group meetings, Developer A was generally recognized as serving in the lead because of his deeper knowledge regarding PREMIS implementation. Utilizing a full list of PREMIS entities and semantic units (see PREMIS Data Dictionary, Version 2.0), the first author conducted semi-structured interviews in which each of the three available developers was asked to indicate which semantic units the FDA used or did not use during implementation. Each developer was asked specifically about the nature of the PREMIS implementation process, with the question: “What is the process or steps involved when trying to implement PREMIS?” Developers were also explain what those challenges were and how they were addressed. Each developer was interviewed informally and separately in his or her office during normal business hours. en
dc.description.file 1 .pdf file; preprint en
dc.identifier.doi 10.1108/07378831011047677


Files in this item

This item appears in the following Collection(s)

Show simple item record

Search IUScholarWorks


Advanced Search

Browse

My Account

Statistics