3.3.3 Documented history of changes
|3.3.3 Documented history of changes|
|Compliance Rating||Mostly compliant|
The repository shall have a documented history of the changes to its operations, procedures, software, and hardware.
This is necessary in order to provide an ‘audit trail’ through which stakeholders can identify and trace decisions made by the repository.
Examples for Meeting the Requirement
Capital equipment inventories; documentation of the acquisition, implementation, update, and retirement of critical repository software and hardware; file retention and disposal schedules and policies, copies of earlier versions of policies and procedures; minutes of meetings.
This documentation may include decisions about the organizational and technical infrastructure. Documentation of or interviews with appropriate staff who can explain repository practices and workflow should be available.
All of our formal policies include a version history and list of reviewers.
- Preservation Services Policy: https://doi.org/10.18130/V3N58CK61
- Succession Plan: https://doi.org/10.18130/V31C1TF5Z
- Financial Sustainability and Business Principles and Practices: https://doi.org/10.18130/V3WM13T1F
- Collection Development Policy: https://doi.org/10.18130/V3RX93C9C
The Archive list provides access to previous versions of the wiki and WARC files.
Technical documentation, especially the Architecture and the System processes and interaction described in the Components, Responsibilities & Resources document, outline the hardware and software design of APTrust.