4.2.6 Documented processes for acquiring PDI for associated Content Information
The repository shall have documented processes for acquiring Preservation Description Information (PDI) for its associated Content Information 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 Information is not corrupted (Fixity) and is findable (Reference Information), but to help ensure the Content Information 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 Information.
Preservation Description Information (PDI) is captured first as the BagIt tag files upon submission of SIPs to the S3 Receiving Bucket, and second as system-generated PREMIS event metadata, upon ingest. Additionally, PDI is captured for Update actions.
Definition of AIP describes the PDI associated with each intellectual object and provides the details of PDI generation during the creation of that object.
Processes for acquiring PDI are also documented in the following places: