You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

5.1.1.6.2 - The repository shall have a process for testing and evaluating the effect of changes to the repository's critical processes.

Explanation

SP tests and evaluates changes to its critical processes in isolated development environments to ensure that changes will not disrupt normal operations. In addition to automated tests and checks performed by software, SP staff manually evaluate changes by examining samples of the relevant content. Staff evaluate changes for their effect on the integrity of information, the speed and efficiency of the system, and the accessibility and usability of disseminated information. The repository uses a code versioning system to record changes to software. Moving software from development to production is an automated process. Testing and evaluation continues in the production environment, and the repository uses JIRA for logging and reporting problems (see 5.1.1.3.1 for more information about JIRA).

Solicited and unsolicited feedback from users and OCUL members is another source of information about system behaviour. SP has a large and diverse Designated Community, and they regularly report malfunctions and glitches to repository staff.

Please see the Risk Analysis and Management Strategies document for additional information about software failure. The repository has a Backup Plan that describes policies and procedures used by SP and the University of Toronto Libraries' Information Technology Services department to provide reliable backup copies of the repository's data, databases, and applications.

Responsibility

Digital Preservation Policy Librarian

System Administrator

Potential Risks

There is always a risk of software failure in complex information systems. SP uses widely accepted, industry-standard procedures for testing and evaluating software changes, but small errors or conflicts sometimes escape testing. Software failure could force SP to suspend certain operations until the affected systems can be thoroughly analyzed, repaired, and tested.

Monitoring Commitments

SP will monitor changes to critical processes and procedures for compliance with the Mandatory Responsibilities described in OAIS. In addition, the repository will examine new editions of the OAIS Reference Model for changes.

Relevant Document

  1. Risk Analysis and Management Strategies
  2. Backup Plan
  • No labels