Preservation

From UA Libraries Digital Services Planning and Documentation
(Difference between revisions)
Jump to: navigation, search
(Preservation Plan for Digital Materials)
(11 intermediate revisions by one user not shown)
Line 1: Line 1:
 +
==  University of Alabama Libraries Digital Services==
 +
 
===  Preservation Plan for Digital Materials ===
 
===  Preservation Plan for Digital Materials ===
 +
 +
The University of Alabama (UA) Libraries preserve selected digital content for long-term access support. Our highest level of attention and support is given to content selected for digitization from UA Libraries Special Collections. Other research materials are assigned preservation strategies at appropriate levels based on file formats and perceived needs of our designated audience, the faculty and students of the University of Alabama. 
 +
 +
The University of Alabama (UA) Libraries DigiPres group will determine the need to normalize or migrate files pending loss of access due to obsolescence. Decisions will be made on a cost/benefit basis with consideration for the needs of our stated audience.
  
 
[[HighLevelPolicies|High Level Policies]]
 
[[HighLevelPolicies|High Level Policies]]
  
===  University of Alabama Libraries Digital Services===
+
[[Security and Business Continuity Policies]]
==        2009 ==
+
 
 +
[[Recommendations for Authors and Creators]]
  
 
===Division of Digital Content===
 
===Division of Digital Content===
  
#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.  
+
#'''Level I support''' is for content digitized in formats and with methods supporting the current archival standards, and for which we have digital rights management permissions and documented access permission.  This is our most dedicated level of support.  It includes collection of technical and administrative metadata, bit-level preservation, and commitment to migrate content as formats change over the years.An example would be a manuscript collection digitized by Digital Services. 
#Content which may not have been digitized in currently supported archival formats, but for which The University of Alabama Libraries has committed long term 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.
+
#'''Level II support''' is for content which may not have been digitized in currently supported archival formats, but for which The University of Alabama Libraries has committed long term access support, and for which we have digital rights permissions and documented access permissions.  An example would be Electronic Theses and Dissertations.
#Content which may not have been digitized in currently supported archival formats, but for which The University of Alabama Libraries has committed short term access support, and for which we have digital rights permissions and documented access permissions, will receive, to the best of our ability, Level III support.
+
#'''Level III support''' is for content which needs to undergo regular change, and hence is not appropriate for inclusion in LOCKSS;  however, it is to our benefit to offer bit-level preservation for this content until it needs to change.  An example of this would be software necessary for either migration or emulation.  
#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 IV support.
+
#'''Level IV support''' is for content which may not have been digitized in currently supported archival formats, but for which The University of Alabama Libraries has committed short term access support, and for which we have digital rights permissions and documented access permissions.  An example would be Undergraduate Research Papers.  
#Content for which The University of Alabama Libraries has no digital rights permissions will not receive support.
+
#'''Level V support''' is for 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.  An example would be files digitized at the patron request.
  
===Levels of Support===
 
  
#'''Level I Support: archival formats & long term storage'''
+
 
##Digital content will be named according to our file naming scheme and organized according to our file storage scheme on our storage server.
+
{| class="wikitable" border="1" cellpadding="2" cellspacing="1"
##Descriptive, administrative, and provenance metadata will be stored in current schemas and formats in the file system as specified.  
+
|-
##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).
+
! Support Level
##Open-source software which renders the current archival format, if available, will be stored with the content.
+
! Example
##A copy of an open-source operating system which supports the open-source software, if available and feasible, will be stored with the content.
+
! Committed to sustain access
##File system information which enables emulation of the operating system to support the file system will be stored with the content.
+
! Migration Support
##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.
+
! Emulation Support
##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.
+
! Long Term Retention
##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.
+
! Bit-Level Preservation
##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.
+
! Annual Review
##Prior to obsolescence, all archival formats will be evaluated for preservation measures, which may involve either migration (reformatting) or emulation. All preservation measures taken will be recorded, and every effort will be made to continue accessibility.
+
! Local Backups
#'''Level II Support: non-archival formats & long term storage'''
+
|-
##Digital content will be named according to our file naming scheme and organized according to our file storage scheme on our storage server.
+
| Level I || Manuscript collection digitized by us || Yes || Yes || Yes || Yes || Yes || Yes || Yes
##Descriptive, administrative, and provenance metadata will be stored in current schemas and formats in the file system as specified.  
+
|-
##Technical metadata will be extracted from files and formatted for storage into appropriate schemas.
+
| Level II || Electronic Theses and Dissertations || Possibly || Possibly || Possibly ||Yes || Yes || Yes || Yes
##Open-source software which renders the current format, if available, will be stored with the content.
+
|-
##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.
+
| Level III || Open source software for rendering archival content || No ||  No || No || No || Yes || Yes || Yes
##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.  
+
|-
##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.
+
| Level IV || Undergraduate Research Papers || No ||  No || No || No || No || Yes || Yes
##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.
+
|-
##Prior to obsolescence, all content will be evaluated for preservation measures, which may involve either migration (reformatting) or emulation. Dependent upon their decisions and the availability of resources and viable migration/emulation methods, efforts will be made to continue accessibility. All preservation measures taken will be recorded.
+
| Level V || Material digitized at patron request ||No ||  No || No || No || No || No || Yes
##If continued accessibility is deemed infeasible or advised against, online access will end, and stored content and metadata will be deleted.  
+
|}
##The definition of obsolescence used in these statements 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.
+
 
