Attachment_1_Library_LMS_Section_J.docx

Document Title: Library Services Platform for the Census Bureau Library Section J.1. Attachment 1 System and Support Requirements Document Number:

ADMIN-18-0087

Page:

SECTION J.1. ATTACHMENT 1. SYSTEM AND SUPPORT REQUIREMENTS

J.1. GENERAL SYSTEM AND SUPPORT REQUIREMENTS

This section describes requirements that shall be met by the proposed solution as a whole.

J.1.1. Architecture, System Updates and Upgrades, and Reliability

· Census Bureau Library strongly prefers a single, cloud-based solution.

· Where requested below, include a narrative description of how the system complies with the requirement or explain why it does not comply.

· Please specifically address the functions and features of any client-based software included in the proposal.

(a) Act as a completely functional integrated library system (ILS) in its own right, and not be tied to an underlying ILS in order to function completely.

Describe how the system complies with this requirement or explain why it does not comply.

M

(b) Have all modules in full, operational release at the time of proposal submission. Or, 1-2 minor modules in beta testing with the production release planned within three (3) months of this solicitation’s closing date.

Fully document and describe any major releases to the system that are planned within the next six (6) months.

M

(c) Systems shall comply with Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d).

Provide details for each system demonstrating the solution adequately addresses the requirements for Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d).

Submit a Voluntary Product Accessibility Template (VPAT) for each system offered.

M

(f) The system should allow the Library to increase capacity, content, and users without requiring changes to its deployment architecture.

Describe the system’s ability to scale.

M

(h) Be completely cloud-based with multitenant architecture.

Describe in narrative how the system complies with this requirement or explain why it does not comply. Please specifically address the functions and features of any client-based software in the proposal.

D

(i) The systems are under continual enhancement, with regular updates rather than large overhauls every few years.

D

(j) Not including scheduled downtime for updates, have a system uptime of at least 99.75%.

Document the system’s typical annual scheduled downtime. Also document the system’s average unscheduled downtime for the last 24 months.

D

J.1.2. Data Security and Access

Preferably the system(s) shall:

(a) Be FedRamp compliant, or the vendor must be able to provide documentation that compliance is anticipated within six months of this solicitation’s closing date.

Provide this documentation M

(b) Comply with all security, access, authentication, and other protocols and perform continuous monitoring, as required by FedRamp compliance.

M

(c) The System shall allow different levels of authentication, i.e., staff levels, patron types, etc.

Describe system authentication for both staff and patron accounts.

M

(d) Allow the Library full access to extract or export its complete set of bibliographic, patron, digital assets, and other data at no additional cost (beyond pricing in Section B.), should the Library terminate its use of the system.

Describe the process for extracting or exporting the Library’s data and assets from the system; for example, if the Library later decides to migrate to a different LSP. Also state whether there is any additional charge for this data extraction (up to two passes) or if it is included.

M

J.1.3. Integration and Extensibility

The proposed solution shall seamlessly integrate the following functions and constituents:

J.1.4. Contractor Support

J.1.4.1. Training

The Contractor will provide a comprehensive training plan for understanding and using all system functions. This training will include but is not limited to:

(d) Continuous training after implementation. If webinar-based, available at no extra cost.

Describe how the system complies with this requirement or explain why it does not comply. Please also include a description/list of typically scheduled live webinars and a list of recorded webinar available at any time.

M

J.1.4.2. Help Desk and Customer Support

The Contractor shall:

(b) Provide a Service Level Agreement that addresses the Contractor’s response to support requests.

Describe customer service support response times, including details on any tiering/triaging of tickets.

M

(d) Provide the same level of customer support to all customers, without additional charges for higher levels of support.

Describe how the system complies with this requirement or explain why it does not comply. If additional charges apply, please list fees.

D

J.1.4.3. System Maintenance and Long-term Management

The Contractor shall ensure that:

(a) Major and minor system releases will occur on a regular basis.

Provide an annual maintenance schedule, the product’s Roadmap for the next 24 months, and the update schedule for the next 12 months.

M

(d) The system has long-term feasibility and relevance by tracking trends and technological advancements in the library and archives professions, and incorporating these advancements into the system’s long-range design.

M

(e) The solution is implemented primarily at Academic and Special libraries to ensure that product development is in line with the needs of these library types. Solutions implemented primarily at public and school libraries will not be considered.

State the percentage of LSP implementations at Academic, Special, Public, and School libraries. Implementations should be reported at the top level for each institution and not include branches.

M

