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.

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 APTrust policies include a version history and a list of reviewers and approvers. For the list of policies, see the Policies page. Previous versions of each policy are archived in the University of Virginia’s institutional repository. 

The Historic Documentation list (internal access only) provides access to previous versions of the wiki and WARC files.

Technical documentation, such as the Architecture and System processes and interactions, is described on the System Infrastructure page (internal access only) and outlines APTrust’s hardware and software design.

See also Member Meeting pages.