5.1.2 Manage the number and location of copies of all digital objects
|5.1.2 Manage the number and location of copies of all digital objects|
|Status||Ready for review|
|Compliance Rating||Fully compliant|
The repository shall manage the number and location of copies of all digital objects.
This is necessary in order to assert that the repository is providing an authentic copy of a particular digital object.
Examples for Meeting the Requirement
Random retrieval tests; validation of object existence for each registered location; validation of a registered location for each object on storage systems; provenance and fixity checking infonnation; location register/log of digital objects compared to the expected number and location of copies of particular objects.
A repository can have different preservation policies for different classes of objects, depending on factors such as the producer, the information type, or its value. Repositories may require a different number of copies for each class, or manage versions needed to meet access requirements. There may be additional identification requirements if the data integrity mechanisms use alternative copies to replace failed copies. The location of each digital object must be described such that the object can be located precisely, without ambiguity. The location can be an absolute physical location or a logical location within a storage media
The APTrust ingest process disassembles the submitted bag, records it's metadata in its' repository database and stores intellectual objects in their respective S3 buckets and Glacier storage. As part of the ingest workflow storing of digital items in the preservation storage is verified the APTrust storing service after the object has been stored.
Regular 90-day fixity checking ensures consistent copies of all digital objects.