20180126_Item1_ProductDescription_WebBasedDiscoveryProduct.docx

Product Specifications with Salient Characteristics

PRODUCT: WEB-BASED LIBRARY DISCOVERY PROGRAM

A. Product Specification for Web-Based Library Discovery Program Requirements. This requirement is for an UNCLASSIFIED Web-based Library Discovery Program that will operate in a consortia environment; creating the Discovery layer of the federated Army University (ArmyU) Library Enterprise System. The ArmyU Library Enterprise System is combining 13 stand-alone libraries (three of which are combined academic and public libraries) into a unified Library Management Services (LMS) platform. This requirement is for the off-the-shelf Web-based Discovery Program that will result in 14 iterations of the Web-based Discovery Program (i.e., one each for the 13 libraries and one over-arching enterprise ArmyU layer. The Web-based Library Discovery Program will respond to the needs of all users, from the novice to the expert, applying searches across different resource silos to find high quality, relevant content. Search results will be fast and accurate. The interface will allow individual libraries and the ArmyU Library Enterprise System consortium to customize the user experience.

B. Characteristics:

1) Federated search capabilities for online public discovery and at a minimum access via:

a) Functional Requirements for Bibliographic Records (FRBR)

b) Faceted searching

c) Spelling and search suggestion

d) Z39.50

2) Program must provide citation tools:

a) Email

b) Print

c) Export to RefWorks citation manager as well as other citation manager software, such as Zotero, EndNote, or Mendeley.

3) Program must include capability to add new institutions over time.

4) Program must provide ability to integrate internal repositories.

5) Program must provide architecture of data storage and redundancy (for example, multi-tenancy, cloud distributed, etc.).

6) Program must provide support for various web browsers across multiple platforms (e.g., Windows, OS, Android, others) for both Staff and end-users, specifically Internet Explorer and Edge, Mozilla FireFox, Chrome, and Safari and provide support for two earlier versions of listed browsers.

7) Program must be currently deployed and operational in at least three (3) academic library consortia and the vendor must include the name of three (3) institutions who are currently using their discovery layer. One must be a multi-library system who migrated to their product from a different vendor's discovery layer. All references will include the name and address of the institution/agency, as well as the name of the contact person of the director.

C. Data Formats and Indexing

1) Program must support technical integration with content providers and various Digital Rights Management (DRM) systems, e.g. at a minimum, Overdrive, Adobe Digital Editions, Adobe Content Server, Ebrary, Safari, iLibrary, EBSCO, Janes Defence, Proquest, LexisNexis, DTIC, and digitized content and online archives repositories such as OCLC ContentDM. Vendor must provide a list of all current content providers capable of interfacing with product.

2) Program must fully integrate with multiple Integrated Library Systems such as SirsiDynix (Symphony, Horizon, Unicorn), Innovative (Sierra, Millennium Classic, Virtua, Polaris), OCLC (WMS, SISIS), ExLibris (Alma, Aleph, Voyager), and Library World. Vendors must supply a list of the supported Integrated Library Systems and explain how their discovery solution would interact with the Integrated Library Systems from the listed vendors.

3) Program must provide comprehensive knowledge base that is automatically updated when vendors change metadata and content in their proprietary databases (e.g. resources from vendors such as ProQuest, EBSCO, Jane's Defence, LexisNexis, and others). Knowledge base must also be library-editable for additions of non-standard resources for complete integration and indexed discovery and access to all licensed and local-databases, and eBooks, eaudio-books, etc.

4) Program must integrate standard reference tools (such as SpringShare [Company] LibGuides) into discovery search and results.

5) Program must provide A-Z journal title search/list.

6) Program must provide open URL link resolver.

7) Program must support one or more single sign-on authentication providers, i.e.:

a) Central Authentication Service (CAS 2)

b) Shibboleth SAML 2

c) EZproxy®

d) OpenAthens

8) Program must support integration with existing identity stores (e.g. Active Directory and Lightweight Directory Access Protocol (LDAP)).

9) Program must have the ability to import metadata from records such as MARC, EAD, MODS, METS, TEI, KBART, Dublin Core, etc.

10) Program should have ability for all libraries to be able to login via IP authentication.

D. Branding, Local Library Customization and End User Personalization

1) Program must provide the ability to opt in or out of available resources such as but not limited to Open Access eBooks (such as the HathiTrust), journals, and textbooks.

2) Program must have the ability to integrate with Learning Management Systems, such as Blackboard, Moodle, etc.

