Primo Roadmap Highlights
Overview
The Primo roadmap provides a preview of what is planned for 2024 and what is expected to become available in the first and second half of the year. The roadmap is based on community feedback, ideas from the Idea Exchange, NERS voted enhancements, and strategic enhancements that serve longer term goals. This published roadmap focuses on the highlights. We may add other development items over time, which will appear in the release notes.
The information below represents our primary planned development. Roadmap items are listed by category and timeline, followed by additional details when available. If feature development and design is not complete, details will be available closer to release.
As we work closely with the Primo working group while designing some enhancements, we’ll deliver more relevant information to the community by sharing mockups, workflows, and additional details.
The content on this page is informational and may be subject to change without prior notice at the sole discretion of Ex Libris.
Related Information
Highlights by Category
The planned developments are organized by category. For additional details regarding a development, select its link:
User Experience (UI and functions):
-
Ongoing improvements
Library Empowerment – New Tools and Configurations to Expose Library Resources:
-
During the year, we plan to have an audit and fill out a VPAT to be in compliance with the new criteria of WCAG 2.1 Level A and AA.
-
Ongoing Accessibility – We make every effort to ensure that Primo can be used by everyone. It’s continually designed and developed to meet Level AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions. For more information, see Primo Accessibility Statement. Throughout the year, we fix accessibility items based on external audit results and customer feedback.
-
Ongoing Analytics – As Primo evolves and new functionalities are introduced, new actions will be added to Primo Analytics to help you learn more about your patrons' usage.
Highlights by Timeline
The following table lists the planned developments by timeline. For additional details regarding a development, select its link.
2024 H1 | 2024 H2 |
---|---|
Additional Details
Support Bulk Export of Search Results
NERS 2023 Request #8126
What's New? | Highlights | Impact |
---|---|---|
Ability to export a large number (thousands) of search results. |
|
Users can save and maintain their literature review outside the context of Primo. |
Allow HTML Coding in Labels, Public Notes and Collection Description
NERS Request #8134
What's New? | Highlights | Impact |
---|---|---|
Support formatting and link out to other pages using HTML coding for labels and public notes. |
|
Provide better user experience and workflow. |
Prevent Search Results Expansion Using Exact Phrase
NERS Request #8210
What's New? | Highlights | Impact |
---|---|---|
Limit exact searches to not expand the query using linguistic capabilities. |
|
Better search capabilities to improve the discovery experience. |
CDI Subject Headings and Keywords Normalization Refinements
What's New? | Highlights | Impact |
---|---|---|
Deduplicated and normalized CDI subject headings based on LCSH and MeSH controlled vocabularies. |
|
Eliminates user confusion leveraging familiar vocabulary schemas. |
Support Special Linking Parameters for Select Providers
What's New? | Highlights | Impact |
---|---|---|
CDI Quicklinks and Link in record links will use the customer linking parameters specified in Alma for each library. |
|
One-step configuration. |
Improve Book Review Identification
What's New? | Highlights | Impact |
---|---|---|
Book Reviews that were previously categorized as Articles by the match & merge process will now reflect their correct Content Type. |
|
Easier, more accurate identification of desired resources. |
Improve Handling of In Press Articles
NERS Request #8156
What's New? | Highlights | Impact |
---|---|---|
In Press articles that do not have sufficient metadata for linking (e.g. volume and issue) will be handled with special logic in Primo. |
|
Prevent broken links to content and avoid user frustration. |