skip to content
(This requirement is based on a specification provided by a Discovery service vendor. Please feel free to edit . The specification is available for free unrestricted use and re-use under a creative Commons CC-0 license
What is the name of the system?
What open standards does the system support?
Please supply full details of system requirements, including production and test servers, operating systems, network, power supplies and any other dependencies on third party elements.
Please list the Library Management Systems with which the system is known to work.
Do you offer supplier hosting of the system? If hosted, please state if it is hosted in the UK or abroad, and if abroad, state the impact this status has in respect of the UK Data Protection Act.
If software is to be provided, will you be the sole owner?
If not, please state who will own it, how licensing will operate and how support will be provided.
Please give examples of your ability to work with third party suppliers in the context of these requirements.
Describe any searchable central index of scholarly materials, and the benefits to the user arising from this approach.
Provide full details of the agreements which you currently have with publishers to include their metadata in a central index.
How often is metadata from 3rd party suppliers updated?
Please describe the levels of metadata in the central index and any enrichment provided.
Describe how the system will import or access locally held catalogue records, journals lists, archival finding lists etc. Please describe how you would maintain consistency with the source.
What open Application Programming Interface (API) Web services or other open technologies are provided to facilitate the integration of existing and emerging library and institutional online services?
How is the integration of new services into the system supported by tools, documentation, user forums and/or technical support.
How does the system comply with prevailing UK accessibility legislation?
Does the system comply with the requirements of the Data Protection Act?
Describe how the system supports an integrated search of the Library catalogue, sources of article-level, journal-level and database-level metadata, and other locally held and external metadata sources including repositories and archive/museum resources.
How does the system support Federated Search?
If the system supports Federated Search describe how new or changed connectors are managed in the system.
The system must provide a straightforward search function that comes close to the Google experience in terms of speed and simplicity
Please describe how searches can be refined at any stage. Tools should be provided to help users improve the specificity of their search and relevance of results, and to expand their search to retrieve related results
The system should provide an alternative advanced search function. Please describe.
Search strings containing miss spelt terms should prompt "did you mean" alternative search suggestions and present an option to the user to return results that include suggested alternative search terms.
Searches should include synonymous terms not included in the entered search. A search results summary should make clear to users that the search includes synonyms.
A history of previous searches carried out during the current browser session should be available to the user until they log out or close their browser.
How is ranking of search results achieved?
How can locally held or licensed materials be highlighted in the search results?
How can records that lead directly to full text be flagged differently from metadata only records?
Provide details of OpenURL link resolvers which the system is known to support.
How are duplicate records identified and presented in the results list?
A summary at the head of the search result should include the search entered by the user, and the number of results retrieved.
The display of search results should be clear, without distractions (e.g. advertising).
The system should have the option to print, save, or e-mail search results and to send results to EndNote, RefWorks or other bibliographic software.
What options does your system offer for automated running of saved searches (i.e. SDI)?
The origin of each result (i.e. the information resources from which it has been drawn) should be displayed in each case, and be available as a hyperlink.
Catalogue record displays should include material type indicators (print/online book/journal; AV cassette, CD or DVD) for each record.
Record displays for physical items in the catalogue should include location and availability information, and links to make reservations.
Catalogue record item availability information must be updated dynamically from the Library Management System (LMS).
Items should include links to alternative fulfilment options e.g. interlending options, Google Books, WorldCat, Amazon.
Provision should be available for including book covers and links to other enriched content (Tables of Contents, introductory book chapters etc.).
Provide information about the authentication protocols that your system supports.
The system should allow users to review and run saved personal searches.
The system should allow users to save and manage search results
Functionality for tagging and reviewing search results for personal and public consumption should be available and self-evident. Describe how user-added content can be managed by system administrators.
Is the user interface customisable by the customer and/or the supplier? e.g. Local branding. Give examples.
Describe the functions carried out in any administrative interface provided.
Please detail the management reports available and the extent to which they are customisable
It should be possible to export statistics to standard desktop packages
Support and Maintenance
The service must be resilient to server, power, network and other failures.
The service must be restorable in the event of non-recoverable problems, such as disastrous server or component failure. Describe how this would work.
Specify the upgrades, updates and patches, and interoperation plug-ins that are included in the support and maintenance agreement.
Describe your system support arrangements for:
fault reporting and response procedures, including prioritisation and escalation;
software fixing procedures and time-scale;
how customers are informed about known software faults and bugs;
Describe your proposed ongoing support package including:
helpdesk features, availability and support levels;
availability of service level agreements;
arrangements for out of hours support;
Any other support provided.
Provide details of any warranties supplied with the service.
Describe how software support, development and enhancements are managed, particularly how customers are involved.
Describe your software release programme, including system updates.
Please provide a roadmap for future development of the product with timescales.
Training and documentation
What help and documentation is available for staff users and systems administrators?
Describe the quantity and nature of training provided as part of the standard implementation package and for new releases.
Describe the specialist technical support and advice relating for the maintenance and ongoing use of the system and contents.
[ close ]
Enable Complex Tables
Turn supplementary image paste support on
· Last modified: 2019/07/10 16:13 by
Back to top
Except where otherwise noted, content on this wiki is licensed under the following license:
CC0 1.0 Universal