Preservation

From UA Libraries Digital Services Planning and Documentation
Revision as of 11:13, 25 May 2009 by Jlderidder (Talk | contribs)

Jump to: navigation, search

Preservation Plan for Digital Materials

University of Alabama Libraries Digital Services

2009

Division of Digital Content

  1. Content digitized within Digital Services for archival purposes, and for which we have digital rights management permissions and documented access permissions, will receive, to the best of our ability, the highest levels of support for long-term access: Level I support. All such content must be created in formats and with methods supporting the current archival standards.
  2. Content which has not been digitized in currently supported archival formats, but for which The University of Alabama Libraries has committed access support, and for which we have digital rights permissions and documented access permissions, will receive, to the best of our ability, Level II support.
  3. Content for which The University of Alabama Libraries has not committed access support, but which is currently managed by Digital Services, and for which we have digital rights permissions, will receive, to the best of our ability, Level III support.
  4. Content for which The University of Alabama Libraries has no digital rights permissions will not receive support.

Levels of Support

  1. Level I Support
    1. Digital content will be named according to our file naming scheme and organized according to our file storage scheme on our storage server.
    2. Descriptive, administrative, and provenance metadata will be stored in current schemas and formats in the file system as specified.
    3. Technical metadata will be extracted from archival files and formatted for storage into appropriate schemas (local profiles are currently under development, drawing from standards such as MIX for images, TextMD for text, AudioMD for audio).
    4. Open-source software which renders the current archival format will be stored with the content.
    5. A copy of an open-source operating system which supports the open-source software will be stored with the content.
    6. File system information which enables emulation of the operating system to support the file system will be stored with the content.
    7. The storage system is covered by a weekly full backup and daily differential backups. The weekly full backup is duplicated, and a copy is sent offsite, with at least a two-month rolling backup schedule.
    8. MD5 checksum scripts will run before each tape backup to verify content is not corrupt, and will notify the repository administrator of any errors. Backup copies of current checksums are stored on a separate server, and scripts on a third separate server verify checking scripts run as scheduled and without error.
    9. We are and will continue to be involved in LOCKSS or a similar preservation network, supporting at least 7 copies of the archival content across a geographically disbursed area. All archival content will be made available to this system.
    10. Formats of archival files and versions of metadata will be stored on the top layer of the file system, in a flat text file exported regularly from the database where all entries to the storage system are entered and monitored regularly for format or metadata migration requirements.
    11. Prior to obsolescence, all archival formats will be migrated to the appropriate currently supported archival formats. All such migrations will be recorded, and the original format retained.
  2. Level II Support
    1. Digital content will be named according to our file naming scheme and organized according to our file storage scheme (see attached) on our storage server. This storage area will be separate from the one containing Level I support content.
    2. Descriptive, administrative, and provenance metadata will be stored in current schemas and formats in the file system as specified.
    3. The storage system is covered by a weekly full backup and daily differential backups. The weekly full backup is duplicated, and a copy is sent offsite, with at least a two-month rolling backup schedule.
    4. MD5 checksum scripts will run before each tape backup to verify content is not corrupt, and will notify the repository administrator of any errors. Backup copies of current checksums are stored on a separate server, and scripts on a third separate server verify checking scripts run as scheduled and without error.
    5. Formats of files and versions of metadata will be stored in a database where all entries to the storage system are entered and monitored regularly for format or metadata obsolescence risks.
    6. If funding, staffing, and viable migration methods become available, formats will be migrated to currently supported formats for online delivery prior to obsolescence.
    7. When a format has been determined to be obsolete, the online access will end, and stored content and metadata will be deleted.
    8. The definition of obsolescence used in this statement is that in which the approved computer systems and software on the University of Alabama Library computers can no longer render viable access to the content in the file without emulation services.
  3. Level III Support
    1. Digital content will be named according to our file naming scheme and organized according to our current working area storage requirements; content will not be stored on the storage server.
    2. Descriptive, administrative, and provenance metadata will be stored with the content while it resides on our servers, organized according to our current working area storage requirements.
    3. The working area system is covered by a weekly full backup and differential backups at least twice a week.
    4. After digital services requested have been rendered, content will be retained for 6 months, and then deleted.

Our current preservation Network is [The Alabama Digital Preservation Network]

Personal tools