#'''Level III Support: non-archival formats & short-term storage'''
+
===Committed to sustain access===
##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  and Level II support content. 
+
Every feasible effort will be made to continue access to this content.  This may involve migration to new formats, or development and maintenance of emulation methods.  This level of institutional commitment can only be made for content created in current archival format standards.
##Descriptive, administrative, and provenance metadata will be stored in current schemas and formats in the file system as specified.
+
Content not created in current archival standards is much likely to be migratable to new formats. However, if the content continues to be of value and either such migration is feasible and retains the significant properties of the content, or if emulation support is feasible, then continued access will be supported. 
##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.
+
 
##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.
+
=== Migration Support===
##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.
+
#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.
##Continued support of these materials will be reviewed annually. Dependent upon their recommendations, online access will either continue or will endWhen online access ends, stored content and metadata will be deleted.  
+
#Descriptive, administrative, and provenance metadata will be stored in current schemas and formats in the file system as specified.  
#'''Level IV Support: temporary storage'''
+
#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).
##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.
+
#Open-source software which renders the current archival format, if available, will be stored in the archive.  This will enable migration to newer file formats after the current ones become obsolete.
##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.
+
#A copy of an open-source operating system which supports the open-source software, if available and feasible, will be stored in the archive.
##The working area system is covered by a weekly full backup and differential backups at least twice a week. 
+
#Software and documentation necessary for emulation (recreation of the current user experience of our delivery system) will be stored in the archive.
##After digital services requested have been rendered, content will be retained for 6 months, and then deleted.
+
#File system information which enables emulation of the operating system to support the file system will be stored with the content.  
 +
 
 +
=== Emulation Support===
 +
#In addition to the migration support above, open-source software needed for creating derivatives and providing web delivery may be stored in the archive.
 +
#Documentation of current procedures for recreating the current online user experience may be stored in the archive.
 +
 
 +
=== Bit-Level Preservation===
 +
#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.  
 +
#We are and will continue to be involved in LOCKSS or a similar preservation network, supporting at least 6 copies of the archival content across a geographically disbursed area.  All archival content will be made available to this system.
 +
 
 +
=== Annual Review===
 +
#Prior to obsolescence, all content will be evaluated for preservation measures, which may involve either migration (reformatting) or emulation. Dependent upon their decisions and the availability of resources and viable migration/emulation methods, efforts will be made to continue accessibility. All preservation measures taken will be recorded.
 +
#If continued accessibility is deemed infeasible or advised against, online access will end, and stored content and metadata will be deleted.  
 +
#The definition of obsolescence used in these statements 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.
 +
 
 +
=== Long Term Retention===
 +
#Digital content will be named according to our file naming scheme and organized according to our file storage scheme on our storage server.  
 +
 
 +
=== Local Backups===
 +
#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.  
 +
 
 +
=== Descriptive Metadata ===
 +
# Up to 2 versions of descriptive metadata will be stored, the original and the most recent. Captures will be made quarterly from the delivery software web directoriesIf the metadata found there is more recent than what is stored, it will be placed in the archiveVersion 2 of each metadata file will be overwritten with each new capture.
 +
 
  
 
