Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


SP tests and evaluates changes to its critical processes in an isolated development environment to ensure that changes will not disrupt normal operations or cause data corruption or loss. 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. Testing and evaluation continues in the production environment, and the repository uses JIRA for logging and reporting problems (see for more information about JIRA).

Feedback from the Designated Community is an important source of information about accessibility, usability, understandability, holdings, and overall system performance. As described in, the repository receives ongoing and extensive feedback from its Designated Community.

Please see the Risk Analysis and Management Strategies document for additional information about software failure. SP 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.