5.1.1 - The repository shall identify and manage the risks to its preservation operations and goals associated with system infrastructure.
Introduction (or Explanation)
Scholars Portal SP performs technical risk management in order to ensure the integrity, security, and reliability of the repository's content. Scholars Portal SP has assessed threats to its hardware, software, and technical operations and implemented a wide broad range of management risk-minimization strategies in collaboration with the University of Toronto Libraries' Information Technology Services (ITS) department. Technical risk management is a part of the repository's comprehensive risk management strategy, described in the Risk Analysis and Management Strategies document. In addition, the repository has a Backup Plan that describes policies and procedures implemented by SP and ITS to provide reliable backup of the repository's data, databases, and applications. To support the repository's risk-minimization activities, SP maintains an inventory of hardware and software components.
The Risk Analysis and Management Strategies document covers, among other things, the following technical risks:
- hardware failure or and obsolescence
- storage media failure or and obsolescence
- software failure or and obsolescence
- loss of critical hardware or software support
- operator error
- cyber attack
To minimize risk
ensure secure and trustworthy
inventory of components/lifetimes/refreshment schedule
community supported software?
risk assessments for hard, soft, operational
scalable, evolvable, extensible without disruption
export to future custodian
A summary of our practices in relation to our objectives, commitments, and context. May include:
- Standards met or industry best practices employed, and their applicability to Scholars Portal; certifications achieved or audits undertaken if applicable
- Differences from standards or best practices and our rationale for those differences if applicable
- Parties involved in the creation of the document if applicable\
The complete text of the SOMETHING is available through the link below. The SOMETHING fulfills all or part of this criteria by describing SOMETHING, SOMETHING, and SOMETHING. (repeat for all documents linked)In order to change hardware or software components without disrupting normal operations, SP implements and tests changes in isolated environments. For policies and procedures related to hardware and software change management, please see 220.127.116.11.4, 18.104.22.168.8, 22.214.171.124, 126.96.36.199 , 188.8.131.52.1, and 184.108.40.206.2. For policies and procedures related to operator authorization and access, please see 5.2.3.
Digital Preservation Policy Librarian
Potential Risks (delete if not needed)
Significant risks, threats, changes, or dependencies that could affect our ability to satisfy this criteria or deliver this service in the future. How are we addressing these risks?
Monitoring Commitments (delete if not needed)
How frequently we intend to monitor the situation or review the document. Mention automated reports if applicable.
Future Plans (delete if not needed)
Things we are planning to do in the future. Things we would like to do in the future.
Relevant Document(s) (delete if not needed)
- Document Title (link)
Key Resources Consulted (delete if not needed)