Integrated Library System

Provide an integrated library system that meets the needs of both an academic library and a modern public library.
- System Administration Requirements:
1. Full SIP2/ESIP functionality conforming to version 2 or higher; SIP2/ESP functionality is required for these third-party vendors at present:
a. Comprise Technologies
b. Convergent
c. Hoopla
d. iTiva/Illion (Telemessaging)
e. OCLC - EZProxy
f. OCLC – MuseumKey
g. Overdrive
h. TechLogic
2. Vendor must provide documented, secure API and/or web service capabilities for core ILS functions and data required to support thirdparty integrations, reporting, and system interoperability.
3. Vendor must support a documented database backup, recovery, and maintenance strategy that includes full and incremental backups, transaction log protection where applicable, backup validation, retention schedules, recovery procedures, and protection of any critical application, operating system, configuration, or system files required to restore the solution
4. Observability and application performance monitoring (APM) via the library's Nagios server, including installation of the NCPA and/or NRPE clients as necessary
5. Development environment for testing configuration changes, upgrades, new features, third party connectivity and backup verification
6. On-prem backups of full DB dumps, transactions logs and any other critical OS / system files
7. Flexible tool for exporting MARC bib, item & transaction data to be used by third party services
8. Flexible tool for exporting borrower data
9. The solution must run in a virtualized environment
10. Accessibility to meet Colorado’s legal standard of WCAG 2.1, level AA for all ILS modules, including staff modules, the public catalog, mobile app for patrons, and mobile app for staff
a. Vendors must provide VPAT (Voluntary Product Accessibility Template) documentation
11. Vendor must also meet HECA (Higher Education Compliance Alliance) requirements
12. Fully functional self-service reporting & statistical capabilities
13. System must provide self-service reporting, dashboards, and statistical reporting tools that allow authorized staff to create, modify, schedule, export, and share reports without vendor assistance
a. Reporting must include access to core ILS data, including circulation, patron activity, collections, holds, items, cataloging, acquisitions, usage statistics, and system activity where applicable
14. A fully web-based staff client
15. Mobile app for staff
a. App must be native iOS and Android or have a mobile-responsive web interface
b. Ability to perform remote circulation and inventory, and search the catalog
16. Mobile app for patrons
a. App must be native iOS and Android or have a mobile-responsive web interface
b. Ability to meet library branding standards
17. Read/write programmatic access to the database via API or ODBC, Python is the current preferred language
18. Read/write access to the database via SQL client
19. System must support granular, customizable permission levels across all staff modulesSystem scalability & data capacity – must accommodate the combined WPL + FRCC bibliographic, item, and authority databases without loss of data or functionality.