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.
735 results found
-
Show the date/time a question is asked in the AI research assistant, and in the copied result.
The date/time a question was asked is only visible when hovering over the question in the research history sidebar. This is a problem especially when working with history items that have multiple questions.
Scenario: User asks a question on something contemporary. They want to ask the same question in 3 months and then again in 6 months as more sources become available.From the history they open their previous question and use the "Try again" function. In another few weeks they do this again.
The question responses do not indicate when each iteration of the question was asked.
If they…12 votes -
Increase the maximum number of viewable records
Currently the max number of viewable records is 2000. If the number of search results exceeds 2000, paging beyond the first 2000 records is prevented.
If the limit is increased, users can continue to view search results beyond the first 2000 records without having to try and refine their search which may be difficult to do.
2 votes -
Granular Control for Alma Viewer and Digital Versions Tab in Primo NDE
Description:
In Primo NDE, the rule “Hide service: Representation Delivery Service” affects both alma-viewer-content and the Digital Versions tab (nde.brief.results.tabs.digitalVersions). In contrast, Primo VE allows institutions to independently control visibility of the Alma Viewer and the Digital Versions tab.
This enhancement request seeks to restore this level of granular control in Primo NDE. Specifically, institutions should be able to:
Hide the Alma Viewer for certain representations (e.g., auxiliary or restricted content)
Still display the Digital Versions tab for those same representations
This would provide the flexibility needed for managing multiple representations of a record while ensuring users can discover digital…
3 votes -
Pair display of 880 fields with their linked MARC field
When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).
In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare…
115 votes -
Allow Print option in Primo VE to print Quick Access representation along with metadata
When using the "Print" command in a Primo full view record, the print screen shows a record's metadata. However, if the record has a digital representation in the "Quick Access" section (as might be the case in a record managed by Alma-D), the image is not included in the print page. Having the option to include the representation would be helpful in cases where a printed image is needed alongside its metadata.
2 votes -
please add pick up library in purchase request form for patron to choose if checking "reserve"
Hi, sir,
There is purchase request library in primo VE purchase request form.
But usually the request library is not same as user pick up library, if patron check "reserve", that mean once the purchase is accepted and book send to library ,alma will generate a reserve for this request.
but now has no patron's pick up library for reference.
so please add a pick up library filed in purchase request form if checking "reserve".
Thanks ~20 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.
22 votes -
Allowing to opt out of loading OAI Repository records into Discovery Network
Allowing to opt out of loading OAI Repository records into Discovery Network
1 vote -
CSL Data (Citation Style Language) in Primo Search API
Primo uses Citation Style Language to generate citations for bib records. Presumably the bibliographic metadata is at some point converted to a csl-data object. https://github.com/citation-style-language/schema/blob/master/schemas/input/csl-data.json
It would be helpful if that csl-data JSON object was available through the Primo Search API. This could be a additional information one could request from the API. https://developers.exlibrisgroup.com/primo/apis/docs/primoSearch/R0VUIC9wcmltby92MS9zZWFyY2g=/
2 votes -
Allow Digital Viewer to use different View than Primo
When viewing digital representations in the Digital Viewer, Alma-D uses the same Primo VE View; however, this can cause some difficulties when configurations ideal for Primo don't translate well to the Viewer.
For example, we have a pop-up chat icon in Primo VE for patrons to chat with librarians; because this is configured in View, it's also present in the Digital Viewer, but the icon ends up obscuring parts of the representation's image and metadata.
We'd like to be able to point the Digital Viewer to a different View entirely than the one Primo VE is currently using.
5 votes -
Primo VE customize logo tooltip/description
Allow tooltip/description text to be added to the uploaded logo in the Primo VE view customization, similar to the "Links Menu" customization description.
This is a basic usability feature that should be easy to configure.
Our usability testing showed that about half the users expected the logo to go back to the main Primo VE search landing page rather than the library's home page (as many libraries have configured). Having a description on hovering would help clarify for users.8 votes -
Use all occurrences of a bibliographic field within GES Bib Field Enrichment
Institutions can define which fields are extracted from the bibliographic record metadata to be used in General Electronic Services by adding fields to the GES Bib Fields Enrichment mapping table. However, if the bibliographic field occurs multiple times in the record, only the first occurrence of the field is used. This means that the GES is not calculated for any subsequent occurrences of the field. For example, if I want a GES to be displayed based on a particular value in a 590 local note, the GES will only display if that value occurs in the first of what may…
1 vote -
Improve Primo VE drool editor messaging to display an error if the rules fail
Currently the Primo VE drool editor will not display error messages in some situations where the rules crash and fail.
Instead the Discovery Administrator flows through the process of updates believing that their changes to the rules are correct and have taken effect, only to find perhaps much later after reindexing request that they have not.
Actually what happens is that if the rules fail, there is no error shown, and the entire ruleset fails back to the out-of-the-box rules.
This is a considerable hindrance given the situation of no option to test display rules.Ex Libris advised in a…
3 votes -
Journal Title Facet Should Include Local Records in Blended Scopes
Currently, the Journal Title facet in Primo only applies to records from the Central Discovery Index (CDI), excluding locally cataloged article records and those imported from external sources such as institutional repositories. This behavior leads to inconsistent and confusing results for end users, especially when using a blended scope that includes both CDI and local records.
Problem:
Users conducting searches—particularly in the local language—often retrieve a significant number of local article records. Despite these articles being published in journals, their journal titles do not appear in the Journal Title facet.
Users are unaware of the distinction between CDI and local…3 votes -
Implementation of CDI rights at the article level and not just at the database and title levels
CDI knows that a given article belongs to a given journal and knows that we have a subscription to it for this year (based on our SFX subscriptions). CDI therefore displays the article citation as part of the content to which we subscribe and creates an OpenURL link based on the citation metadata. If the citation in CDI is correct but this content does not exist on the platform, this generates errors in our catalogue and returns results that we do not have access to.
ExLibris does not have rights at the article level (only at the database and title…
1 vote -
Add a language limiter to the Journal Search
Adding a language limiter to the Journal Search in Primo (VE or NDE) would be immensely helpful to students who need to find journals in specific subject areas.
3 votes -
Primo VE Permalink Verification Process
We would like a process to verify a file of Primo Permalinks are still valid for our institution.
Our librarians and professors place Permalinks in online documents for our patrons. As the documents age and portfolio IDs change the links can fail. This is very frustrating for our patrons.
The only link verification method today is to manually click on each permalink. This tedious and time consuming process is not cost effective when there are hundreds of links to check. Using standard web link checkers that operate in batch only establishes that a page does not result in an HTTP…
1 vote -
Primo NDE change order of fields in request forms
We would like to be able to change the order of the fields in the Request forms in Primo NDE
For example: in the Request another Issue Digitization Request Form the 'Comment' field is in the middle of the form, and we would like it to be in a more consistent place, at the bottom of the form.
1 vote -
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…
10 votes -
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…
18 votes
- Don't see your idea?