4.4.2.2 Compliance with specification
The repository shall be able to demonstrate that any actions taken on AIPs were compliant with the specification of those actions.
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.
Preservation metadata logged, stored, and linked to pertinent digital objects and documentation of that action; procedural audits of the repository showing that all actions conform to the documented processes.
Successful preservation of information in the archive is strongly linked to following established and documented procedures to complete any actions that affect the repository data. The more often ‘special handling’ of repository data occurs and the more often this ‘special handling’ is not overseen in a consistent manner, the more likely that the data held by the repository will be compromised. When procedures are regularly followed, any deviation from procedures that would be likely to cause an alteration in the data will more likely be noticed or, if not noticed, may more likely be able to be corrected, or the timing and likely change could be identified in the future.
See 4.4.2.
APTrust runs automatic fixity checks on all files in the High Assurance Storage Class every 180 days. The system records PREMIS events describing when the fixity check occurred, what software performed the action, and what the outcome was.
APTrust permits restoration of objects through its WebUI and REST API. The restoration process is described in section 4.4.2.1. APTrust does not currently record PREMIS events when an object is restored. The system does keep a Work Item record showing when the request was initiated, when it was completed, whether it completed successfully or not, and where the restored item was placed for download. APTrust does not record who requested the restoration, whether the restored item was ever downloaded, or who may have downloaded it from the restoration area.
APTrust permits deletion of files and objects through its WebUI. This process is described in detail in section 4.4.2.1.) Upon deletion, the system records a PREMIS event describing when the item was deleted and at whose request.
See also: