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.
654 results found
-
User-defined favorite libraries that get preferential ranking in the Brief Display, the Get It section and Libraries facet
The idea is to introduce a new feature: "Favorite Libraries". In the Library Card, patrons could select their favorite library or libraries (regardless of the IZ to which they are affiliated to, in case of a consortium). Consequently, in the Brief Display, this choice influence the ranking of the records, in the GetIt section, the system first displays items from the selected favorite library(ies) on top. In the facet "libraries" where results are sorted by library, the system would display the favorite libraries on top, before other libraries.
4 votes -
The Resource Sharing Request Form and Hold Request Form should allow letters in the start page, end page, and Pages to Photocopy fields.
There are a number of academic journals that use alphabet characters when numbering their publications- especially in supplement volumes. These characters should be allowed when patrons submit requests for materials.
6 votes -
Recommendation system for learning and research resources
Academic libraries increasingly act as an ecosystem for learning and research resources. Therefore, they need a platform that can serve as an ecosystem to guide academic users.
Target: Incorporate into Primo VE a recommendation system that, based on users' searches, gives recommendations at the resource level (e.g., article, book, book chapter, case study, image, thesis, etc.).
Output: After the user searches, Primo VE provides a list of prioritized learning or research resources, sorted by their thematic relevance or visualisation-based popularity.
Parameters: The recommendation system should match the query with the users' profile (e.g., career, under|postgraduate level, etc.) after they log…
1 vote -
Add an option to move the "Show more" link above the "Additional Services" link for "Display All Links in Full Display for CDI. "
Current design: Additional services will appear before "Show more" link when "Display All Links in Full Display for CDI ." See the documentation here: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Display_All_Links_in_Full_Display_for_CDI.
Suggestion: add an option to change the order of the links,
3 votes -
Improve Citation Action
We would like to summarize in this idea exchange several issues we have run into with the citation action that inhibit the usefulness of the functionality for our customers greatly. Most of these relate to a lack of language sensitivity on the incoming side of the citation action. We would think it would be good if Ex Libris could work towards an improvement here, maybe together with the Citation Styles Language Project.
The formatting for the page count should be p.DDD-DDD or p. DDD-DDD in 773 $$g according to Ex Libris. The issue with this is that when our cataloguing…
52 votes -
Ahead of print articles
I would love to see some regulations or procedure set in place for articles not yet published from being published in primo. I understand this is a vastly complex issue but curious if anyone else has had these issues as well and ideas on the topic.
Per Ex Libris
Ex Libris's goal is to reflect the provider’s content and metadata and cannot directly make changes in our databases without the provider making these changes. If the provider has sent us a record for an article that is not yet published, or not yet assigned to a specific volume/issue, you will…16 votes -
Index Item Description in Primo VE
We record the monographic titles of periodical issues only in the Item Description field and not in the periodical bibliographic record.
This item field is searchable in Alma but not in Primo VE.
We need that the Item Description field to also be searchable in Primo VE.41 votes -
Display import profile name also for for failed import jobs
Currently, the scheduled job "Import Data to Primo VE" gives us the name of the import profile/external data source that was harvested, but only if the job ran successfully. If not, only the name of the job will be given, but not which profile it ran on. This is true both in Alma and for the corresponding e-mail notifications. We would be glad if this could be changed so that the profile name is always displayed, as the current behaviour is making troubleshooting issues with the import profiles quite cumbersome, especially if several are affected at once.
37 votes -
search profile slot drag and drop
Like many other Primo VE libraries, we have a single search profile slot (Everything) with a lot of difference search profiles (105 in total). Whenever a new search profile is created, it will be at the bottom and since you can only move item by clicking up & down each times, for libraries that have a lots of profiles, it is a nightmare. Imaging moving just 1 item to the top will take 105 clicks. It would be very helpful if it can be drag & drop instead to change position of an item on the list.
3 votes -
Allow Customization of Link Prioritization in the Merged Record to prioritize OA
Currently, when there is a merged record with multiple links, the links are prioritized according to a fixed set of prioritization rules (https://knowledge.exlibrisgroup.com/Primo/Content_Corner/Central_Discovery_Index/Documentation_and_Training/Documentation_and_Training_(English)/CDI_-_The_Central_Discovery_Index/050CDI_and_Linking_to_Electronic_Full_Text#Link_Prioritization_in_the_Merged_Record). In general, the rules prioritize links to paid content over links to unrestricted (OA) content. For example, if all records in a merged group are coming from collections using link in record, Link in Record links for subscribed content are prioritized over OA links. As another example, if some records in a merged group use the link resolver, and some use link in record, link resolver links for subscribed content are prioritized over the OA…
37 votes -
Dedicate a user role for "Access Analytics (Primo)"
Now full "Design Analytics" role is required to access "Access Analytics (Primo)". In fact Primo usage is quite different from other Alma data including sensitive data like user, acquisition. It would be useful to have a partial analytics role for "Access Analytics (Primo)" like "Design Analytics – Acquisition", "Designs Analytics – Fulfillment", etc.
Thank you.
Howard
CUHK Library, Hong Kong5 May 2025
4 votes -
Allow Primo Research Assistant proxy definition to be determined by electronic collection's service
Currently, there is only one proxy definition allowed for the electronic services in Primo Research Assistant, but a one-size-fits-all approach is not sufficient for our needs. Alma allows for multiple proxy definitions to be used with electronic services, as they are configured in each electronic collection's service editor. We currently use 3 different definitions: 1) OpenAthens Redirector, 2) OpenAthens Proxy, and 3) no proxy. Please mirror this functionality in PRA so that we can create the correct links for all of our electronic services.
3 votes -
Add in additional filter features and options on Display Logic Rules (All/Any)
For the display logic rules to include an ALL/All other function in the rules.
Occasionally, we want to hide something, except when it's the only option available. We can only do this within the Display logic rules by selecting each service or interface individually to add to the list.
Creating the rule in this way makes it very large and unwieldy as well as static, having to go back in repeatedly when a new service or interface becomes available to add it to the extremely large list. By creating an all/all other option it would save time, make it less…
2 votes -
Primo VE - Allow normalization of Esploro records
As a discovery tool Primo VE is supposed to deliver a unique gateway to many Library Resoures, including the a Institutional Repository (i.e. Esploro ).
To do so in a blended search one must be able to normalize records from different sources. We used to do that in Primo Classic, with a Pipe and a Normalization Rule. This is however not possible in the newer Primo VE.
Please allow manipulation and normalization of Esploro assets so that we can show them in the catalogue in a consistent way.38 votes -
Show “display fields” and “General electronic services” in a DEDUP record
We show print records when records are DEDUPed (Availability: ALMA-P).
When there is a display field created for an e-record it will not show up when the record is deduped with the print record. Neither will so called “General electronic services” created for the e-record show up.15 votes -
Display "to present" for journals with current coverage
Primo displays current journals by displaying only the start date - the "to present" is implied, but we've heard from our users that they are confused by this. Please allow the system to display "to present" for journals with no end date in coverage.
3 votes -
Disable default search for related titles without direct links
It would be helpful to be able to deactivate the often-problematic default search Primo conducts whenever you click on a related title without a direct link to a corresponding record, since this search frequently returns irrelevant records.
2 votes -
Cross-Institution favorites
In a consortial environment, we would like to see favorites shared across institutions.
Currently, favorites from institution A are only visible when logged into institution A but not when logged into institution B and vice versa.
Our desired behaviour would be that all favorites from all institutions are shown, regardless of which institution a user is logged in to.
4 votes -
Research Assistant: please allow to link external website for help pages
The current RA help page is built from the contents of code tables, but this doesn't give much flexibility in lay-out, to include images etc. Our question is that institutions also have the possibility to link to their own web pages for documentation and help.
5 votes -
Dublin Core field to display external links (like an 856)
We would like to have a way to link users to external resources from a Dublin Core record, similarly to how an 856 is used in MARC. Example: a digital object in Alma could link to a related finding aid in ArchivesSpace.
Perhaps the field(s) most appropriate to display in this manner would be dc:relation, dcterms:isPartOf, dcterms:replaces, dcterms:requires, dcterms:conformsTo and dcterms:isVersionOf.. but only if those fields utilize (dcterms:URI). If any of those fields are not tagged as a URI, that field should display as it does now.We are agnostic to whether such hyperlinks should be displayed in the "links"…
9 votes
- Don't see your idea?