3.3.3 Documented history of changes

From aptrust
Jump to: navigation, search

3.3.3 Documented history of changes
Status Ready for review
Compliance Rating Fully compliant

The repository shall have a documented history of the changes to its operations, procedures, software, and hardware.

Supporting Text

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.

Evidence Provided

Partner Meeting Minutes

All of our formal policies include a version history and list of reviewers.

The Archive list provides access to previous versions of the wiki and WARC files.

There are two versions of our wiki: Old wiki and New wiki

Technical documentation, especially the Architecture and the System processes and interactions described in the Architecture page, outline the hardware and software design of APTrust.