(f) Customers have a strong voice in determining and prioritizing new features and enhancements, and the Contractor will solicit and integrate customer feedback and involvement in future system direction.

Describe how the system complies with this requirement or explain why it does not comply. Please include information regarding the process for making enhancement requests, the typical turnaround time for implementing agreed-to enhancement requests, and any other information that documents the Contractor’s enthusiastic willingness to give Customers a strong voice in product development.

M

J.2. LIBRARY STAFF FUNCTIONAL REQUIREMENTS

Staff functions and modules are those that are used exclusively by Census Bureau Library Staff and comprise Acquisitions Management, Cataloging, Circulation, Digital Asset Repository, Electronic Resource Management, Holdings Management, Interlibrary Loan, Serials Management, Reporting/Statistics, and Global Updates. All functions and modules shall integrate seamlessly and be cloud-based.

J.2.1. Requirements Applicable to All Library Staff Functions

The following requirements are applicable to all back-end/Library Staff functions and the system(s) that handle those functions.

J.2.1.1. System Integration and Customization

The Customer requires a solution that integrates a seamless workflow between systems/functions. The system shall:

(a) Offer easy-to-implement, seamless, and easy-to-use interoperability between systems/functions.

M

(c) Provide workflow automation such as dashboards, reminders, e-mails, notifications, and alerts.

M

(d) Allow library staff to toggle or move easily between circulation and other staff modules, such as cataloging, acquisitions, circulation, reports, and others.

M

