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.
679 results found
-
Do not display private fields in “display source record” or full record in Primo VE.
Marc 21 coding is used to identify some marc record fields/subfields as private. As an example, the indicators in the 541 tag are used to indicate that data in the field is ‘private’ to the organisation. Primo VE should automatically hide these fields from the source record and full details display in Primo VE. If an organisation wishes for the field to be made public they can adjust the record coding as appropriate. Alternatively organisations should be able to select to suppress private fields (as identified in marc 21) from public display.
87 votes -
"Feedback Tool" for the New Primo UI: insert the e-mail of the logged in user automatically
Currently the field "e-mail" in the Feedback form is defined as optional.
As well as with the current e-mail functionality of bibliographic citations, we would expect the e-mail to be automatically pre-filled when a user is logged in. But unfortunately this does not happen.
Please insert the e-mail of the logged in user automatically or at least give us the possibility to set this option in the Primo backend.
Thank you in advance!
P.S.: Please see also this Idea:
Feedback Tool for Primo VE - allow user's email as addressFrom in Report a Problem Letter
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45350419-feedback-tool-for-primo-ve-allow-user-s-email-as19 votes -
Reverse the order of Available in Library / Available Online on full record display
We are new to Primo so pardon if this idea already exists. My public services colleagues would like to see "Available Online" appear before Physical Availability in the brief record information on the top of the full record display. We can move the View it service section higher in the page but we can't flip these two links.
4 votes -
Inform users when wildcard limit has been reached for local records (when still displaying CDI results)
Based on Salesforce case 06390632.
When using wildcards in a Primo search, there is a limit to how many you can use before the search triggers an error that excludes all local records.
This limit is only for local records. The CDI search does not follow the same limitations and will still gather results even if this limit is reached.
If a users crosses the wildcard threshold when searcing in a scope containing only local records, there will be an error message displayed that explains why no results were found. However, if the same search is done in a…
42 votes -
"Exclude all CDI Books from all different reference types"
Make it possible to exclude ALL CDI ebooks even from databases
22 votes -
Show item availablity on the top level for 'Group Locations by Library in Get It'
In April 2022 we got the "Group Locations by Library in Get It" feature: https://knowledge.exlibrisgroup.com/Primo/Release_Notes/002Primo_VE/2022/010Primo_VE_2022_Release_Notes#Group_Locations_by_Library_in_Get_It-98574
To save users' time when it comes to finding out whether an item is available or not, would it be possible to show the item availability already on the top level, for each library? Color coding wouldn't hurt either, indicating instantly whether a location has the item available or not.
A rough example in the attached files.
1 vote -
Collection Discovery: "new" pagination method instead of endless scrolling
Already some time ago (May 2021 Release) Ex Libris has rolled out the "new" pagination method: users can now specify whether to display 10, 25, or 50 results per page.
This works also in the "Database Search" and the "Journal Search" but not in the "Collection Discovery" section of Primo.
"Collection Discovery" still provides the old endless scrolling method (Button "Load More Results") where you quickly run into brower performance problems if a collection contains my items.Please make the "new" pagination method also availalbe in the "Collection Discovery" area.
Thank you in advance!37 votes -
Display license information for Open Access and Open Educational Resources
Please add license information for resources and collections that are known to be open access or open educational resources, making it clear what licence applies. This applies both in CZ records and CDI. We would like to make it clear to our users when a title is made available under a particular licence terms.
173 votes
AdminTamar Ganor
(Admin, Ex Libris)
responded
Hello,
This idea will be transferred to the Primo forum as it will require product development to support this metadata.
Kind regards,
Tamar Ganor
Content Product Manager
-
customization package API
Please add an API to deploy customization packages in Primo VE so that customers with many views can automate the cumbersome deployment process.
0 votes -
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.
101 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 -
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 -
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…
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…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.39 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
- Don't see your idea?