From Confusion and Chaos to Clarity and Hope: Reorganization of Work Flows, Processes, and Delivery for Digital Libraries

The following chapter excerpt is from the third section of Digitization in the Real World; "The Digital Campus: Digitization in Universities and Their Libraries." Download the entire chapter for free (PDF)   or purchase online at Amazon.com.

View the collections here.

Author

Jody L. DeRidder (The University of Alabama Libraries)

Abstract

Digitization support within an institution may be fractured across several departments, only partially funded, and may suffer restraints imposed by delivery software which seriously hamper progress. Most digitization is undertaken with little thought for the future; the result is digital file chaos and confusion. Without clarification of file identities and relationships, preservation and migration to new systems are seriously hampered. Additionally, low funding for archival staff may preclude the creation of valuable item-level metadata. The University of Alabama Libraries leveraged the expertise available across the library to build a cross-departmental collaboration with which to face our challenges, recognizing that obstacles become opportunities for creative solutions. We are involved in a series of pilot projects to explore how to address the gap in archivist staffing to create item-level metadata. This chapter shares our discoveries and solutions.

Introduction

The first few years of most digital library initiatives are marked by 'boutique' collection development, in which the standards, organization, methodology, metadata, file names, and consistency vary considerably. At the time of my arrival at the University of Alabama in mid-2008 as head of the new Digital Services department, over thirty such digitization projects had been completed. Each collection had its own file-naming system and metadata fields, with inconsistencies throughout; nothing was standardized. Metadata in the delivery software did not retain in any predictable fashion a reference to the related archival files, and could not be exported in full. Digital Services staffing was minimal, requiring time from the Cataloging and Metadata Services for subject headings and upload, from archival staff for preparation of content and descriptions, and from Web Services to manage the interface and software support.

The scope of the task ahead was to expand heavily on the scanning staff and equipment, develop a feasible set of systematic work flows for supporting a large increase in scanning, build a cross-departmental team capable of supporting digital library development, and to create an organized and reusable set of digital content that is not dependent upon resident knowledge for continuation or restoration. Challenges included a simultaneous reduction in archivist work hours, minimal space for expansion, difficult relations between some departments, and insufficient time available from Web Services.

As in many smaller organizations, our digitization effort is tremendously dependent upon cross-departmental collaboration. Programming assistance and web delivery, metadata services, archivist expertise and a regular influx of well-chosen content are all critical to the development of our online research collections. A previous gift from EBSCO Industries to the libraries supports digitization and the development of technical infrastructure, but it does not support the processing, arranging, and description of archival collections. Our need for content creates a demand on the archivists that they simply do not have the resources to meet.

Recognizing the need for improved cross-departmental communications and teamwork, our dean (L. A. Pitschmann, personal communication, August 25, 2008) called together lead representatives (including two associate deans) from Library Technology, Web Services, Collection Development, Cataloging and Metadata Services, Special Collections and Archives, and Digital Services, to form an ongoing Digital Programs group which would meet regularly to hash out problems, develop alternatives, research opportunities and assign priorities. The creation of this group was a stroke of brilliance. By forming this framework for participation, setting forth a strategic goal and providing clear administrative support, our dean laid the groundwork for success. Given our multiple operational and relational challenges, we could only succeed by seeking solutions with the assistance of all impacted parties.

Against this backdrop we are working through four major problems: digital file chaos, the inability to reunite metadata with the archival content, software restrictions on the number of collections, and a lack of archivist time to create item-level metadata.

Download the entire chapter for free (PDF)  or purchase online at Amazon.com.

References

Boyko, A., Kunze, J., Littman, J., Madden, L. & Vargas, B. (2009). The BagIt file packaging format (V0.96). Retrieved November 14, 2009, from http://www.cdlib.org/inside/diglib/bagit/ bagitspec.html

California Digital Library. (2009). Online Archive of California (OAC). Retrieved November 15, 2009, from http://www.cdlib.org /inside/projects/oac/

Cheng, M., Taylor, M., Hegemann, R., Leidinger, A., Tominaga, T, Shibata, N., et al. (2009). The LAME project. Retrieved November 14, 2009, from http://lame.sourceforge.net/index.php

Conway, P. (2009). The image and the expert user: a qualitative investigation of decision-making. Paper presented at Archiving 2009, Arlington VA. In Archiving 2009, Vol. 6. (pp. 142-150). Society for Imaging Sciences and Technology.

DCMI. (2009). Dublin Core metadata initiative. Retrieved November 15, 2009, from http://dublincore.org/

Fogel, P. (2006). CDL 7train Profile – CONTENTdm simple and complex objects in METS Metadata encoding and transmission standard. Retrieved November 15, 2009, from http://www.loc.gov/standards/mets/profiles/00000010.html

Fogel, P. & Hetzner, E. (n.d.). 7train METS Generation Tool. Copyright the University of California Regents. Retrieved November 15, 2009, from http://seventrain.sourceforge.net/

Google. (2009). Tesseract-ocr. Retrieved November 14, 2009, from http://code.google.com/p/tesseract-ocr/

ImageMagick Studio LLC. (2009). ImageMagick. Retrieved November 14, 2009 from http://www.imagemagick.org/ script/index.php

Library of Congress. (2009a). EAD Encoded archival description (Version 2002). Retrieved November 14, 2009, from http://www.loc.gov/ead

Library of Congress. (2009b). METS Metadata encoding & transmission standard. Retrieved November 14, 2009, from http://www.loc.gov/standards/mets/

Library of Congress. (2009c). MODS metadata object description schema. Retrieved November 14, 2009, from http://www.loc.gov/ standards/mods/

LOCKSS. (2008). What is the LOCKSS program? Retrieved November 14, 2009, fromhttp://www.lockss.org/lockss/Home

Loewald, T. (2009a). Acumen. Retrieved November 15, 2009, from http://acumen.lib.ua.edu/

 Loewald, T. (2009b). Archivists utility. Retrieved November 15, 2009, from http://lb-416-003.lib.ua-net.ua.edu/notes/?f= Archivist%20Utility.txt

Network of Alabama Academic Libraries. (n.d.). Alabama Mosaic. Retrieved November 14, 2009, fromhttp://www.alabamamosaic.org/

Network of Alabama Academic Libraries. (2009). The Alabama Digital Preservation Network (ADPNet). Retrieved November 14, 2009, from http://www.adpn.org/

OCLC. (2009a). CONTENTdm Digital collection management software. Retrieved November 15, 2009, fromhttp://www.contentdm.com

OCLC. (2009b). FirstSearch Online reference. Retrieved November 15, 2009, from http://www.oclc.org/firstsearch/

OCLC. (2009c). Multi-site server. Retrieved November 15, 2009, from http://www.oclc.org/firstsearch/

University of Alabama Libraries. (2010a). Septimus D. Cabaniss Papers digitization project. Retrieved March 9, 2010 from http://www.lib.ua.edu/libraries/hoole/cabaniss

University of Alabama Libraries. (2010b). UA libraries digital services planning and documentation. Retrieved March 9, 2010 from http://www.lib.ua.edu/wiki/digcoll

W3C. (2005). XML:id Version 1.0. Retrieved November 15, 2009, from http://www.w3.org/TR/xml-id/