(e) Include the ability to modify order and bibliographic status (i.e. on order, arrived, checked out, lost, ILL, etc.

Describe how the system complies with this requirement or explain why it does not comply. List specific status selections and whether library can add/modify custom status selections.

M

(f) Allow library staff to use modules concurrently, without losing current work data when toggling or moving between modules.

D

J.2.1.2. Data Handling

The system shall:

(a) Support global changes to entire fields and subfields, and specific strings within fields and subfields in all record types including, but not limited to, order, vendor, bibliographic, circulation, patron, item, and authority records.

M

(b) Include validation for order, bibliographic, holdings, item, patron, and authority records.

M

(c) Include standard database maintenance reports of the system, including, but not limited to, subject headings, data duplication, etc.

M

(d) Include current and future linked data and search engine crawling/indexing capabilities.

Describe how the system complies with this requirement or explain why it does not comply. In particular, how would patrons and the public discover Library’s holdings through the use of linked data or search engine crawling/indexing when searching for materials on a variety of search engines? How would they see search results linking to the library’s individual bibliographic records or URIs, rather than search results linking to the library’s home page or the Discovery home page? Are there options for the library to customize the search engine optimization of the portions of its records/holdings that are publicly viewable?

M

(e) Make data available through documented web services and APIs, including supported data operations (read, write, update, delete, etc.).

Describe how the system complies with this requirement or explain why it does not comply. Information on licensing or technical restrictions or constraints placed on the use of these tools and services shall be provided. Please include a list of all currently available APIs and those that are planned for future release.

M

J.2.2. Requirements Applicable to Specific Back-end / Library Staff Functions

J.2.2.1. Acquisitions Management

If module provided, the system shall include:

(a) Basic acquisitions management features such as ordering, receiving, cataloging, etc.

M

(b) Integration with book vendors, including the ability to find items for purchase from multiple vendors, and the ability to import complete MARC records for ordered items prior to receipt.

Describe how the system complies with this requirement or explain why it does not comply. Please also list supported book vendors (such as Baker & Taylor, Ingram, etc.)

M

(c) Capabilities such as library-level budgeting, ability to place, store, and report on orders, financial reporting, vendor records, and a desiderata file.

D

J.2.2.2. Cataloging

J.2.2.2.1. General Cataloging Requirements

The solution shall provide:

(a) Support for multiple metadata standards, including MARC, Dublin Core, and RDA.

List available built-in metadata standards.

M

(b) Support for the Library Linked Data model, including the Resource Description Framework (RDF) and BIBFRAME.

Describe how the system complies with this requirement or explain why it does not comply. Please include information about plans to use linked data to expose the library’s records and holdings to the greater web (through search engines and other sources). Also describe any relevant partnerships with third parties (such as Zepheira).

M

(c) Conversion tools or utilities within the system(s) that translate one metadata schema to another.

D

(d) Ability to add local fields to imported records, including, but not limited to, holdings information, shelf location, multiple notes fields, and other proprietary fields.

M

(l) Capability to edit records individually and globally with ability to make those edits within the cataloging module, without having to use any external resources to make global edits.

D

(m) Capability of batch addition/deletion/modification of bibliographic and/or item records.

M

(o) Ability to create cataloging templates that include pre-populated data, including shelf locations and other fields.

D

(r) A link checker to identify/update broken links.

D

(s) E-book integration that allow patrons to discover and download e-books with minimal clicks.

D

(v) Ability to create catalog records for non-standard materials such as A/V equipment and other non-print-based physical objects.

D

(x) Include robust search functions for catalog and patrons records:

· Ability to search most data fields

Describe which data fields are searchable and which are not.

M

· Advanced autocomplete and autosuggest functionality

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically state whether search terms can be pre-loaded, or if the search becomes more robust as more users search.

D

· Autocorrect and “Did you mean…?” functionality

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically state whether search terms can be pre-loaded, or if the search becomes more robust as more users search.

D

(z) Ability to have up to 3 location levels per item.

Describe this functionality.

D

(aa) Ability to tag items for routing to specific patrons when they are received and processed.

D

(ab) Ability for library staff to view and revert to prior versions of bibliographic records.

Describe this functionality, including any ability to undo changes. Also describe how many previous record versions back a user can go.

M

(ac) Ability to have bibliographic changes (modifications to existing records or new records) visible in the Discovery system within several hours.

M

(ad) Ability to have holdings changes visible in OCLC WorldCat within several hours.

State the duration of time between posting holdings to OCLC WorldCat and their appearance in OCLC WorldCat.

D

J.2.2.2.2. Cataloging Authority Control

The solution shall:

(a) Allow for the management and maintenance of shared authority files.

Describe how the system complies with this requirement or explain why it does not comply. Please also list which authority control files are included/used.

D

(c) Allow for both third party authority control files and the ability to create custom authority control files.

D

(d) Support proprietary authority files of the library’s own creation, and allow for those files to have controlled vocabularies.

D

J.2.2.2.3. Cataloging Statistics and Reporting

The solution shall have:

(b) The ability to run reports at various frequencies: monthly, weekly, daily, hourly, on the quarter hour. Reports can be scheduled to run at these frequencies or run manually as needed.

M

(c) The ability for report to output in multiple formats: tab delimited files, graphs, Excel, HTML, PDF, XML, TXT, RTF.

Describe how the system complies with this requirement or explain why it does not comply. Please list both the process of exporting data and supported file types.

M

(d) The ability to produce lists of items by:

J.2.2.3. Physical Processing

The solution shall support:

(b) The processing of physical materials including support for spine-label printing through the solution itself and third party label printing software.

M

(c) The processing of regularly-scheduled and special issues of serials, including receiving, item generation, labeling, and routing.

D

J.2.2.4. Serials Management

If module provided, the system shall include:

(f) Electronic claims of missing/damaged issues, whether the library handles serials in-house or through a third-party vendor.

D

J.2.2.5. Holdings Management

The serials module of the system shall:

(a) Have multiple fields available for documenting local holdings in MARC and other cataloging formats.

Describe how the system complies with this requirement or explain why it does not comply. Please list specific fields with this functionality.

M

(b) Support the linking of bibliographic records to other bibliographic records in the catalog. For example, linking the records of various formats of the same title, or linking between records when the title has changed.

M

(c) Support the display of the Library’s local holdings for items in union catalogs, such as OCLC WorldCat or others.

D

J.2.2.6. Circulation and Interlibrary Loan

J.2.2.6.1. General Circulation Functions

The circulation module shall include the ability to:

(a) Create lending rules (by item format, patron group, staff type, etc.) and determine levels of access for viewing and manipulating those rules.

M

(d) At point of service, retrieve borrower records via specific fields, including borrower name, borrower unique identifier, barcode, etc.

M

(g) Change an item’s status without first checking it in (such as marking it “damaged”).

M

(h) Circulate non-print physical items, such as A/V equipment.

D

(i) Circulate e-books, audio files and other electronic resources, especially those that require proprietary software.

D

(j) Provide for automatic renewals of checkouts, unless there is a hold on the item.

D

(l) Generate automated staff notifications via e-mail regarding holds, overdue books, and other circulation-related issues using e-mail. (For example, when a patron places an ILL or hold request, a notification e-mail is sent to Library staff).

D

(m) Send overdue and other notices multiple times, at intervals that can be customized for different patron and item types.

M

J.2.2.6.2. Patron Records, Communications, and Notifications

The circulation system(s) shall be able to:

(a) Provide batch import, editing, and deletion of borrower/patron records.

M

(c) Generate automated patron notifications regarding holds, overdue books, and other circulation-related issues using e-mails that can be scheduled to run at a set times or immediately upon an action (for example, a book is returned, which triggers a checkout to the next patron with a hold for the book, which then triggers an immediate e-mail notifying the patrons that the book is available).

M

(d) Allow for the customization of the language and design of patron notifications.

M

J.2.2.6.3. Interlibrary Loan

The Interlibrary Loan, the system shall be able to:

(a) Integrate interlibrary loan directly into circulation workflow by including processing of incoming and outgoing interlibrary loan items within the system, or with an outside system such as OCLC ILL.

M

(b) Allow Library patrons to identify items of interest outside of the Library’s collections and to initiate ILL requests for those items through the Discovery system.

Explain how patrons can identify and request items held by other libraries.

D

(c) Allow library staff to differentiate between books checked out to local patrons and books checked out for ILL.

D

J.2.2.6.4. Circulation Statistics and Reporting

The system shall have the ability to:

(a) Generate the majority of brief reports within 1-2 minutes, and lengthy reports within 10-30 minutes (or some other quantitative measure).

Describe how long it takes to view/download different types of reports after running them. Please differentiate between pre-designed/off-the-shelf reports and custom-designed reports.

M

(b) Retain transaction-oriented information indefinitely for statistical reporting purposes, even if the associated item or patron has been removed from the system.

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically address how this information is accessed, and if there is an additional fee required.

M

(c) Toggle on and off the retention of individual book checkout histories, both in aggregate (high-level data across all book checkouts) and also at the individual patron level (for a particular book, a history of the patrons that checked it out).

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically address the following: once a decision is made at the outset to capture or not capture individual book checkout histories, can the decision be reversed?

M

(d) Toggle on and off the retention of individual patron circulation histories.

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically address the following: once a decision is made at the outset to capture or not capture patron checkout histories, can the decision be reversed?

M

(e) Generate reports (both from templates and those that are created on an ad-hoc basis on:

(g) Generate borrower/patron reports by any field in the borrower record and by items linked to those records, including user location, office, etc.

D

J.2.2.7. Electronic Resource Management

If module provided the system shall include:

(a) The ability to manage the following types of administrative information:

(b) Workflow management of electronic resources, such as reminders for renewal or the ability to track new resources from trials through to rollout.

D

(c) The ability to output electronic resource records for integration into library websites and Discovery systems.

D

J.2.2.8. Digital Collection and Asset Repository

J.2.2.8.1. General Requirements

In addition to the general technical requirements listed in Section B, the Digital Collection and Asset Repository module shall meet the following technical criteria:

(a) Be interoperable with other systems, including the Library Services Platform (LSP) modules.

Describe whether Digital Asset Repository functionality is a core part of the Library Services Platform or an independent platform.

M

(b) Provide a web interface for users to access the material in the digital collection.

M

(c) Be standards-based, such as Dublin Core, XMP, and DACS.

M

(d) Make data available through documented web services and APIs, including supported data operations (read, write, update, delete, etc.).

Describe how the system complies with this requirement or explain why it does not comply. Please include a list of all currently available APIs and those that are planned for future release.

D

J.2.2.8.2. General Functionality

The system shall allow for digital collection and asset processing and storage and include:

(b) The ability to ingest files from multiple locations and file servers, whether from hardware or from the cloud.

Describe how the system complies with this requirement or explain why it does not comply. Please list all applicable hardware (PC, CD-ROM, DVD, etc.) and remote web sites/file servers (Google Docs, Dropbox, etc.).

M

(c) The option of batch uploading for migration of digitized assets and their metadata.

M

(f) Ability to upload large files.

List the maximum size file that can be uploaded, and the process for uploading large file sizes.

M

(g) The ability to upload, host, retrieve, display, and play multimedia including photographs, streaming video, archived webpages, and audio, as well as emerging formats, including:

9. HTML files (not simply HTML links)

List all available formats and their version numbers.

D

(h) Convert and export digital asset records (typically in Dublin Core) to MARC format, including links to the underlying digital asset(s).

Describe how the system complies with this requirement or explain why it does not comply. Please also list which MARC specific fields are included, and the inclusion of any crosswalks/converters, such as Dublin Core/MARC.

D

(i) The ability to export digital objects/assets and their metadata without an additional fee.

Describe how the system complies with this requirement or explain why it does not comply. Please also list which export file types are included and the process for export.

D

(j) OCR capability to ensure that digital objects can be searched in full-text (where applicable).

Describe the process for applying OCR to files where there was no prior OCR applied.

D

(l) Ability to create ad hoc, customizable reports covering both administrative and patron statistics.

D

(m) Preservation and risk management features such as checksums, data validation, permissioning of specific collections to various user groups, and backup/data recovery capabilities.

D

J.2.2.8.3. Metadata Handling

The system shall provide the following metadata capabilities:

(b) The ability to apply metadata to more than one digital object—one-to-one and many-to-one relationships for groups of objects or entire collections.

M

(c) Ability to support embedded metadata in JPEG, PDF, and other digital assets.

M

(d) The ability to handle a variety of metadata types (descriptive, administrative, technical, preservation, structural) for all record formats in the collection.

Include a full list of all metadata types and fields included in the system.

D

(e) Metadata format(s) compliant with archival standards such as extended Dublin Core, with the ability to include customizable metadata fields.

D

(f) The ability to create and use metadata templates via web-based forms.

Describe how the system complies with this requirement or explain why it does not comply. In addition, state which metadata standards are supported for these templates/forms.

D

(g) Ability to match metadata to controlled vocabularies; both those provided by the Contractor and those created by the library staff for searching.

D

(h) Controlled vocabulary: the ability for staff users to add and edit vocabulary terms within the system.

D

(j) Include advanced autocomplete and autosuggest functionality

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically state whether search terms can be pre-loaded, or if the search becomes more robust as more users search.

D

(k) Include autocorrect and “Did you mean…?” functionality

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically state whether search terms can be pre-loaded, or if the search becomes more robust as more users search.

D

J.2.2.9. Collection Analysis (Optional)

(a) The system offers the ability to analyze the collection and compare it to benchmarks, authoritative lists, or other institutions.

Briefly describe the capabilities and mechanism of the system’s collection analysis and evaluation functions.

D

J.3. PATRON-FACING FUNCTIONAL REQUIREMENTS

Patron-facing parts of the solution shall:

(a) Provide an interface that will be patrons’ primary point of entry into Census Bureau Library print, electronic, and digital collections that are cataloged and, where applicable, stored, in the back-end.

M

(b) Where applicable, provide seamless linking from the interface to digital assets.

M

(c) Provide a single patron account that includes all library functionality under a single set of authentication credentials.

Describe how the system complies with this requirement or explain why it does not comply. In addition, state whether a single account is provided via single sign on or another method, and the acceptable formats for usernames, passwords, barcodes, pin numbers, etc.

M

(d) Integrate with EZ Proxy account management.

M

(e) Provide immediate, seamless transfer of item and patron data from the LSP to the interface, without the need to run reports manually or take any other action to update the system.

Describe how the system complies with this requirement or explain why it does not comply. If the transfer of information is not in real-time, explain the timeframe for updates to be visible from one system to the other.

M

J.3.1. Discovery System Web Integration and Customization

If provided, the Discovery system shall:

(a) Be content neutral and allow library staff to designate the order in which vendor-supplied content appears in search results.

Describe how the system complies with this requirement or explain why it does not comply. Also explain the timeframe for these changes to become active.

M

(b) Have a proprietary central index that includes content from a wide variety of vendors.

Include a list of all vendors/databases that are centrally indexed.

M

(c) Allow for indexing of and access to Special Collections, archival items, and digital objects.

Describe how the system complies with this requirement or explain why it does not comply. If the system complies, please describe how this functionality works, what item types are included, and how metadata is harvested from special collections. Please also describe how users are led from the Discovery listing of the item to the either a) a link to more information about the item or b) a link to the underlying full-text document or digital object itself.

