4.2.6 Documented processes for acquiring PDI for associated Content Data Object
The repository shall have documented processes for acquiring Preservation Description Information (PDI) for its associated Content Data Object and acquire PDI in accordance with the documented processes.
In particular the following aspects must be checked:
4.2.6.1 The repository shall have documented processes for acquiring PDI.
4.2.6.2 The repository shall execute its documented processes for acquiring PDI.
This is necessary in order to ensure that an auditable trail to support claims of authenticity is available, that unauthorized changes to the digital holdings can be detected, and that the digital objects can be identified and placed in their appropriate context.
Standard operating procedures; manuals describing ingest procedures; viewable documentation on how the repository acquires and manages Preservation Description Information (PDI); creation of checksums or digests, consulting with Designated Community about Context.
PDI is needed not only by the repository to help ensure the Content Data Object is not corrupted (Fixity) and is findable (Reference Information), but to help ensure the Content Data Object is adequately understandable by providing a historical perspective (Provenance Information) and by providing relationships to other information (Context Information). The extent of such information needs is best addressed by members of the Designated Community(ies). The PDI must be permanently associated with Content Data Object.
APTrust maintains documented processes for acquiring, generating, preserving, and associating Preservation Description Information (PDI) with its Content Data Object. These processes are defined in the APTrust BagIt Profile and Bagging Requirements, the APTrust User Guide (Ingest, Updates, and Restoration), PREMIS Events documentation, and related Registry workflow documentation.
PDI in APTrust consists of both depositor-supplied metadata and repository-generated preservation metadata. These processes are executed during ingest and throughout the AIP lifecycle, and PDI remains permanently associated with the Content Data Object.
Definition of AIP describes the PDI associated with each intellectual object and provides the details of PDI generation during the creation of that object.