Library Web Services

The Vendor is required to provide library web services for include:
- Content management system
•    Provide template-based guide and page creation with consortium-level and campus-level branding options 
•    Support reuse of content across guides and campuses, including shared assets, reusable content blocks, and system-wide database lists 
•    Support use of the content management platform as the primary public-facing website for individual campus libraries, including custom domain mapping, custom navigation structures independent of the guide hierarchy, and custom CSS and JavaScript injection, all configurable per campus without additional per-campus licensing fees 
•    Provide version history and the ability to restore previous versions of content 
•    Support draft, review, and published workflow states 
•    Provide mobile-responsive public-facing output across all content types 
•    Support an a–z database list with subject and type filtering, editable at both campus and consortium level
•    Support embedding of subject guides, course guides, and database lists directly into course shells via LTI 1.3 or higher, with seamless authentication through the LTI launch and support for lti deep linking 
•    Expose an OAI-PMH endpoint for guide content metadata supporting standard Dublin core output, compatible with ex Libris alma and primo VE import profile configuration, and configurable to expose metadata at the campus or consortium level 
•    Provide usage statistics at the guide, page, asset, and database-link level, exportable in standard formats
- Virtual reference and communication services
•    Provide real-time chat with queue management, including the ability to transfer chats between operators and campuses 
•    Support a cooperative or consortium chat model in which chats from one campus queue can be answered by staff at another campus, while preserving per-campus branding and per-campus reporting 
•    Allow chat widgets to be embedded in guides, library web pages, and course shells 
•    Support canned responses and a shared knowledge base of FAQs, editable at both campus and consortium level 
•    Provide an email-based ticketing system with queue management, assignment, and status tracking, with tickets creatable automatically from incoming email and from chat transcripts 
•    Archive all chat transcripts and ticket records, searchable by date, operator, campus, and topic, and retained for a minimum of three (3) years 
•    Provide usage analytics including chat volume, response times, and ticket resolution rates at both campus and consortium level, exportable in standard formats and sufficient for ACRL reporting 
•    In the cooperative chat model, display the originating campus branding to the patron throughout the session regardless of which campus's operator responds, support configurable fallback queues for after-hours routing without requiring the patron to re-initiate the chat, and provide operators with visibility into the patron's originating campus and the page or guide from which the chat was launched
- Scheduling, booking, and appointment services
•    Provide public-facing event calendars with self-service registration, configurable per campus, with calendar exports in ICAL format and integration with google calendar and outlook, and automated confirmation and reminder notifications to registrants
•    Provide self-service room and equipment reservation with configurable booking rules, approval workflows, and utilization reporting at campus and consortium level 
•    Provide appointment scheduling for individual librarians and service desks with configurable availability, automated patron communications, and per-librarian and campus-level reporting 
•    Provide service desk scheduling and shift management for library staff, integrated with the calendar and appointment services above
- E-reserves
•    Support the creation and management of e-reserves reading lists associable with specific courses, instructors, and terms 
•    Provide a faculty request workflow with library staff review, approval, and denial functions, and automated faculty notification 
•    Support uploading and secure storage of documents as well as linking to items in licensed databases 
•    Include access controls allowing restriction of reserve materials by course enrollment, password, or ip range, with automated visibility controls scoped to relevant terms or date ranges 
•    Include a copyright and permissions workflow for each item, with the ability to record copyright statements, fair use determinations, license terms, and permission status, and to display customizable copyright notices to users
•    Support embedding of e-reserves reading lists directly into course shells via LTI 1.3 or higher, with seamless authentication through the LTI launch 
•    Allow point-of-need integration within e-reserves views, including inline chat widgets and links to related subject guides 
•    Provide usage statistics at the course and item level, exportable in standard formats.

Questions/Inquires Deadline 1: May 12, 2026
Questions/Inquires Deadline 2: May 19, 2026