M

(d) Allow for relevancy ranking of search results, and the ability for the library to customize that ranking.

M

(e) Supply APIs, widgets, and other embedded code that allow for the integration of Discovery search forms, canned searches, and other web applications into third party interfaces.

M

(f) Provide customization options, including the ability to set default options (limits/facets) such as which databases and/or collections are searched.

Describe which specific fields/sections are customizable directly by Library staff, and which fields/sections can be set with default options. Please also describe in detail how branding and styling can be modified.

M

(g) Provide branding and styling options.

Please describe in detail how branding and styling can be modified. Include information on any support for branding and styling through CSS, JavaScript, and any other web design tools or languages.

M

(j) Include an OpenURL resolver.

Describe the OpenURL resolver functionality.

M

J.3.2. Discovery System Search

J.3.2.1. Search Capabilities

The following content shall be indexed and searchable by the Discovery system if provided:

J.3.2.2. Search Functionality

The search functionality of the Discovery system shall:

(a) Allow for a variety of search types and the customization of the number of fields that can be searched and limits that can be set on each field.

Describe how the system complies with this requirement or explain why it does not comply. In addition, list what search types are available (keyword browse, keyword search, title search variations, full text search when applicable, etc.)

M

(b) Include expert searching features, such as Boolean logic, for researchers who require more control in formulating search statements.

