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.
545 results found
-
Purchase Request date
Add the user's purchase request date on their Primo library card in their account.
We would like that the user can see the date when he create a purchase request date on his Primo library card in his account.
We think that's will be an improvement for the users.
18 votes -
Responsive label "item in place/not in place" for open shelf items
Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.
As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this…
17 votes -
opensearch description support in Primo VE
Primo supports opensearch description allowing a better integration with modern browser but this functionality is no longer support in Primo VE. It would be very useful for users to be able to continue to integrate the search engine with browser.
3 votes -
Add library location name and/or code to advanced search options
I'd like to submit for reconsideration an idea that was posted back in 2020 but which unfortunately didn't receive enough votes to be considered for future development at that time. My own library has only been using Primo VE since May 2024, so we didn't get a chance to vote for the original post.
The previous post is at:
The earlier post was limited to adding the library location name as an advanced search drop-down filter. I'm expanding it somewhat here as a request to add library location name and/or location code as filter options. This is something we…
2 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.
1 vote -
Open Access Indicator for Unimarc records
Open Access Indication in Primo VE is currently supported for Marc21 and Dublin records : https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Open_Access_Indication_in_Primo_VE
Please support Unimarc record, too !109 votes -
Add more than 7 lines – Advanced searches only include a maximum of seven search criteria lines
Could we have the capability to include more than seven lines in the advanced search function? In Summon, Web of Science and numerous other platforms, there is an unlimited possibility to select more lines.
Given that our users frequently search using both Danish and English keywords, the seven-line limit is often reached when both languages are used in an 'OR' search.6 votes -
Primo default language
When opening discovery, the language showed is the default one set in the Alma configuration. Many website today are capable to adapt the default language depending on the language set in the browser or the ip adress or other technologies.
The current idea propose to investigate and eventually apply the technologies that allows an automatic adjustment of the primo default language.1 vote -
Support for Numeric Subfields (e.g., $0, $1) in MARC to PNX Mapping in Primo VE
Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.
Please map at least subfields $0 and $1 to PNX
This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .Use Case Example:
A record with multiple subject headings (650 fields) includes…13 votes -
Sort Favorites by Call Number
Allow sorting of "My Favorites" by Call Number. Currently, you can only sort "My Favorites" by Date Added, Author, and Title.
3 votes -
Allow the resource type - " Trade Journals " as an option under Primo's Resource Types!
Allow the resource type - " Trade Journals " as an option under Primo's Resource Types!
4 votes -
Improve call number Browse search
To improve the user experience in Primo VE, we propose modifying the call number browsing feature to show a few call numbers both before and after the searched call number, providing better context and making it easier to locate desired items.
2 votes -
Provide option to remove 490 field from Browse Index
We would like the option to remove the 490 series description field from the Browse index. Because we use 490 for series description and 8XX for the authorised form of series in the same record, the browse series feature in Primo counts one record twice. If we could have the option to remove this from the Browse index, this would solve the problem. It would need to be optional as it is clear that some Primo Libraries rely on the 490 for this purpose.
26 votes -
Customize brief display of fees in user account - Primo VE
On the overview page in the fees tile it displays 4 lines of information. If a user need more information they have to click on the entry to do so. One of the pieces of information in the drill down is if the fee was transferred to an outside entity such as bursars. Given there is a Pay Fees button even if transferred fees are present on this tab it would be nice to be able to have more lines display or at the least be able to order the display so what we feel is most important shows in…
3 votes -
Change CDI handling of Language data for Primo
CDI Language data in handled in ways which have undesirable impact on patrons in Primo, such as:
• A default language is applied to all records in a CDI feed for use in Primo in the Language field display, search, and facet. This may be done when the CDI provider feed has no record-specific Language information available automatically and the provider has not otherwise advised that all the records are in a specific known language and confirmed that this Language can be applied to the records in CDI
• Records may be allowed to merge into a CDI logical record…1 vote -
Improve Primo linking to limit dead/inaccurate links
To prevent user confusion, frustration, and access delays, we would like Ex Libris' Primo to mirror a feature that LibKey calls "Entitlement Confirmation," which would help prevent delivering dead links to end users, especially when Metadata in the CDI is lacking or incorrect.
Delays between publishing and availability, especially with third-party databases (like EBSCOHost), happen often and can vary in length due to the nature of aggregation. The proposed change would confirm if content is available before indicating to end users that it is. This saves user and staff time and effort, streamlining the process and managing expectations while providing…
22 votes -
Disabling automatically generated links for related records if the associated NR is disabled.
Primo VE is capable to automatically create links to related records via MARC 7xx fields.
As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
- in the related records, they differentiate between child records and parent records
- for child records, as the specific relation field is included, Display NR takes effect
- for parent records, as the specific relation field is not included,…43 votes -
NZ/IZ linking in consortia
Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.
In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the…
67 votes -
Author/Title Index in Browse Search
Author/Title Index in Browse Search
Please include an Author/Title index which searches headings combining author/creator name and uniform title. The index usually includes:
* 100/240
* 110/240
* 111/240
* 700 where $$t is present
* 710 where $$t is present
* 711 where $$t is present
* 800 where $$t is present
* 810 where $$t is present; and
* 811 where $$t is present60 votes -
PressReader
PressReader uses Webhook functionality to enable direct search of its content within Primo VE.
In Brief Search Results the link displays as "check for available services'. This is not configurable (Salesforce #07245690).
In the Full Record Screen the default text 'Link to Resource' is used.
This is sourced from Links and General Electronic Services Labels.
Can there please be a separate label, created specifically for PressReader, with text configurable by the library?
Screenshots attached
Thank you!
3 votes
- Don't see your idea?