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
-
Further Customization of "Service Temporarily Unavailable" Message
In Alma, a "Service Temporarily Unavailable" message can be configured for electronic collections that will display in Primo. While the message itself can be customized, it's not very eye catching for users in Primo.
We would love for this to be able to be customized in regards to colour, font size, highlighting, etc. Or display on the main search page rather than needing to click on the title to see it.
3 votes -
Display ebook reading format (HTML, EPUB, PDF etc.) in Primo (VE) full display
When displaying links to Ebook providers in Primo (VE) full display it would be suitable to have a notice of what ebook reading formats accessible for each provider. Instead of having to click further to the each provider to retrieve the information. Even information about online reading and/or download option would be suitable.
44 votes -
ORCID iD Integration in Info Card for Contributor Page in Alma
Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.
Current Conditions for Info Card Display:
- A person is linked to an LC Names authority for a personal name.
- A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
- Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the…
203 votes
AdminAdina Marciano
(Admin, Ex Libris)
responded
Thank you for the suggested idea. We see its value and will consider it in the future. This development requires integration with third-party providers, and we will need to investigate the possibility of this development.
-
Enable Custom Configuration of Primo Normalization Rules for Local Authority Search
Current Situation: Local authority search records are currently displayed with hard-coded normalization rules (NRs).
Proposed Change: Allow users to configure Primo normalization rules for local authority search. This flexibility will enable us to normalize authority records and display fields according to our specific needs.
123 votes -
Include subfield k from 245 in title index (important for manuscripts/archives)
Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html
This subfield is important for manuscripts and archives. Examples from OCLC:
245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5
245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David…
31 votes -
Support turning on/off individual CDI document attributes
Currently, CDI document attributes can only be turned on/off at the view label, and if there is a particular attribute that a library does not want to display, they cannot turn it off as a configuration.
For example, a library may want to turn off the "Primary source" label because it causes confusion when patrons are searching both CDI and local records together.
Please add the ability to enable or disable individual CDI document attributes for display in Primo.
7 votes -
Instant Insight into FRBR Versions in the Search Results
We have received feedback from our users that they would like to get an initial overview of a FRBR group’s contents directly in the results list. When encountering the representative record of a FRBR group, they want to immediately see how many online resources and physical copies are included, along with other useful details such as publication dates or resource types.
A straightforward implementation could be to enhance the link to the versions list so that it not only shows the total number of versions but also indicates how many available online (consortia: only online resources that are available in…33 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,…88 votes -
Change how the 541 holding field displays in Primo VE
Primo VE users would benefit from improved readability of descriptive metadata in library records. Currently, MARC 541 fields display each subfield (such as c; a; d. on separate lines, which fragments the information and makes it harder to interpret.
This proposal suggests enabling a configuration option in Primo VE to display the entire 541 field as a single, continuous line with appropriate punctuation between subfields. Presenting the field in this way would preserve the contextual relationships within the data, reduce visual clutter, and make acquisition and provenance information clearer and more accessible to users.
2 votes -
Remove harvest date from CONTENTdm import profiles so it can be scheduled
Currently, an import profile for CONTENTdm cannot be scheduled as there is a bug that prevents the job from running if the harvest date is populated. Please remove the harvest date input.
1 vote -
Provide method for users to opt out of Mixpanel tracking (NDE)
Users should be able to opt out of Mixpanel data tracking. Although the data sent to Mixpanel is appropriately anonymized, libraries tend to want to allow users to opt out of various tracking mechanisms. Opt-out should be persistent across sessions via a browser cookie or local storage.
3 votes -
Black theme for customization color theme
In the customization color theme of Primo NDE, black (hex #000000) is not one of the 17 colors you can choose.
Many institutions will have black as the main color in their designguide - for menu, text, icons, element details etc.
Please develop this option in customizatition color theme.3 votes -
PRIMO - Campo 774 MARC21- manter ordem dos campos catalogados=maintain the order of the cataloged fields
Gostaria de porpôr a configuração da visualização do campo 774 marc21. No caso de uma miscelânea que tem vários títulos queríamos preserver a ordem dos títulos que estão catalogados. O PRIMO não os apresenta como são catalogados no ALMA, ele ordena-os por ordem alfabética. Seria exelente ter uma opção que respeitasse a catalogação de origem. Ou uma regra que permita a escolha de uma das opções.
I would like to propose a configuration for the display of MARC21 field 774. In the case of a miscellany with multiple titles, we would like to preserve the order in which the titles…
1 vote -
Keywords entered should be carried over from the basic search field to the advanced search field
In Primo NDE keywords entered should be carried over from the basic search field to the advanced search field as in Primo VE
12 votesWe will revisit this and will consider adding this to support user continuity
-
Improve Primo VE searching in non-roman script so definite article prefixes are appropriately counted as non-filing characters
Arabic and Hebrew print titles beginning with the definite article prefix (like English "the") cannot be retrieved in Primo VE unless that initial definite article is included in the search. This is true even when the linked 880 with non-roman script has the number of nonfiling characters coded correctly in the subfield indicator in the bibliographic record
Example:
245 13$6880-02 $aal-Mabānī al-Kanʻānīyah fī Filasṭīn / $cNimr Sirḥān.
880 12$6245-02/(3/r $aالمباني الكنعانية في فلسطين / $cنمر سرحان.Without the initial definite article, the search comes up empty or retrieves only records from the CDI, but not the sought print materials present…
24 votes -
Allow Independent Configuration of “Fine” and “Potential Fine” in NDE Loan Displays
As a Primo administrator, I would like independent configuration control for “Fine” and “Potential Fine” in the NDE loan displays so that libraries can manage Brief and Detailed loan information consistently and transparently.
Current behavior in NDE is unclear and differs from existing Primo VE behavior:
- When “fine” is enabled in the Loans Detailed Display configuration, both “Potential Fine” and “Fine” appear as separate labels to users, even though only one configuration option exists.
- When “fine” is removed from the Detailed Display configuration, both “Potential Fine” and “Fine” are removed from both the Brief and Detailed loan displays in NDE.
…
1 vote -
Make it possible to show suppressed bibliographic records in the collections lobby
We have a large collection where we only want to make a select number of more academic titles discoverable in Primo search so that library users aren't overwhelmed with irrelevant content.
It would still be good to make all titles in the collection discoverable through an alternate means, however it isn't possible to add these to the collections lobby without these appearing in Primo search. The collections lobby only shows titles with unsuppressed bibliographic records. Can we make an option to allow suppressed records to be viewed in the collections lobby?
3 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 present64 votes -
DC record mapping to Journal Title, RIS Volume, Year, Issue
Based on the current Primo VE documentation, both dcterms:isPartOf and dcterms:bibliographicCitation may be used in the mapping to the addata section. These fields can also be used for extracting host information, such as volume, issue, and year, when the value is formatted accordingly.
The problem is with keeping the journal title in dcterms:isPartOf (for example, Technologies) and place the enumeration value (for example,14(2026)2) in dcterms:bibliographicCitation is that it override the Journal title in the RIS and display the enumeration instead. (See RIS export below). It is currently a limitation in mapping to extract Journal title to JF and volume, issue…
3 votes -
Allow patrons to manage email notification preferences by themselves
As a consortium serving more than 200,000 patrons, we request that Primo My Account include a self-service “Notification Preferences” section allowing patrons to select or deselect specific categories of library emails (e.g., courtesy letter, availability letter...), with clear distinction between mandatory and optional notices. This would improve user experience, reduce unnecessary email volume, enhance deliverability of critical communications, and support environmental sustainability by limiting avoidable large-scale email traffic across the consortium.
2 votes
- Don't see your idea?