Specifications include, but are not limited to:Product Description – Required Components 1. General Overview: Describe the functionality, development, and enhancement of the system, paying particular attention to the following. a. Library and industry standards, formats, data types, and protocols supported. b. Copyright compliance and access control. c. Testing for adherence to accessibility guidelines and standards. Provide documentation of the testing performed and results of that testing, including a Voluntary Product Accessibility Template (VPAT). d. The number and sizes of academic libraries where this system is currently running in a production environment. e. Offeror’s track record of developing and implementing integrated library management systems. f. Offeror’s relationship with the vendor(s) of any third party tools ( i.e., reporting tools, application server and DBMS vendors, etc. ) included in this proposal including licensing, costs, support for the product(s), and versions ( e.g., full or modified ). Provide pricing in section Attachment E Pricing Schedule of this RFP. g. Active user groups and how they function. h. Development methodology used for your system. Give details about the testing phases, and the roles of the people involved in the development of the software. i. Process for determining enhancements that will be made to the application software. j. Standard and proprietary APIs, integration/connection resources, and development languages and tools that extend your toolset. Specifically, explain your system’s potential for integration with other systems using Learning Tools Integration specification (http://www.imsglobal.org/lti.) Provide details for all functions of the system that can take advantage of APIs, including acquisitions, e-resources, metadata/cataloging, circulation, discovery, end-user interfaces, mobile interfaces, collection reporting, and digital content management systems
