The most important document related to preservation is RLG's Audit Checklist for the Certification of Trusted Digital Repositories.
Items on RLG's checklist of immediate interest
For the most part, these items relate to our use of HPSS:
- 3.6 Repository commits to define, collect, track, and provide, on demand, its information
- B1.1 Repository identifies properties it will preserve for each class of digital object.
- B1.5 Repository obtains sufficient physical control over the digital objects to preserve
them. (The description of this is confusing, encompassing many different aspects of repository functionality.)
- B2.1 Repository has an identifiable, written definition for each AIP or class of information
preserved by the repository.
- B2.4. Repository has and uses a naming convention that can be shown to generate visible,
unique identifiers for all AIPs.
Other preservation-related items
OAIS is the primary model for building preservation systems.
RLG's older document, Trusted digital repositories: Attributes and Responsibilities.
The October 2005 RLG DigiNews describes requirements for "certification" of a digital repository. Many of these requirements are related to preservation.
There is a paper from Los Alamos about integrating OAI and OpenURL with an OAIS model.
There is a paper on bottom-up preservation issues that may also be useful.
The architecture of the LOCKSS system may be a useful guide, but LOCKSS currently relys on each participating institution "owning" a copy of the item. This is most useful for electronic journals.
Portico is a preservation archive for e-journals, based on Documentum. They perform extensive validation before accepting data into their repository.
The Florida Center for Library Automation is developing an archive system. This may provide some ideas, and they may eventually release code that we can use.
Vol. 54 (2005) no. 1 of 'Library Trends' is a theme issue, entitled: "Digital Preservation: Finding Balance", with many interesting articles.
Meet with the HPSS people to find out about their long-term plans and how best to store files. Can we
eventually store lots of small files (page images)