Page History

...

• Persistent IDs for digital preservation (Bill)
  • We are working on preserving the digital objects in two large collections, the Euclid journals and the arXiv.org preprints.  In general, we can view the objects as having at least one content file and an object descriptor file containing metadata about the object. Most digital objects contain multiple content and metadata files.  We need to be able to identify and locate the files for a long time, regardless of where they are located. Rather than changing the metadata in the descriptor file every time a file is moved-an event that occurs several times during the archival ingest and storage process-we would like to create persistent identifiers that can be mapped to the files' current locations.
  • The number of component files to be preserved will be several times larger than  the number of digital objects. With processing efficiency in mind, we would prefer a solution that will allow us to resolve the identifiers locally, without going out over the internet for each request for resolution.
  • The digital objects' component files in our preservation system will not be directly accessible to the public; access will occur through a gated interface. The persistent identifiers need not, and should not, be public.

• • identifier mechanism we use should be able to be produce identifiers that are private and not discoverable.

Requirements for an implementation (John)

...

• A deliverable: A Usage Document that explains how the system can be integrated into CUL collection building  (Adam C)

• An We recommend that, embedded in mapping metadata, there be an explicit statement of the estimated lifespan of the PID and of the object it represents. This practice will add value to the identifier and help enforce a best practice in lifecycle management of our digital objects. (Bill)