M

(c) Include advanced auto-complete, - auto-suggest, and auto-stemming functionality.

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically state whether search terms can be pre-loaded, or if the search becomes more robust as more users search.

D

(d) Include autocorrect and “Did you mean…?” functionality.

Describe how the system complies with this requirement or explain why it does not comply. In addition, specifically state whether search terms can be pre-loaded, or if the search becomes more robust as more users search.

D

(e) Include synonym expansion, stop word filtering, and vernacular search and retrieval, and character normalization.

D

(f) Include both a single search box, and an Advanced Search that allows user to search by:

20. Other customizable fields

List all additional customizable fields.

D

J.3.2.3. Search Results Display and Limiting

When displaying and limiting search results, the Discovery system shall:

(c) Allow users to sort results by relevancy, publication date, title, author, collection, or other criteria that are configurable by the library.

M

(d) Provides near seamless e-book integration (the user clicks on the e-book title, and gets directly to the full-text e-book within 1-2 clicks)

M

(g) Allow for certain bibliographic records to be suppressed in the Discovery system, but visible to library staff in the LSP.

Describe how the system complies with this requirement or explain why it does not. Include information about how staff can change the timeframe of this suppression, and if it can be suppressed permanently.

D

(h) Display a results list where the order of results, and the order of information within each result, can be customized.

