4.3.5 Documented AIP export plan

The repository must be able to export the relevant AIPs to its successor location in the timescale required, together with supplementary information including specifications of the AIPs adequate for the information contained in them to be extracted.

Supporting Text

This is necessary to ensure that the objects it had originally committed to preserve can be imported into a successor preservation system.

Examples for Meeting the Requirement

Written and credible detailed export plan with details of the encoding of the AIP including its mapping to the OAIS Information Model; definitions of the Designated Communities, Preservation Objectives, and Transformational Information Properties which the originating repository used; descriptions of the relationships between Editions and Versions of AIPs; explicit agreements with successor organizations documenting the measures to be taken to ensure the complete and formal transfer of responsibility for the digital content and related assets, and granting the requisite rights necessary to ensure continuity of the content and repository services.

Discussion

A repository’s inability to preserve specific digital information threatens the long-term sustainability of that information content. The repository should be able to provide enough information for the AIPs to be imported into the successor custodian’s preservation system. The timescale may be determined by the funding horizon of the repository; that is, the export form of the AIPs must be created and exported within that timescale.

The repository should also provide information to its Designated Communit(ies) when it is contemplating and after it has executed such a handoff.

The contingency plans could include procedures to destroy certain of its holdings, following specified procedures.

Evidence Provided

This requirement was added in the most recent version of ISO 16363. The APTrust Certification Working Group is working on updating this page.