4.4.2 -The repository shall have contemporaneous records of actionsand administration processes that are relevant to storage and preservation of the AIPs.
Supporting Text
This is necessary in order to ensure documentation is not omitted or erroneous or of questionable authenticity.
Examples of Ways the Repository can Demonstrate it is Meeting this Requirement
Written documentation of decisions and/or action taken; Preservation metadata logged, stored, and linked to pertinent digital objects.
4.4.2.1 The repository shall have procedures for all actions taken on AIPs.
Supporting Text
This is necessary in order to ensure that any actions performed against an AIP do not alter the AIP information in a manner unacceptable to its Designated Communities.
Examples of Ways the Repository can Demonstrate it is Meeting this Requirement
Written documentation describing all actions that can be performed against an AIP.
Discussion
This documentation is normally created during design of the repository. It should detail the normal handling of AIPs, all actions that can be performed against the AIP, including success and failure conditions and details of how these processes can be monitored.
4.4.2.2 The repository shall be able to demonstrate that any actions taken on AIPs were compliant with the specification of those actions
Supporting Text
This is necessary in order to ensure that any actions performed against an AIP do not alter the AIP information in a manner unacceptable to its Designated Communities.
Examples of Ways the Repository can Demonstrate it is Meeting this Requirement
Preservation metadata logged, stored, and linked to pertinent digital objects and documentation of that action; Procedural audits of repository showing that all actions conform to the documented processes.