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.
387 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
Configure page metadata (browser tab title) across key pages independently from the main menu labels
In Primo NDE, the browser tab title (the HTML <title> element) for many pages uses the same label as the top menu, e.g., ILL request forms, Citation Linker, Collection Discovery, Purchase request form.
Screenshot with label codes toggled on to demonstrate the same label used for different functions
This means that the title in the tab cannot be independently customised to act consistently with other areas of Primo (search and my library account where separate labels can be managed). This creates issues:
Usability:
- Users with many collection discovery tabs open cannot distinguish which collection is in each tab. Users sharing…
3 votes -
Copy text from digital viewer
When reading documents in the digital viewer, it would be nice to have the ability to copy text directly from the page. You can do this if you download the document. I was attempting to do this with a larger file that mentioned other reports I wanted copy the name of a report to view/search for in the catalogue; however, the digital viewer does not allow users to select text from the document.
13 votes -
Allow icons display in database search
Allow display of images in database search results view for showing databases icons.
It's the only menu in Primo where it's not possible. Makes no sense !1 vote -
Improve Browse with 505 $$t subfield
Ex Libris technicians report that currently only the first occurrence of 505 $t is included in the Title index. As a result, if you Browse by a title listed further within the 505, the results don't supply a matching record. All $$t subfields in the 505 (and any other fields recording titles) should be included in the Title index to avoid this issue.
7 votes -
Icons in NDE
The icons at the top of the list of records following a search are not very self-explanatory.
On one hand, the export icon looks more like an logout icon.
On the other, the bookmark icon is not easily recognizable as such. Visually, it appears more like a simple rectangle rather than a flag, making it particularly difficult to identify for users with visual impairments.
We would encourage improving these two icons to enhance usability.
1 vote -
Enable exclusion of resource types in WorldCat 3rd party index scopes
Many of our researchers prefer to search using a blended scope that includes WorldCat along with other Primo indexes. Despite the lack of facets for the WorldCat records and other caveats, this is a popular scope especially for advanced researchers. However, the inclusion of article records in the WorldCat index is unnecessary and confusing. Many of the WorldCat article records do not include sufficient metadata, although fuller metadata may be available in the records within WorldCat. The insufficiency of metadata results in the inability for accurate availability calculation and display of links to full text. Researchers may therefore place interlibrary…
1 vote -
Add Due Date to Real Time Availability Status in Brief Records
We would like to be able to see the status messages to include Due Dates, where applicable.
Example: add date to Not available - Loan message, something along the lines of Not available - Checked out until {date}.8 votes -
Improved Display of Coverage Statements for Taylor and Francis Journals autoholdings collection.
Taylor and Francis adds multiple coverage rows to reflect the different purchasing methods. For example, one line may represent perpetual access while another indicates current access. This is why some coverage statements appear to overlap.
We propose to:
1. Retain the purchase type (e.g., perpetual, current) for each coverage statement within Alma.
2. Present only non-overlapping coverage statements to users in primo.
This enhancement is planned as an upgrade to the current functionality, but there is no set release date as of now.
To help expedite this enhancement, the support team suggested to open an idea exchange to encourage all…71 votes -
Display of Advanced Search Pre-filters in the “Searched for” section in the Advanced Search summary
Currently, the “Searched for” section in the Advanced Search summary does not display complete pre-filter information. We believe it would be beneficial for users to see a complete summary of all search parameters, including any date range pre-filters applied in Advanced Search.
For example, if a user searches with the following criteria:
All Subjects contains exact phrase North Korea
Resource Type: Books
Date: 2016–2026
the search results currently display only "Searched for: All Subjects contains exact phrase North Korea"
We ask that the “Searched for” summary reflect the full set of applied filters, such as "Searched for: All Subjects contains…
1 vote -
Make "patron default sort" an optional feature
Please allow customers to disable the Patron Default Sort feature. [1]
Since this feature was added to Primo last year, we are regularly contacted by perplexed users wondering why relevancy ranking isn't working. Invariably, the users had selected a different sort option the last time they used Primo and did not realize that Primo would remember their sort options in the future.
If there are no plans to implement this feature in NDE, please disregard this request.
3 votes -
Do not show availability for CDI/Alma records with matching GTI ID
Occasionally, CDI records will show availability for physical items (holdings/digitization offers via Rapido), and the physical records will show online availability. To our understanding, this is due to a matching GTI ID. We were informed in a SF case that it is currently not possible to resolve this. As this leads to confusion for our libraries (mainly digitization requests for an electronic resource) we would be glad if a solution could be found to no longer show these incorrect availabilities (or at least for the digitization requests to show the physical record they were actually placed on).
Example: https://ubs.swisscovery.slsp.ch/permalink/41SLSP_UBS/giv3ks/cdi_askewsholts_vlebooks_978354048849174 votes
- Don't see your idea?