Describe how the system complies with this requirement or explain why it does not comply

D

(i) Display a results list page that shows the following information per bibliographic and/or other type of item/record:

2. Brief summary/description

Describe how the system complies with this requirement or explain why it does not comply. Please describe the source(s) of these descriptions (i.e. from the MARC record or third party sources) and if additional fee applies.

M

3. Book jacket art (small or thumbnail size)

Describe how the system complies with this requirement or explain why it does not comply. Please describe the source(s) of these descriptions (i.e. from the system itself or third party sources) and if any additional fee applies.

M

7. Links to full text, digital object record, or an external URL from the 856 field.

M

(j) Allow user to limit/refine search results by the following facets/filters:

6. Format, including the ability to limit by print book or ebook.

M

13. Other customizable fields

Describe any additional fields that can act as search limits. Also describe the Library’s ability to configure which fields are used as limits.

M

(k) Display an item description page that shows the following information per result:

5. Book reviews (both professional and user-generated)

Describe any third-party vendor suppliers of book reviews, and whether additional fees apply.

D

(o) Integrate with Springshare’s LibGuides and LibCal products.

Describe all available integrations, and any actions the library must take to enable these integrations.

D

J.3.3. Digital Collections and Assets

For patron viewing and use of digital collections and assets/objects, the system shall provide:

(a) Branding and customization options.

M

(b) Detailed digital asset item records.

M

(c) Ability to organize content by collection and allow patrons to browse by a variety of access points.

Describe how the system complies with this requirement or explain why it does not comply. List the access points by which patrons can browse.

D

(d) Ability to display digital objects in collection groupings.

D

(f) Advanced digital asset and multimedia functionality, including:

6. Display and playback of multimedia files. System shall include an embedded multimedia player that allows users to listen and view audio-visual materials directly from search results. The embedded audio and video player shall be HTML5 compliant, including Flash fallback. It should support responsive design, keyboard control, and subtitles.

D

(g) Simple and advanced search options, including:

7. Complex search strings

M

(h) Simple and advanced search limit options, including:

J.3.4. User Personalization and Interaction

J.3.4.1. User Discovery Accounts

If provided, patron/end user Discovery system accounts shall:

(c) Allow for combined patron Discovery and Library accounts.

M

(e) Allow patrons to create and save, print, share, or export single items or lists of items to citation management, word processing or other productivity software.

M

(f) Allow patrons to edit contact and other information.

D

(h) Offer the capability of creating and retaining customized queries/search strategies when logged into the system. For example, patrons can create folders for frequent searches.

D

(i) Alert authenticated patrons to newly cataloged items via RSS or e-mail alerts.

D

J.3.4.2. User Library Accounts

Patron/end user Library accounts shall: