4.2.7 Content Information is understandable for Designated Community at the time of AIP creation
|4.2.7 Content Information is understandable for Designated Community at the time of AIP creation|
|Compliance Rating||Half compliant|
The repository shall ensure that the Content Information of the AIPs is understandable for their Designated Community at the time of creation of the AIP.
This is necessary in order to ensure that one of the primary tests of preservation, namely that the digital holdings are understandable by their Designated Community, can be met. (See 4.3 for additional requirements for understandability beyond ingest.)
Examples for Meeting the Requirement
Test procedures to be run against the digital holdings to ensure their understandability to the defined Designated Community; records of such tests being performed and evaluated; evidence of gathering or identifying Representation Information to fill any intelligibility gaps which have been found; retention of individuals with the discipline expertise.
This requirement is concerned with the understandability of the AIP. If the ingested material is not understandable, the repository needs to ingest or make available additional information to make sure that the AIPs are understandable to the Designated Community(ies). For example, if documents are written in a dying language and the Designated Community is no longer able to understand the language the documents are written in, the repository would need to provide additional documentation that would allow the Designated Community to understand the documents (e.g., translations of the documents in a language the Designated Community could understand or dictionaries that would allow the Designated Communities to translate the documents into a language its members understand).
2007 Requirement ID
B2.10 Documented process for testing understandability of the information content
APT makes sure that the information is understandable. The two things that describe the AIP are the object resource and the file resource. those resources are visible thru the Web UI and the rest APIApplication Programming Interface.
The system does not have regular, recurring automated restore tests, which are currently done on an adhoc basis and not recorded. -- Andrew needs to get this implemented to get this item FULLY COMPLIANT.