Library Discovery System

The vendor is required to provide that library discovery system primo VE, to the new alma-based discovery system will involve a comprehensive approach to data migration
- This includes the extraction, transformation, and loading (ETL) of essential data such as bibliographic records, user information, and system configurations, ensuring a complete backup of all data before proceeding.
- This system will serve over 250,000 students, faculty, and staff across more than 30 libraries, offering a unified platform for accessing the wealth of resources available within our consortium.
- The proposed discovery system must:
• Integrate with alma, enabling real-time synchronization of bibliographic data, holdings, and item availability; automating processes; providing consistency between it and alma; ensuring reliability; and offering high performance
• Support centralized configuration and management through alma, reducing administrative overhead and improving efficiency.
• Provide a single search interface that facilitates the discovery of all library resources, including physical items, electronic resources, and digital collections
• By unifying resource discovery, the system will simplify the search process for users, making it easier for them to find the materials they need, regardless of format or location
• Feature a modern, responsive user interface that is intuitive and user-friendly.
• It must be optimized for both desktop and mobile devices to accommodate the needs of our students and faculty who increasingly access library resources on the go
• Support data-driven decision-making by including integrated analytics tools via a dedicated interface within alma, allowing library staff to easily access and interpret the data without needing to switch to external systems.
• Provide insights into user behavior, search patterns, and resource usage, enabling library staff to make informed decisions about collection development, user services, and resource allocation.
• The interface must support role-based access control, inherited from alma, to ensure appropriate data access for different staff roles
• The search results must be ranked according to relevance and include features like spell-check, auto-suggest, and search term highlighting
• Customization is a key requirement for the proposed discovery system.
• Libraries must be able to tailor the interface to reflect their unique branding, configure search scopes, and adjust ranking algorithms to prioritize specific collections or resource types.
• Support linked data principles, enhancing the discoverability and interoperability of library resources by connecting them to related information on the web
• Provide users with a richer context for the materials they find and open up new avenues for research and exploration.
• Comply with international, national, and state accessibility standards, providing an inclusive experience for individuals with disabilities
• This includes support for screen readers, keyboard navigation, and other assistive technologies.
• Ensuring accessibility for all users is a fundamental requirement.
- Project planning and management:
• Project plan with timetable for deliverables and deadlines
• University resource plan including campus representatives
• Weekly status reports
• Issues and risk logs
• Communication plan
• Steering committee charter
- Requirement’s validation and proof of concept
• requirements document including:
1. Library system (alma) integration requirements
2. Campus-specific needs
• Proof of concept implementation report
• Gap analysis document
• Configuration templates for different campus types
- System installation and configuration
• Application configuration document
• Security configuration document
• Installation checklist
• Environment setup documentation
• Customization documentation for local branding
- System integration and interface(s):
• Library system (ALMA) integration configuration document
• Functional design documents
• Technical design documents
• Authentication integration plan
• API implementation guide
• Integration testing plan for:
1. Link resolver
2. Institutional repository
3. Resource sharing systems
4. Reading list systems
- Data migration
• Data migration plan document including:
1. Library system (alma) data mapping
2. Saved searches migration plan
3. Local holdings migration plan
4. Custom metadata fields mapping
5. Digital collections migration plan
6. Historical usage data migration plan
• Test migration results report
• Data validation procedures
• Rollback plan
- Testing:
• Test plan and scripts
• Performance test results
• Campus testing schedule
• Defect tracking log
• Load testing report
• Browser compatibility report
- Training materials
• Training materials for:
1. End users (basic/advanced)
2. Public services staff
3. Technical services staff
4. Systems administrators
• Quick start guides
• Video tutorials
• Self-paced modules
• Configuration workbooks
- Training sessions:
• 12 training sessions including:
1. 8 public services staff sessions (2 hours each, 20 staff per session)
2. 2 technical services sessions (3 hours each, 15 staff per session)
3. 1 system administrator session for office of library services staff (4 hours)
4. 1 custom feature session
• Training recordings
• Hands-on workshop materials
- Production deployment
• Risk assessment checklist
• Deployment strategy document
• Campus-specific deployment checklists
• Rollout schedule
• Go-live support plan
• Post-deployment audit checklist
- Ongoing maintenance
• Service level agreement
• Quarterly performance reports
• Scheduled maintenance plan coordinated with library system (ALMA) maintenance
• Enhancement request process
• Incident response plan
• Change management procedure
- Contract Period/Term: 5 years
- Questions/Inquires Deadline: February 28, 2025