Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

4.2.6.1 - The repository shall have documented processes for acquiring PDI.

Introduction

When the SIP is first deposited into the repository, SP's customized loader script decompresses it and records the file fixity information. All of the Provider provided metadata for each file, including the PDI, is extracted and normalized to version 3.0 of the NIH Journal Archiving & Interchange Tag set and housed in the eJournals database. Each AIP is given a unique URI. From there it is accessed by the TDR loader script which creates the Preservation Metadata. SP Preservation Metadata for each AIP contains the Reference Information (URI), the Context Information (Provider provided bibliographic information and SP created linkages, TOCs, etc.), Fixity Information, and Provenance Information (created by SP in PREMIS vocabulary as 'events').

For a visual representation of these procedures please see the document belowBelow are the components included in SP's Preservation Description Information:

  • Reference Information - Identifiers are stored for each article identifying it globally (e.g. DOI) and locally (e.g. URI). Global identifiers are generally provided by the Provider while local identifiers are generated locally.
  • Provenance Information - Provenance metadata is generated locally for each object. It provides a history of preservation events in the object's lifetime, beginning at ingest into the SP repository and referencing any preservation activities taken on the object (e.g., replacement due to corruption, format migration, etc.).
  • Context Information - Context metadata is generated locally or supplied by the Provider. This metadata describes relationships between the CDO and other CDOs in the repository. Examples of these relationships can include: a newer version of a document that supersedes an older one, or a journal article that is a part of a journal issue.
  • Fixity Information - Fixity information is generated locally at the time of ingest in order to later determine whether or not the item remains in the same state as when it was ingested. This information can be used to determine integrity of an object being copied within the system (as in the case of a change in storage location), or for periodic integrity checks.
  • Access Rights Information - Access rights information is generated locally based on Provider licensing terms as negotiated between SP and the Provider.

For more information on the procedures used to generate or gather this metadata, see Workflow Charts.

Responsibility

Digital Preservation Policy Librarian

...