Date: Tue, 19 Mar 2024 02:57:24 -0400 (EDT) Message-ID: <312126721.13.1710831444817@spatlassian.scholarsportal.info> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12_1392917145.1710831444816" ------=_Part_12_1392917145.1710831444816 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Explanation
In order to provide a level of service that meets the repository's contr= acted obligations, SP selects and implements hardware technologies based on= a clear and comprehensive understanding of the needs and expectations of i= ts Designated Com= munity Definition, who support decision-making by providing an overview= of the repository's user communities.
SP staff work closely with members of the Designated Community to identi= fy system requirements and test components. Representatives from the Design= ated Community sit on SP's advisory committees, giving them a direct channe= l to the repository's directors and systems administrators. In addition, SP= receives ongoing feedback about system behaviour from its Designated Commu= nity. For example, see the Feedb= ack Forum in SP's journals interface. Feedback from the Designated Comm= unity provides valuable information about response times, page loading, and= overall system performance. Generally, the close relationship between SP a= nd its Designated Community means that SP staff are aware of new needs and = expectations at an early stage.
Systems administrators at SP and the University of Toronto Libraries' In= formation Technology Services department receive information about system b= ehaviour and usage from automated monitoring programs. These programs warn = administrators about events and loads that exceed predetermined levels. Ple= ase see 5.1.1.1.2 for more in= formation.
The repository has an inventory of hardware and software to help staff c= arry out long-term technology planning.
Responsibility
Digital Preservation Policy Librarian
Systems Administrator
Potential Risks
In order to comply with this point, SP must maintain a thorough understa= nding of the needs of its Designated Community. If SP has imperfect or inad= equate information about the repository's Designated Community, then there = is a risk of using inappropriate hardware. The practices described above (s= ee Explanation) are designed to minimize this risk, but sudden, unexpected = changes in user behaviour are possible.
Future Plans
SP has procedures, commitments, and financial resources for regular hard= ware replacement and media refreshment. See 5.1.1.1.4 for details.
Relevant Documents