In order to provide a level of service that meets the repository's contracted obligations, SP selects and implements hardware technologies based on a clear and comprehensive understanding of the needs and expectations of its Designated Community . The repository's Designated Community Definition supports 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 identify system requirements and test components. Representatives from the Designated Community sit on SP's advisory committees, giving them a direct channel to the repository's directors and systems administrators. In addition, SP receives ongoing feedback about system behaviour from its Designated Community. For example, see the Feedback Forum built into in SP's journals interface. Feedback from the Designated Community provides valuable information about response times, page loading, and overall system performance. Generally, the close relationship between SP and its Designated Community means that SP staff are aware of new needs and expectations at an early stage.
The primary risk to SP's compliance In order to comply with this point is a disconnect with the Designated Community such that SP is not aware that the system is no longer meeting the community's needs, or that the community has needs that have not been communicated or anticipated, SP must maintain a thorough understanding of the needs of its Designated Community. If SP has imperfect or inadequate information about the repository's Designated Community, then there is a risk of using inappropriate hardware. The practices described above (see Explanation) are designed to minimize this risk, but sudden, unexpected changes in user behaviour are possible.
SP has procedures, commitments, and financial resources for regular hardware replacement and media refreshment. See 220.127.116.11.4 for details.
- Designated Community Definition
- Hardware and Software Inventory (available on request)