5.1.1.1.1 Hardware technologies appropriate to the services it provides to its Designated Communities

The repository shall have hardware technologies appropriate to the services it provides to its Designated Communities.

Supporting Text

This is necessary to provide expected, contracted, secure, and persistent levels of service including: ease of ingest and dissemination through appropriate depositor and user interfaces and technologies such as upload mechanisms; on-going digital object management; preservation approaches and solutions, such as migration; and system security.

Examples for Meeting the Requirement

Maintenance of up-to-date Designated Community technology, expectations, and user profiles; provision of bandwidth adequate to support ingest and user demands; systematic elicitation of feedback regarding hardware and service adequacy; maintenance of a current hardware inventory.

Discussion

The repository should be aware of the types of storage, file management, preservation and access services expected by its Designated Community, including where applicable, the types of media to be delivered, and needs to make sure its hardware capabilities can support these services. The objective is to track when changes in service requirements by the Designated Communities require a corresponding change in the hardware technology, when changes in ingestion policies require expanded capabilities, and when changes in preservation policies require new preservation capabilities. This can be driven by changes in capacity requirements (the time needed to read all media is longer than the media lifetime), by changes in delivery mechanisms (new clients for displaying authentic records), and changes in the number and size of archived records.

Evidence Provided

APTrust has not previously published a response to this requirement. The APTrust Certification Working Group is working on updating this page.