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.
- or
No existing idea results
- ~ No ideas found ~
651 results found
-
API for customization package deployment
Please add an API to deploy customization packages in Primo VE so that customers with many views can automate the cumbersome deployment process.
103 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 automatically created. Each institution/consortium could configure to which already existing Salesforce account the answer to the case could be sent to. Institutions, and not Ex Libris, would still be in charge of following up with the user. In our case it would be useful to configure both the Salesforce account (BIBSYS consortium's) and who at the specific library would be in charge of following up with the user.
This way, issues would be reported immediately, which would decrease the time necessary to correct them, but Ex Libris would still communicate with the same salesforce users as before.
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 -
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 the autocomplete dropdown and/or to be able to choose which search scopes appear in this dropdown so that we can show more autocomplete suggestions. In Primo Back Office only tabs show in the dropdown and not scopes so that leaves more rows for autocomplete suggestions – Primo VE is more limited in this area.
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 -
enable a search of parentheses () in middle of word
Currently, Primo is unable to retrieve titles containing parentheses in the middle of a word (eg א(י)מניות : אימהות מביאות אמנות לעולם). It seems elementary that Primo should be able to retrieve any record based on its exact title.
See the following links displaying the issue:
3 votes -
Add Campus IP-address recognition for OpenURL display in Primo VE
When you set up Available For Groups on electronic collections in Alma, you can assign a Campus a certain IP-range and have Primo VE display the correct full text links without requiring the user to sign in first.
This is all good within the scope of Primo VE but when you come to Primo via an OpenURL this functionality does not kick in. Should not all links be created equal, you may ask? Apparently not.
This is a link from a search in Primo VE: https://snipboard.io/L5pvj6.jpg
And the exact same article via an OpenURL: https://snipboard.io/VadX1N.jpg
Please make OpenURL links behave the same as a search in Primo.
When you set up Available For Groups on electronic collections in Alma, you can assign a Campus a certain IP-range and have Primo VE display the correct full text links without requiring the user to sign in first.
This is all good within the scope of Primo VE but when you come to Primo via an OpenURL this functionality does not kick in. Should not all links be created equal, you may ask? Apparently not.
This is a link from a search in Primo VE: https://snipboard.io/L5pvj6.jpg
And the exact same article via an OpenURL: https://snipboard.io/VadX1N.jpg
Please make OpenURL links behave…
3 votes -
Configure new searches to automatically exclude facets from result list (2022)
As a user, I want to configure Primo to automatically exclude certain facets from search results so patrons do not have to exclude the item with every new search
The solution would be configurable.
The default configuration would have no exclusions defined.Using Resource Type: Reviews as an example:
- The institution uses the solution to exclude Resource Type: Reviews.
- The solution adds [facet=rtype,exclude,reviews] to the query. The behavior would be the same as if the user clicked the Exclude button next to the resource type: reviews.
- Users would be able to modify their filters like usual.
Query without configuration:
/discovery/search?query=any,contains,Carrots&tab=Everything&search_scope=Everything&vid=[institution code]&offset=0Same query with configuration:
/discovery/search?query=any,contains,Carrots&tab=Everything&search_scope=Everything&vid=[institution code]&facet=rtype,exclude,reviews&offset=02.5 years in and the solution to https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/16817620-exclude-include-reviews-from-resultlist from 2019 has not had the desired impact.
As a user, I want to configure Primo to automatically exclude certain facets from search results so patrons do not have to exclude the item with every new search
The solution would be configurable.
The default configuration would have no exclusions defined.Using Resource Type: Reviews as an example:
- The institution uses the solution to exclude Resource Type: Reviews.
- The solution adds [facet=rtype,exclude,reviews] to the query. The behavior would be the same as if the user clicked the Exclude button next to the resource type: reviews.
- Users would be able to modify their filters like usual.
Query without configuration:
/discovery/search?query=any,contains,Carrots&tab=Everything&search_scope=Everything&vid=[institution…22 votes -
Feedback Tool for Primo VE - allow user's email as addressFrom in Report a Problem Letter
The Feedback Tool for Primo VE (May 2022) would be even better if the user's email address could be put in the addressFrom field in the Report a Problem letter in Alma. Just as the category is put in the emailSubject field:
New feedback received from a Primo user - {category _ name}
allow the addressFrom field to contain:
{user _ email}
This would then work better with CRMs and ticketing systems, or just mean that you can hit Reply to the email.36 votes -
Make the DOI field on the Full Record page a link including EZproxy
Currently on the Primo Full Record page, the DOI field is not a link to the resource. Please make this a link with the option to prepend your EZproxy URL to the DOI links. (Summon added this feature in 2021.)
1 vote -
Allow patrons to submit ratings on records
We would like our (identified) patrons to be able to add a rating on each record, for example on a scale of 1 to 5 stars. This rating would be saved and displayed to all users on the full display of the record. A facet would be then allow to select records according to their rating.
16 votes -
Allow hosted Back Office sites to use their own XSL transformation routines in data sources
Primo documentation describes using XSL transformation routines to apply changes to records ingested to Primo from external sources (https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/Back_Office_Guide/050Pipe_Configuration_Wizard/040Configuring_Data_Sources) but hosted sites are not able to see details of existing routine files or add their own.
We would like to be able to add our own transformation file to handle a specific issue with harvested OAI metadata. Please make this possible or at least document the existing transformation routines so that we can see what they do.
0 votes -
holdings information search "starts with"
When searching for Holdings Information in advanced search then changing the operator option to "Starts with", changes the search to Title rather than holding information.
The "starts with" operator should only be an option when the user is using the Title Search operator.1 vote -
Collection Discovery : Add a button "View this collection as search results"
Beside the buttons to display a collection as a Grid or a Gallery, we would like to have a button to get the collection items in the result list, with the brief display and the facets. This could be a deeplink on the Collection ID with a "query=cdparentid" in the URL.
Please note that there exist two very close ideas:
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/36709789-add-facets-into-the-collection-discovery-ui
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37607257-collection-discovery-display-items-in-a-list-view
But this idea groups both features.Thank you.
104 votes -
Add 007 to MARC control identifiers for display and search normalization
This would enable normalization rules to target specific resource types.
In cases where MARC data may differ based on current practices (MARC 245 $c: Side B titles vs. Statement of Responsibility), we would be able to differentiate records that may contain uniquely catalogued data.
35 votes -
Allowing the "I only need a specific chapter or pages" checkbox to be defaulted to ticked.
With the introduction of RapidILL, we have defaulted our resource sharing request form to have a format of "Digital". For consistency, we would also like to be able to have the "I only need a specific chapter or pages" checkbox default to being ticked so this matches the format.
The client could then choose to untick (which changes the form format to Physical) if they wish to request a loan.
Thanks
Elizabeth1 vote -
Extend subject heading display masking to CDI records
Like many other institutions, we have used the subject display normalization rules for display to mask offensive subject headings with more preferable terms.
However, these changes do not impact the CDI records. We would like to see the changes we made in the subject display masking apply to the CDI records, whether through the same rule or through a new configuration option specific to CDI.
For reference: If anyone is interested in our documentation to see examples, it's available here: https://connect.library.utoronto.ca/display/CAUG/Subject+Masking+-+Go+Live
10 votes -
collection discovery
Currently grid items in Collection Discovery can show title, resource type and thumbnail. We would like to add creator/author and or creation/publication date if possible. My suggestion is to add configuration for changing what is displayed in the item grid elements in Collection Discovery.
85 votes -
Push record to Zotero
Add the Zotero reference manager as an additional action link in the "Send to" section, just like Mendeley or EndNote.
110 votes -
Translate coverage and licence labels for NZ full text services in IZ views
PrimoVEs in our network use 4 languages for the user interface - English, German, French and Italian.
Consortial and Open Access e-resources are activated in the Network Zone for all the IZs.
When viewing Full-text services from NZ in the detailed view in IZs, the coverage and license labels are not translated to the language of the user UI.
The absence of translation creates discrepancy for our users. The IZ FT services' labels are translated but the NZ services are always in English.104 votes -
Visualization of Analytical Bibliographic Data in PrimoVE.: Correct Sorting of Parts
A multi-part resource (eg: a sketchbook containing 200 drawings) is catalogued in MARC 773 (host/item relationship). PrimoVE ought to sort and display the component parts using $$g and $$q. Currently PrimoVE fails to do this in the correct numerical order. Rather, the presentation is alphabetical which is useless for component-items organized by their part or page number. There was a recent ideas exchange issue raised on this very topic, which was “solved” by providing the aforementioned “alphabetical solution”. However, a NUMERICAL visualization has much more value in Discovery for patrons who are interested in locating an item as part of a host (the drawing on page number 12 of a sketch book, for example). This is a frequent and conventional library requirement for example in Special Collections communities, as it reflects accurately the sequential order within an actual work or a manifestation.
Currently (SEE SCREENSHOT BELOW) the user sees this rather wild presentation in PrimoVE (the resource is the sketch-book of 200 drawings cited above).Another example from the world of monographs is a collection of Brecht’s works: currently looking like this in PrimoVE:
https://basel.swisscovery.org/permalink/41SLSP_UBS/1hbnn2v/alma993707790105504
The publisher’s website displays the correct sequence:
I do not consider this request an “enhancement” feature, rather a basic library requirement, dating back to the traditional card-catalogue-era.
Many thanks.
A multi-part resource (eg: a sketchbook containing 200 drawings) is catalogued in MARC 773 (host/item relationship). PrimoVE ought to sort and display the component parts using $$g and $$q. Currently PrimoVE fails to do this in the correct numerical order. Rather, the presentation is alphabetical which is useless for component-items organized by their part or page number. There was a recent ideas exchange issue raised on this very topic, which was “solved” by providing the aforementioned “alphabetical solution”. However, a NUMERICAL visualization has much more value in Discovery for patrons who are interested in locating an item as part of…
425 votesHi all,
This idea was reviewed as part of planning 2026 roadmap, as the solution yet is not clear and we are still examining the possible solutions.
This kind of sorting is more complex as it involves free text values and it requires different sorting method than what currently being used.
This is currently not included in the 2026 roadmap.
We will continue evaluate the possible solutions.
-
OpenURL resolving - BaseURL configurable for extension to consortial network
If an OpenURL request comes from external to Primo VE, then only the inventory in the IZ is considered and there is no possibility to extend the request to the physical inventory of the corresponding consortial network.
Suggestion for an enhancement: the BaseURL for OpenURL-request should be configurable in a way that the argument "consortial network" can be included in the request [i.e. with the configuration it can be decided whether only
a.) the inventory of the IZ (or Campus)
OR
b.) also the physical inventory of all libraries of the consortial network should be displayed (i.e. analogous to "search_scope")”51 votes
- Don't see your idea?