3.3.3 - 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 of Ways the Repository can Demonstrate it is Meeting this Requirement
SP documents major changes to its organizational and technical infrastructure in its annual reports to OCUL Directors. These reports record the history of changes in ongoing and planned projects, contractual obligations, organizational structure, staffing levels, operating procedures, hardware, and software. SP preserves copies of these reports. In addition, SP preserves copies of minutes of meetings and budgets in order to record the history of key decisions made by staff. SP's Organizational Chart identifies appropriate staff who can explain repository practices and workflows.
SP retains historical versions of software in its code versioning system so that changes to critical processes can always be reversed. Please see 126.96.36.199.1 for additional details.
Digital Preservation Policy Librarian
While SP documents the history of major changes to its organizational and technical infrastructure, there is a risk that minor changes, which may turn out to be significant at a later time, are not recorded in an easily accessible or understandable format or not recorded at all.
There is a risk that personnel who know the repository intimately will leave the organization at some point. To minimize this risk, SP keeps a record of changes (see Explanation above) and uses well known technical components. Please see the Risk Analysis and Management Strategies document for more information about SP's strategies for reducing the impact of personnel departures.