4.3.1 Documented preservation strategies relevant to its holdings
|4.3.1 Documented preservation strategies relevant to its holdings|
|Compliance Rating||Mostly compliant|
This is necessary in order that it is clear how the repository plans to ensure the information will remain available and usable for future generations and to provide a means to check and validate the preservation work of the repository.
Examples for Meeting the Requirement
Documentation identifying each preservation risk identified and the strategy for dealing with that risk.
The repository should be able to deal with the types of requests that will come from a typical user from the Designated Community. A repository does not necessarily have to satisfy every possible request. Retrieval metadata is distinct from descriptive information that describes what has been found.
APTrust core service uses a robust, redundant cloud-based design to safely store data files deposited to it by Depositors and to be able to return identical data files to the Depositor when requested, with high-assurance proof provided by widely accepted verification methods that the files are indeed identical. In its core service, APTrust preserves content in its original format and is managed solely by the depositor. Services other than APTrust's core service may be available through APTrust now or in the future. In its core service, the APTrust does not provide access to deposited data files to any party other than the depositor and APTrust staff.
Content preserved by APTrust is stored in a combination of S3 and Glacier for redundancy, mitigation against failure in a particular storage layer as well as geographic redundancy (see Preservation and Storage).
APTrust's preservation strategy is based on LOCKSS threat analysis. The identified threats and mitigations, in certain cases being shared between APTrust and Amazon Web Services, are discussed in Risk Management, Threats, and Mitigations.
Ready for review