4.2.1 - The repository shall have an associated definition for each AIP or class of AIPs preserved by the repository that is adequate for parsing the AIP and fit for long-term preservation needs.
Supporting Text
This is necessary to ensure that the AIP and its associated definition, including appropriate Packaging Information, can always be found, processed and managed within the archive.
4.2.1.1 The repository shall be able to identify which definition applies to which AIP.
Supporting Text
This is necessary to ensure that the appropriate definition is used when parsing/interpreting an AIP.
Examples of Ways the Repository can Demonstrate it is Meeting this Requirement
Documentation clearly linking each AIP, or class of AIPs, to its definition.
4.2.1.2 The repository shall have a definition of each AIP that is adequate for long term preservation, enabling the identification and parsing of all the required components within that AIP.
Supporting Text
This is necessary in order to explicitly show that the AIPs are fit for their intended purpose, that each component of an AIP has been adequately conceived and executed and the plans for the maintenance of each AIP are in place. (See 4.3 Preservation planning, below)
Examples of Ways the Repository can Demonstrate it is Meeting this Requirement
Demonstration of the use of the definitions to extract Content Information and PDI from AIPs.