3) Program must provide ability to create a customizable “LibGuide like” roll-up of all library resources through a single search.

4) Program must include a fully integrated dynamic web content management system (CMS) to create, manage, and host library websites.

5) Program must allow staff to completely customize websites with ready-to-use themes, drag-and-drop page layouts, and fully customizable blocks with CSS override; and, include the ability to pull together curated lists of electronic and physical items (to include cover art), and local and web content quickly and with minimal effort.

6) Program must provide web interface architecture that is platform agnostic and provides interfaces for mobile devices (e.g., responsive design; options for using the public interfaces with mobile devices) and provide a responsive web design (RWD) to accommodate various device platforms.

7) Program must provide ability to create multiple dashboards for collaborative research and to create and customize enhanced searching interfaces such as “expert.”

8) Program must provide ability to manage locations, users, content creation, etc. through a single interface.

9) Program must provide web services Application Program Interface (API) at no additional cost.

10) Program must provide ability to create customizable controlled vocabularies used throughout site to filter content.

11) Program must provide patron personalization tools, such as saved searches, reading lists, etc.

12) Program must provide separate interfaces depending on patron type.

13) Program must provide ability to search for and request materials from across member libraries.

14) Program must provide ability to limit search to a particular library or collections within a library.

15) Program must provide ability for individual libraries to customize searches/scopes such as searching journal titles, reference books, or new books.

E. Accessibility

1) Program must be WCAG 2.0 Level A and Section 508 compliant.

2) Program must provide fully cloud-based architecture and hosting that does not require use of any locally-installed vendor-client software on customer equipment.

3) Web-based program must be deployed and maintained in accordance with current DOD and industry standards, including:

a) Third party access to the environment must be vetted and monitored per company policy and access is immediately disabled once no longer needed or when access is determined to be inappropriately provisioned in accordance with third party or service provider agreements.

b) Software must operate in a Family Educational Rights and Privacy Act of 1974 (FERPA)-compliant environment or a demonstrated equivalent

c) Software must provide encryption of data between server and client.

d) Software must provide granularity of security options for library staff and faculty.

F. Customer Support Model

1) Vendor shall require any patron accessing her/his system account information to go through a strongly encrypted authentication method to ensure minimal security risk (such as Secure Hypertext Transfer Protocol connection or HTTP over Secure Socket Layer).

2) Vendor shall provide basic telephonic/email 24/7 help desk support to mitigate and resolve problems quickly and accurately with minimum downtime (not to exceed 0.4% downtime on any given day without advance customer notice). Shall accept support requests from any consortium member library and from consortium central staff.

3) Vendor shall provide tiered-level support 24/7 (this is more than basic 24/7 help desk) to allow customer to submit questions and issues by phone or email and receive acknowledgement; allow staff to submit configuration and design issues; and allow staff/customers to track status of their issues in a tracking system or monitor log system.

4) Vendor shall provide ongoing staff customer support to include system troubleshooting and configuration issues, application advice, and design planning questions during normal hours of TRADOC operation by telephone or online.

5) Vendor shall provide standard access to their online and telephonic training to the TRADOC/ArmyU Enterprise and Center/School Library staffs.

G. Electronic Delivery

1) Program must provide the ability to add customizable public notes to items such as copyright restrictions, number of views left on limited eBooks etc.

H. ERM, Reports and Statistics

1) Program must support management and display of license terms and conditions in machine-readable format to include linkage to digital resources; communicating key usage terms to users and staff; and comparing terms across different licenses on the local and consortial levels.

2) Program must provide ability to upload and edit publisher(s) license documents and view history of edits/versions on the local and consortial level.

3) Program must provide the ability to ingest and manage usage statistics for electronic resources and to create standard library reports at the local and consortial levels, including COUNTER and SUSHI.

4) Program must provide ability to create surveys, polls, and web forms quickly and include a robust submission analysis and reporting function.

I. Frequency and Intervals of Updating

1) Program must reflect administrative changes in the discovery results (e.g., turning on and off databases and customization of the interface) within 1 working day.

2) Vendor shall provide a protocol to document and promptly assist customer with expunging/removing any links to documents and/or data sources from the Discovery Knowledge Base and/or search results that contains "restricted/classified" government information (for example WikiLeaks releases)

J. Implementation Timeline

1) Vendor must provide a sample implementation timeline for a consortium of similar size to ArmyU Libraries Enterprise System (i.e., 13 geographically separated libraries with a combined FTE of over 38,000 and over 114 staff.