Our current preservation Network is [[http://www.adpn.org/  The Alabama Digital Preservation Network]]
 
Our current preservation Network is [[http://www.adpn.org/  The Alabama Digital Preservation Network]]
Line 57: Line 86:
 
* [[Formats]]
 
* [[Formats]]
 
* [[File Naming and Linking for LOCKSS]]
 
* [[File Naming and Linking for LOCKSS]]
 +
 +
[[User:Jlderidder|Jlderidder]]

Revision as of 13:35, 24 September 2012

Contents

University of Alabama Libraries Digital Services

Preservation Plan for Digital Materials

The University of Alabama (UA) Libraries preserve selected digital content for long-term access support. Our highest level of attention and support is given to content selected for digitization from UA Libraries Special Collections. Other research materials are assigned preservation strategies at appropriate levels based on file formats and perceived needs of our designated audience, the faculty and students of the University of Alabama.

The University of Alabama (UA) Libraries DigiPres group will determine the need to normalize or migrate files pending loss of access due to obsolescence. Decisions will be made on a cost/benefit basis with consideration for the needs of our stated audience.

High Level Policies

Security and Business Continuity Policies

Recommendations for Authors and Creators

Division of Digital Content

  1. Level I support is for content digitized in formats and with methods supporting the current archival standards, and for which we have digital rights management permissions and documented access permission. This is our most dedicated level of support. It includes collection of technical and administrative metadata, bit-level preservation, and commitment to migrate content as formats change over the years.An example would be a manuscript collection digitized by Digital Services.
  2. Level II support is for content which may not have been digitized in currently supported archival formats, but for which The University of Alabama Libraries has committed long term access support, and for which we have digital rights permissions and documented access permissions. An example would be Electronic Theses and Dissertations.
  3. Level III support is for content which needs to undergo regular change, and hence is not appropriate for inclusion in LOCKSS; however, it is to our benefit to offer bit-level preservation for this content until it needs to change. An example of this would be software necessary for either migration or emulation.
  4. Level IV support is for content which may not have been digitized in currently supported archival formats, but for which The University of Alabama Libraries has committed short term access support, and for which we have digital rights permissions and documented access permissions. An example would be Undergraduate Research Papers.
  5. Level V support is for 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. An example would be files digitized at the patron request.


Support Level Example Committed to sustain access Migration Support Emulation Support Long Term Retention Bit-Level Preservation Annual Review Local Backups
Level I Manuscript collection digitized by us Yes Yes Yes Yes Yes Yes Yes
Level II Electronic Theses and Dissertations Possibly Possibly Possibly Yes Yes Yes Yes
Level III Open source software for rendering archival content No No No No Yes Yes Yes
Level IV Undergraduate Research Papers No No No No No Yes Yes
Level V Material digitized at patron request No No No No No No Yes

Committed to sustain access

Every feasible effort will be made to continue access to this content. This may involve migration to new formats, or development and maintenance of emulation methods. This level of institutional commitment can only be made for content created in current archival format standards. Content not created in current archival standards is much likely to be migratable to new formats. However, if the content continues to be of value and either such migration is feasible and retains the significant properties of the content, or if emulation support is feasible, then continued access will be supported.

Migration Support

  1. 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.
  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, if available, will be stored in the archive. This will enable migration to newer file formats after the current ones become obsolete.
  5. A copy of an open-source operating system which supports the open-source software, if available and feasible, will be stored in the archive.
  6. Software and documentation necessary for emulation (recreation of the current user experience of our delivery system) will be stored in the archive.
  7. File system information which enables emulation of the operating system to support the file system will be stored with the content.

Emulation Support

  1. In addition to the migration support above, open-source software needed for creating derivatives and providing web delivery may be stored in the archive.
  2. Documentation of current procedures for recreating the current online user experience may be stored in the archive.

Bit-Level Preservation

  1. 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.
  2. We are and will continue to be involved in LOCKSS or a similar preservation network, supporting at least 6 copies of the archival content across a geographically disbursed area. All archival content will be made available to this system.

Annual Review

  1. Prior to obsolescence, all content will be evaluated for preservation measures, which may involve either migration (reformatting) or emulation. Dependent upon their decisions and the availability of resources and viable migration/emulation methods, efforts will be made to continue accessibility. All preservation measures taken will be recorded.
  2. If continued accessibility is deemed infeasible or advised against, online access will end, and stored content and metadata will be deleted.
  3. The definition of obsolescence used in these statements 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.

Long Term Retention

  1. Digital content will be named according to our file naming scheme and organized according to our file storage scheme on our storage server.

Local Backups

  1. 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.

Descriptive Metadata

  1. Up to 2 versions of descriptive metadata will be stored, the original and the most recent. Captures will be made quarterly from the delivery software web directories. If the metadata found there is more recent than what is stored, it will be placed in the archive. Version 2 of each metadata file will be overwritten with each new capture.


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

Jlderidder

Personal tools