Primo
Your feedback matters to us. Help us improve Primo by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
700 results found
-
Drag-and-drop to reorder search-criteria rows in Primo VE Advanced Search
As an end-user building a complex multi-line advanced search, I want to drag any criteria row to a new position so that I can quickly reorganize my query without deleting and re-typing fields.
I'd imagine a little click-drag icon on the left that the user could use to re-order query fields. I found an example built in react at https://react-querybuilder.js.org/demo , screenshot attached.
3 votes -
Journal Title Facet Should Include Local Records in Blended Scopes
Currently, the Journal Title facet in Primo only applies to records from the Central Discovery Index (CDI), excluding locally cataloged article records and those imported from external sources such as institutional repositories. This behavior leads to inconsistent and confusing results for end users, especially when using a blended scope that includes both CDI and local records.
Problem:
Users conducting searches—particularly in the local language—often retrieve a significant number of local article records. Despite these articles being published in journals, their journal titles do not appear in the Journal Title facet.
Users are unaware of the distinction between CDI and local…3 votes -
Enhancing visibility of Open Access indication for CDI article records
Problem:
[see 1OAPrimo.png] Currently, the Open Access indication appears under a title in Primo for Open Access CDI article records, which can confuse library users. They might think that all collections under "View Online" are all full-text open access.Idea: To enhance clarity for users, we recommend first configuring Alma settings to control the display of the Open Access indication, followed by adjustments in Primo.
[In Alma] [see 2OAPrimo.png] We propose adding a tick box or a dedicated field within the service level settings to indicate open access. When enabled, this setting will control whether the OA indication appears.
[In…
3 votes -
Granular Control for Alma Viewer and Digital Versions Tab in Primo NDE
Description:
In Primo NDE, the rule “Hide service: Representation Delivery Service” affects both alma-viewer-content and the Digital Versions tab (nde.brief.results.tabs.digitalVersions). In contrast, Primo VE allows institutions to independently control visibility of the Alma Viewer and the Digital Versions tab.
This enhancement request seeks to restore this level of granular control in Primo NDE. Specifically, institutions should be able to:
Hide the Alma Viewer for certain representations (e.g., auxiliary or restricted content)
Still display the Digital Versions tab for those same representations
This would provide the flexibility needed for managing multiple representations of a record while ensuring users can discover digital…
3 votes -
Configure page metadata (browser tab title) across key pages independently from the main menu labels
In Primo NDE, the browser tab title (the HTML <title> element) for many pages uses the same label as the top menu, e.g., ILL request forms, Citation Linker, Collection Discovery, Purchase request form.
Screenshot with label codes toggled on to demonstrate the same label used for different functions
This means that the title in the tab cannot be independently customised to act consistently with other areas of Primo (search and my library account where separate labels can be managed). This creates issues:
Usability:
- Users with many collection discovery tabs open cannot distinguish which collection is in each tab. Users sharing…
3 votes -
Make "patron default sort" an optional feature
Please allow customers to disable the Patron Default Sort feature. [1]
Since this feature was added to Primo last year, we are regularly contacted by perplexed users wondering why relevancy ranking isn't working. Invariably, the users had selected a different sort option the last time they used Primo and did not realize that Primo would remember their sort options in the future.
If there are no plans to implement this feature in NDE, please disregard this request.
3 votes -
Make advanced search and natural language search terms visible for Primo NDE in portrait view of mobile phone devices
At present, when a user undertakes a Natural Language search or Advanced Search in Primo NDE on a mobile phone in portrait mode, the search query is not displayed however this is being displayed when viewed in landscape mode.
User's may not know to change the orientation of their device to see this information.
Support case #10573480 created with ExLibris responding as follows:
"Due to UX considerations and current UI limitations in the mobile view, the advanced query search terms are not displayed. This behavior also applies to natural language searches. At this time, there are no plans to change…3 votes -
DC record mapping to Journal Title, RIS Volume, Year, Issue
Based on the current Primo VE documentation, both dcterms:isPartOf and dcterms:bibliographicCitation may be used in the mapping to the addata section. These fields can also be used for extracting host information, such as volume, issue, and year, when the value is formatted accordingly.
The problem is with keeping the journal title in dcterms:isPartOf (for example, Technologies) and place the enumeration value (for example,14(2026)2) in dcterms:bibliographicCitation is that it override the Journal title in the RIS and display the enumeration instead. (See RIS export below). It is currently a limitation in mapping to extract Journal title to JF and volume, issue…
3 votes -
Make it possible to show suppressed bibliographic records in the collections lobby
We have a large collection where we only want to make a select number of more academic titles discoverable in Primo search so that library users aren't overwhelmed with irrelevant content.
It would still be good to make all titles in the collection discoverable through an alternate means, however it isn't possible to add these to the collections lobby without these appearing in Primo search. The collections lobby only shows titles with unsuppressed bibliographic records. Can we make an option to allow suppressed records to be viewed in the collections lobby?
3 votes -
Black theme for customization color theme
In the customization color theme of Primo NDE, black (hex #000000) is not one of the 17 colors you can choose.
Many institutions will have black as the main color in their designguide - for menu, text, icons, element details etc.
Please develop this option in customizatition color theme.3 votes -
Provide method for users to opt out of Mixpanel tracking (NDE)
Users should be able to opt out of Mixpanel data tracking. Although the data sent to Mixpanel is appropriately anonymized, libraries tend to want to allow users to opt out of various tracking mechanisms. Opt-out should be persistent across sessions via a browser cookie or local storage.
3 votes -
Metadata from Database Link Resolver into the Resource Sharing request form
Allow more metadata from Database Link Resolver into the Resource Sharing request form to ensure the library staff can more easily fulfill the request and patrons are well-informed through notifications of the exact item they have requested - for example a specific chapter from a multi-chapter book written or edited by someone other than the chapter's author. Having the Book Title, Chapter Title, Book Editor/Author, and Chapter Author would be helpful especially for our faculty patrons.
3 votes -
Suppress controlled vocabulary expansion notification when expansion has no impact on results
When a search triggers controlled vocabulary expansion but the expansion term contributes zero results, Primo VE still displays the message informing the user that the search has been expanded, and offers a link to disable the expansion (conVoc=false).
Clicking this link produces no observable change in the result set, since the expansion was not contributing any results in the first place.
This creates a confusing experience for the user:
1. The system implies the search was meaningfully expanded
2. The user is offered the option to opt out
3. Opting out has no visible effectProposed improvement:
The expansion notification…3 votes -
Enable ability to increase number of autocomplete rows that appear in the dropdown in Primo VE
In Primo VE the dropdown that appears when entering search terms in simple search is limited to 8 rows. The top rows are taken up with suggestions for each of the search scopes that have been defined and the remainder are used for autocomplete suggestions. If there are a higher number of search scopes defined then there are less spots available for autocomplete suggestions.
For example Otago has 6 search scopes defined which only leaves space for two autocomplete suggestions to appear in the dropdown. https://www.screencast.com/t/9mrmza2gMUaG
We would like the ability to increase the number of rows that appear in…
2 votes -
Allow Primo users to report inaccurate metadata on a record directly to Ex Libris
We've had several cases where metadata was incorrect in a Primo record. The user (in several occasions the author of the article) reported the issue to their library, who reported it to us (BIBSYS consortium), and we reported this to Ex Libris.
Once the issue was fixed, after quite some time, the feedback followed the same road, back to the user.
It would be more efficient if metadata issues could be reported directly to the instance actually able to correct them, which is Ex Libris.
The issue would be reported directly by the user in Primo/a salesforce case would be…
2 votes -
Custom location order in brief results list
Where there are multiple records for the same holding within our institution, we would like to configure the order of locations in the brief results. Patrons could then see the circulating items first, rather than non-circulating items, reducing confusion and wasted time.
This is similar to #32961133, "Ability to select which location appears first." The resulting Location Ordering Profile allows us to set a custom order within a single record, which is very helpful. But it does not solve the problem where there are multiple records.
2 votes -
Show last edit date in Manage Customization Package tab for Primo VE View
Currently, the manage customization tab shows no information about when the package was last updated. I suggest adding information in the display area that shows "Package last updated: YYYY-MM-DD," preferably with the user's id.
2 votes -
Integrated with ChatGPT technology
Good to integrate ChatGPT technology in Primo VE.
2 votes -
Add ability to control local record access information in Primo
Primo managed via Back Office has powerful functionality to control access information in Primo for all our local records.
This includes the aligned features of availability statements and Get It / View It by Delivery & Scoping rules, Links rules for all harvested data sources, and the option to build custom mapping tables for references in various rules, all of which can be married with top level facets by Facet rules.These features provide necessary information in Primo as expected for a core discovery layer functionality of advising users how they can access and request our resources, and avoids wasting…
2 votes -
Feedback Tool for Primo VE - ability to disable categories
For the Primo VE Feedback Tool, we would like to have the ability to disable the email form so that we can link instead to our existing form and chat service from the report.generalText bubble. Basically, we would have zero categories/issue types configured so that the email options would not be presented to the user. The user would only see the report.generalText bubble (see edited screenshot attached).
2 votes
- Don't see your idea?