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.
651 results found
-
Preference of links from link resolver over link in record in brief results for merged records
When one or more of the records in a merged group is coming from a collection using the link resolver, and other records are coming from collections using the link in the record, the link in record type of link is always displayed in the brief result list. It should be possible to choose to always display a link resolver type of link instead.
4 votes -
Show amount of records of a Discover Import Profile
In Alma it's not possible to use the adv search bar/jobs/analytics to list records from external data sources. We can see the records loaded in the History option of each profile execution. But to have a total, we would need to open one by one.
Could it be possible to have the amount of records and MMS IDs of each discovery import profile available to see?
For example, in the same menu list where we see the History, Reload and Delete, etc, add an option called: Total and when we click on it Alma searches for all records of the…
1 vote -
Add editing functionality to labels/tags created in My Favorites
Currently, there is no way to edit a label created in My Favorites to organize items you have saved/Pinned to My Favorites. It would be helpful to be able to edit typos or make adjustments to the label as needed, without have to reassign items.
1 vote -
Consistent UX or labelling for Collection Discovery search box
Ideal solution: The Collection Discovery search box should be persistent and always search at the item level within all collections (as it does in the lobby) in order to provide a logical, consistent user experience.
Secondary solution: the label text should be editable for each search box separately to make it clear what is being searched on the page.
Problem:
- The lobby search box is for everything
- The top-level collection search box is for the title of sub-collections in that area only
- The sub-collection search box is for items in that sub-collection only.
Yet, all three options say "search" and…
1 vote -
Quicklink display options on full record
In Primo VE, any quicklinks associated with records show both at the top of the full record display and in the Links section of the record. CSS can be used to hide quicklinks from the Links section, but often results in a blank Links section on the record.
It would be helpful to have options to show quicklink at the top of the full record display, but hide them from the Links section. This would help improve the usefulness of the Links section of the record.
15 votes -
Enhance DC XML normalization routines for external sources (PrimoVE)
In Primo Back Office, there is 86 inbuilt transformational routines for MARC21 and Dublin Core data normalization (e.g. “Take first words”, “Get highest number and normalize last digit”, and “Remove HTML tags”). Most have been translated for MARC21 in PrimoVE by various people but, because of limited regex and Xpath functionality, few have been translated into Dublin Core XML normalization routines for PimoVE.
We would like to see the implementation of full regex and/or XPath / XQuery functionality (or similar) to allow all Back Office normalization routines to be created for PrimoVE.
60 votes -
Pipe setting improvement: allow to exclude specific OAI sets from a pipe
We would like to have the possibility to exclude one or more specific sets when we harvest the data with OAI-PMH protocol in Primo.
This option would have 2 results:
- to reduce the number of imported records
- we wouldn't have to set specific normalization rules in order to exclude the records we don't want to show in Primo21 votes -
Change handling of MARC fields 100 and 700 in citation styles in Primo VE
Handling of MARC fields in citation styles should be changed as follows:
1. If there are relator codes in $4, only $4 aut and cmp should be considered as author, relator codes $4 edt, ill, ivr, trl and drt should be treated as contributors. Entries with other $4 codes should be ignored for citation.
2. If there are no relator codes $4 in the record, field 100 should be considered as author, field 700 as contributor.
Benefits: Citiation styles get independent from cataloguing language as they are now by using $e. Also citation styles work independent from the fact, if…8 votes -
Automate SSL/TLS certificate management
For hosted Primo sites that have custom domain names, the current process for deploying SSL certificates involves time-consuming manual steps and hand-offs, many of which must be repeated each time a certificate is renewed. [1]
Several institutions will soon require SSL certificates to be renewed every 90 days, at which point the current manual process will become utterly unmanageable for both Ex Libris and its customers. [2]
I propose that Ex Libris adopt an ACME-like service (such as Let's Encrypt) to fully automate SSL certificate management. The customer's responsibility would be to set up a DNS record (as they do…
289 votes -
CDI records: please provide us the ORCIDs in the PNX record in a usable form
Unfortunately, we have received the following case response: "We have reviewed your request with our content operations team and determined that our system is currently not designed to provide the functionality you requested, so the next step is to pursue this as an enhancement."
So we hope to get support for our proposal in the Alma community.We are currently working on making the ORCID more visible in our Primo (incl. linking to the ORCID entry of an author).
We are glad to see that CDI records already contain the ORCIDs in the PNX record.
Unfortunately, they cannot be used…60 votes -
Add a job that can set the CDI option collectively
We would like you to add a job to set "Activate for search in CDI" collectively for the electronic collection set of CZ.
Also, please add a job to batch update the following CDI options for the electronic collection set of IZ.
- CDI Search activation status
- We subscribe to only some titles in this collection
- CDI-only full text activation
- Do not show as Full Text available in CDI even if active in Alma0 votes -
Give customers the option to have a custom multilingual file for synonyms and compound words.
We are a multilingual network, catering to four languages. It is very important to us to ensure that customers find the same resources regardless of the UI language they use. As one of our UI languages does not have a synonyms file, it is currently not possible for us to incorporate synonyms beyond those included by default in our Primo, as this would lead to differing search results for this language. We would like this to be solved by allowing customers to use a dedicated multilingual file for synonyms, compound words etc. that they can customize to their needs.
0 votes -
Add option to filter out Global title index results without any offer
When creating a scope that include CDI records non filtered per availability (Rapido-CDI expanded index), Global title index without any offer (no Get it section, no view online section and no item available in the Rapido tile) are retrieved (example). These records are owned by libraries participating in any POD (outside of ours) of Rapido.
We would like to have an option to exclude the Global title index results without an offer.
104 votes -
Make both the label and the code from the controlled vocabulary registry searchable
When adding a controlled vocabulary to the registry and afterwards connecting it to a certain MARC field in Primo VE, patrons now can only search using the code and not the label.
As an example imagine a controlled vocabulary with the entry ECON (code) and Economy and Finance (label). If ECON (the code) is stored in the record and the patron searches for Economy and Finance in that field (in advanced filter), he or she will get no results. If you search for ECON however all relevant records will be returned.
Of course the patrons are not supposed to know…1 vote -
Integrated with ChatGPT technology
Good to integrate ChatGPT technology in Primo VE.
2 votes -
Separate the Primo My Account Update Login Credentials form into two different forms for PIN code and Password
As a user, I would like to have two different forms for Pincode update and Password update (Update Login Credentials in My Account > Personal Settings) so I am sure that I can also change only one of the two. With the current design (=one form for PIN and password update), it is suggested to me that I always have to update both.
10 votes -
Make the PIN code field in Primo My Account a secure text field with eye icon to show/hide the PIN
As a user, I would like to have the possibility to hide the values I have entered in the Pincode field (Update Login Credentials in My Account > Personal Settings) so that the data isn't visible to others. In order to check for typos, I would like to have the possibility to display the data (e.g. by clicking on an eye symbol)
94 votes -
Change / improve the Booking process for staff and patrons
Hi all,
We wish to submit a proposal to change the current booking process for staff creating a booking request in Alma AND for patrons creating their own bookings in PRIMO VE.
Now, Alma’s option to submit ‘’ Booking ‘’ requests require us to search an item, select it and then enter booking times for each piece of equipment desired, which is very time consuming.
When patrons book equipment, they often need up to 10 or more pieces of equipment for the same booking period. This is quite inconvenient and increases the risk of mistakes in the process.
In our…
3 votes -
Fix the CDI's match and merge process
The CDI's match and merge rules/filters need to be adjusted to prevent multiple ISBNs/EISBNs/DOIs from previous e-book editions from being added to the current edition's record, which frequently breaks OpenURL linking to the correct edition. This particularly affects targets like OREILLYONLINELEARNINGACADEMICPUBLICLIBRARYEDITION in SFX.
1 vote -
Ability to place restrictions on Display Source Record link
When enabling the ‘display source record’ link in Primo VE it would be useful to be able to specify which types of records the link displays or doesn’t display for. In our case we would prefer to restrict the option to our records for published resources so the private notes more typically associated with unpublished material such as manuscripts would not be publicly viewable.
5 votes
- Don't see your idea?