Library Service Platform
5.1. Reports to: The Government’s Representative 5.2 System Requirements At a minimum, the base system must be commercial off-the-shelf software. It must be a managed, turnkey system in use in other F... 5.1. Reports to: The Government’s Representative 5.2 System Requirements At a minimum, the base system must be commercial off-the-shelf software. It must be a managed, turnkey system in use in other Federal Government medical libraries. It must be capable of managing all types of library resources, e.g., print, digital, online, audio, visual, and other types. For future growth and networking, it must allow linking with other systems, sharing records, and/or creating consortium-like groupings of other Federal Government medical libraries. More specific required functionality follows. 5.2.1 Information System Security 5.2.1.1 The Contractor shall provide a completed system security plan (or extract thereof) and any associated plan of actions developed to satisfy the security requirements of the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Processing Controlled Unclassified Information in Nonfederal Systems and Organizations,” in accordance with DFARS clause 252.204-7012 to describe the Contractor’s unclassified information system(s) and network(s) where DoD controlled unclassified information associated with the performance of this contract is processed, stored, developed, or transmitted. 5.2.1.2 The Contractor shall, upon request, provide the Government with access to the system security plan(s) (or extracts thereof) and any associated plans of action for each of its subcontractors that processes, stores, develops, or transmits DoD controlled unclassified information associated with the performance of this contract. 5.2.1.3 The contractor shall ensure to meet the cloud computing requirements for non-IT Services as prescribed in DFARS clause 252.204-7012 (b)(2)(ii)(D). 5.2.1.4 The Contractor shall identify and verify marking requirements for all DoD controlled unclassified information associated with the performance of this contract as prescribed by DoDI 5200.48 and DoDI 5230.24. 5.2.1.5 The Contractor shall identify, track, and safeguard all DoD controlled unclassified information associated with the performance of this contract. 5.2.1.6 The Contractor shall document, maintain, and provide to the Government, a record of any subcontractor that receives or develops DoD controlled unclassified information, as defined in DFARS clause 252.204-7012, and associated with the performance of this contract. 5.2.1.7 The Contractor shall restrict unnecessary sharing and flow-down of DoD controlled unclassified information associated with the performance of this contract, in accordance with any marking and dissemination requirements specified elsewhere in the contract and based on a need-to-know to perform the requirement of this contract. 5.2.2 Circulation The proposed LSP must support basic circulation functions: checkout, checkin, renewal, in-house usage, holds, hold reports, and at least seven configurable borrower notices to be sent on a configurable schedule/calendar. It must support a calendar function that allows staff to set closed days that will prevent due dates falling on them. It must allow at a minimum the creation of complex circulation rules based on borrower type and status; item type and status; collection type; and material type. The proposed LSP must accept current barcode symbology (Codabar with check digit) and allow migration to RFID circulation. 5.2.3 Cataloging At a minimum, the proposed LSP must be able to import records in a variety of formats from a variety of sources, e.g., OCLC, Library of Congress, National Library of Medicine, MARC, XML, Dublin Core, OAI, BIBFRAME, BISAC, MODS/MADS, RDF, ONIX, and others. The proposed LSP must allow local improvements and customization of bibliographic and item records, e.g., custom 59X, 65X, and 9XX fields in MARC bibliographic records, copy-level and item-level messages in non-bibliographic records. 5.2.4 Acquisitions The proposed LSP must allow staff to order print and online resources. It must allow at least 100 locally-customizable funds and vendor records. It must allow multiple payment types. It must be able to transmit online orders to vendors and to receive vendor confirmation reports. The proposed LSP must track the order life-cycle: initial request, approval, fund assignment, encumbrance, order, order report, receipt, confirmation, payment, borrower notification, and withdrawal from the collection. It must track all fund deposits (including refunds), encumbrances, and expenditures. It must be able to calculate vendor discounts. It must be able to assign/allocate shipping costs between multiple funds. It must track vendor performance in terms of order-to-delivery time, stated vs. actual discounts received, and number of orders filled/unfilled. 5.2.5 Digital Right Management/Electronic Rights Management (DRM/ERM) The proposed LSP must track vendor license agreements, including start- and end-dates, allowable uses, disallowed uses, payment due dates, payment history, authentication methods, and administrator interfaces/logins/passwords. 5.2.6 Customized Usage Reports The proposed LSP must provide customizable, granular data for analysis of borrower use, collection use, e-resource use, vendor performance, and fund performance. Reports must be configurable by the user, e.g., library wide-collection-by-collection, item-by-item, item-status-by-item status, borrower-category-by-borrower-category, borrower-status-by-borrower-status, borrower-by-borrower, vendor-by-vendor, fund-by-fund, time-of-day-by-time-of-day, day-of-week, and other factors/parameters/combinations. It must provide a “dashboard” for quick-and-easy summary statistics to monitor on-going use, at the least updated to the day, preferably updated to the minute. It must be capable of at least outputting the data in .csv or .tsv files for analysis in Excel. 5.2.7 Links to Other Vendors’ Online Resources The proposed LSP must provide links to outside systems via APIs. At the least, it must adhere to the ANSI/NISO Z39.88 OpenURL protocol. It must connect to a link-resolver and a knowledge base to provide robust article-level linking capabilities. 5.2.8 Discovery Layer for End Users The proposed LSP must provide a modern discovery layer for end users. The discovery layer must permit users to conduct a single search across all library holdings and subscriptions, and it must return a single integrated list of search results. It must integrate with the Medical Library’s online subscriptions and the local catalog of physical books to return a unified list of book, journal, and online resources to end users. The result set must allow sorting and filtering at least by: full text, physical availability, whether or not it is peer-reviewed, whether or not it is open access, format, topic, author, publication date, language, and subject headings (Library of Congress and Medical Subject Headings). Result sets must be exportable or save-able to bibliographies. Citations must be exportable in at least the .ris format.
Data sourced from SAM.gov.
View Official Posting »