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.
- or
3 results found
-
Include the item barcode as part of the data published from Alma to Primo in the AVA field to improve item search in Primo
Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode manually to the bib 945$$i for each item as part of our processing is not a viable alternative.
We would like an enhancement to Alma publishing that would add the item barcode to the data published in the "AVA" field. This functionality would improve workflow for staff when they need to search a record in Primo without having to navigate out of the items screen in Alma to retrieve the OCLC number, the MMSID or the ISBN, or to pull up the record in Primo when the book is in-hand without needing to key in the title or ISBN.
Examples of migrated records with the item barcode in the 945 $$i:
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71153242760001
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71188416360001451Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode…
465 votes -
Less duplicate records in Primo Central Index results
Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.
Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.
Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate results and consolidate the FRBR groups?
Examples of duplicate records:
Accuracy of prediction of gene content in large animal populations and its use for candidate gene detection and genetic evaluation
3 results (2 FRBR groups):
- TNproquest195858157 and TNfaoagrisUS201300875183
- TNcrossref10.3168/jds.2007-0231, TNscopus2-s2.0-42449094585, TNsciversesciencedirectelsevierS0022-0302(08)71293-1, TNmedline18349258
- TNorbi2268/23076Linguistic symbiosis between event loop actors and threads
2 results (1 FRBR group):
- TNsciversesciencedirectelsevierS1477-8424(08)00024-9
- TNscopus2-s2.0-51649125887 and TNcrossref10.1016/j.cl.2008.06.005Efficient control of transient wave forms to prevent spreading depolarizations
2 results (1 FRBR group):
- TNarxiv0705.3398
- TNscopus2-s2.0-39649117125, TNsciversesciencedirectelsevierS0022-5193(07)00579-6, TNcrossref10.1016/j.jtbi.2007.11.019, TNmedline18177900Le traitement de la modalité épistémique dans les traductions françaises de On the Origin of Species de Charles Darwin
3 results:
- TNerudit1038687ar
- TNscopus2-s2.0-85017546223
- TN_proquest1870219718Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.
Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.
Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate
…203 votesHi all,
We are moving this idea to "Closed" to release your votes, as it is no longer relevant with CDI.
Best regards,
Yael.
-
Ensure that CZ & CDI Metadata is Linked Data Ready
I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:
Broader strategic and commercial alliances required to ensure that data is ready to be linked?
To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?
Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could share.
Isn’t this the best way to ease the burden on libraries and leverage our metadata improvements for mutual and sustainable benefit?
I note that this document alludes to the Company taking a lead in creating a new open metadata platform and preserved data in an open format.
https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Linked_Open_DataPreserving metadata is not the same thing as maintaining it because metadata evolves e.g. authorities are deleted, changed and new ones created.
In light of this I would ask that the Company explore strategic commercial partnerships to ensure that any metadata that they manage (knowledgebases, platforms) is properly maintained.
Jane
I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:
Broader strategic and commercial alliances required to ensure that data is ready to be linked?
To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?
Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could…
16 votes
697 results found
-
Suppress controlled vocabulary expansion notification when expansion has no impact on results
When a search triggers controlled vocabulary expansion but the expansion term contributes zero results, Primo VE still displays the message informing the user that the search has been expanded, and offers a link to disable the expansion (conVoc=false).
Clicking this link produces no observable change in the result set, since the expansion was not contributing any results in the first place.
This creates a confusing experience for the user:
1. The system implies the search was meaningfully expanded
2. The user is offered the option to opt out
3. Opting out has no visible effectProposed improvement:
The expansion notification and opt-out link should only be displayed when the controlled vocabulary expansion actually contributes results. If the expansion term returns zero results, the notification should be suppressed — or alternatively, the UI should clearly communicate that the expansion had no impact on the current result set.This would make the interface more transparent and trustworthy, and avoid users wondering whether the opt-out functionality is broken.
When a search triggers controlled vocabulary expansion but the expansion term contributes zero results, Primo VE still displays the message informing the user that the search has been expanded, and offers a link to disable the expansion (conVoc=false).
Clicking this link produces no observable change in the result set, since the expansion was not contributing any results in the first place.
This creates a confusing experience for the user:
1. The system implies the search was meaningfully expanded
2. The user is offered the option to opt out
3. Opting out has no visible effectProposed improvement:
The expansion notification…3 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 -
NDE- Links should be visually different from regular text (for example, with underlines) so users can clearly identify clickable elements.
Primo NDE - The linked values in records, for example under “Creator” and “Subject” are not visually differentiated from plain text. Consider underlining hyperlinks (or applying another consistent link style) so users can more easily identify interactive elements.
1 vote -
PRIMO NDE - enable selecting Excel export fields for records from search results
PRIMO NDE - enable selecting Excel export fields for records from search results
1 vote -
Metadata from Database Link Resolver into the Resource Sharing request form
Allow more metadata from Database Link Resolver into the Resource Sharing request form to ensure the library staff can more easily fulfill the request and patrons are well-informed through notifications of the exact item they have requested - for example a specific chapter from a multi-chapter book written or edited by someone other than the chapter's author. Having the Book Title, Chapter Title, Book Editor/Author, and Chapter Author would be helpful especially for our faculty patrons.
3 votes -
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 are cataloged. PRIMO does not display them as they are cataloged in ALMA; instead, it sorts them alphabetically. It would be excellent to have an option that respects the original cataloging. Or a rule that allows us to choose one of the options.
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 -
Primo NDE: Full Record Services - split up View It/Get It into its separate sections to allow reordering
When configuring a view (either NDE or VE) in the Full Record Services tab, getit_link1 (View It/Get It) includes BOTH of the sections View It (Default label: View Online) and Get It (Default label: Get It, sub label: Locations). The combined sections works in Primo VE because requests are included in Get It. However, now that NDE has a new separate Requests section, the original View It/Get It should be split into its separate sections to allow institutions to customize the order of all three sections.
For our institution, we want View Online at the very top as online access is a priority for our users, but this forces us to have Locations above Requests. This ordering is confusing and looks especially wrong in records that are print only. Ideally we would like services ordered as View It (View Online), Requests, Get It (Locations), but this is not currently possible with View It/Get It combined as they are in Full Record Services.
Ex Libris advised that we could customize the order using CSS, however, this approach is inaccessible, and introduces the potential for problems with ordering in future releases.
When configuring a view (either NDE or VE) in the Full Record Services tab, getit_link1 (View It/Get It) includes BOTH of the sections View It (Default label: View Online) and Get It (Default label: Get It, sub label: Locations). The combined sections works in Primo VE because requests are included in Get It. However, now that NDE has a new separate Requests section, the original View It/Get It should be split into its separate sections to allow institutions to customize the order of all three sections.
For our institution, we want View Online at the very top as online access…
17 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.
Requested enhancement:
- Clarify the intended relationship between “Fine” and “Potential Fine” in the configuration.
- Allow Brief and Detailed loan displays to be configured independently, consistent with current Primo VE behavior.
- Provide separate configuration options for “Fine” and “Potential Fine,” or clearly document why both labels are displayed from a single configuration setting.
This enhancement would improve configuration transparency and provide libraries with more precise control over the patron loan display experience.
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 -
Direct linking from Full record in Primo
Within the full record display in Primo VE, the available online link should take the user directly to the resource, not to another field in the full record where users can then link out to the resource.
1 vote -
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 to the correct RSI field at the same time.
<dc:date>2026/dc:date
<dc:relation xsi:type="journal">Technologies/dc:relation
<dc:relation xsi:type="volume">14/dc:relation
<dc:relation xsi:type="issue_number">2/dc:relationTY - JOUR
JF - 14(2026)2
PB - MDPI
Y1 - 2026
ID - alma991027502611907026
AU - Saleh, Omar A.
AU - Rao, Saleem G.
AU - Alghadeer, Mohammed
AU - Omar, Ahmed A.
AU - Felemban, Muhamad
SN - 2227-7080
T1 - Optimizing Interface Dielectric Loss in Superconducting Coplanar Waveguide Resonators for Improved Quantum Circuit Coherence
ER -Primo VE documentation:
https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_%28English%29/120Other_Configurations/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_RecordBased 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 -
Make advanced search and natural language search terms visible for Primo NDE in portrait view of mobile phone devices
At present, when a user undertakes a Natural Language search or Advanced Search in Primo NDE on a mobile phone in portrait mode, the search query is not displayed however this is being displayed when viewed in landscape mode.
User's may not know to change the orientation of their device to see this information.
Support case #10573480 created with ExLibris responding as follows:
"Due to UX considerations and current UI limitations in the mobile view, the advanced query search terms are not displayed. This behavior also applies to natural language searches. At this time, there are no plans to change this behavior".At present, when a user undertakes a Natural Language search or Advanced Search in Primo NDE on a mobile phone in portrait mode, the search query is not displayed however this is being displayed when viewed in landscape mode.
User's may not know to change the orientation of their device to see this information.
Support case #10573480 created with ExLibris responding as follows:
"Due to UX considerations and current UI limitations in the mobile view, the advanced query search terms are not displayed. This behavior also applies to natural language searches. At this time, there are no plans to change…3 votes -
Increase Brief Item Display Field Limit in Primo NDE (Support item.brief.4+)
In Primo VE, libraries can configure more than three fields in the Brief Item Display (e.g., item.brief.1–4), which allows key item-level information such as location, call number, availability, and Terms of Use to be shown clearly and separately.
In Primo NDE, the Brief Item Display is currently limited to only three fields (item.brief.1–3), and the fourth field is not supported. This reduces configurability compared to Primo VE and forces institutions to combine multiple data points into a single field or omit information from the brief view.
This limitation impacts usability, as important details like Terms of Use or item policy information cannot always be displayed in a clear and structured way. Workarounds such as merging fields or relying on expanded item views reduce readability and flexibility.
We request that Primo NDE support at least four configurable Brief Item Display fields, to restore parity with Primo VE and better support institutions with richer item metadata needs.
This enhancement would significantly improve flexibility while maintaining the clean design principles of NDE.
In Primo VE, libraries can configure more than three fields in the Brief Item Display (e.g., item.brief.1–4), which allows key item-level information such as location, call number, availability, and Terms of Use to be shown clearly and separately.
In Primo NDE, the Brief Item Display is currently limited to only three fields (item.brief.1–3), and the fourth field is not supported. This reduces configurability compared to Primo VE and forces institutions to combine multiple data points into a single field or omit information from the brief view.
This limitation impacts usability, as important details like Terms of Use or item policy…
11 votes -
Inclusão do campo "código de barras" na busca avançada do Primo
Sugiro a inclusão do campo "código de barras" como opção na busca avançada do Primo. Atualmente, a busca contempla apenas campos do registro bibliográfico, o que dificulta a recuperação direta de itens específicos.
Com a possibilidade de pesquisar pelo código de barras, seria possível localizar um item de forma imediata, sem a necessidade de aplicar múltiplos filtros em diferentes registros. Isso tornaria o processo de conferência mais ágil e eficiente.
4 votes -
Ability to sort/filter according to item status
Ability to sort/filter according to item status
The display order of item records in Primo is the same order in which they appear on the Alma record. Although we can sort them within Alma according to Library/Location, from a user perspective it would be helpful if they had the ability to apply a filter/sort to see first only the itens that are available to borrow
11 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 -
Way to block access to popular fiction/nonfiction that is less than 6 months old in the Global Title Index
I know we can turn off some resource types in the global title index, as we have turned off dissertations and some other categories and it has worked well. We were wondering if there is a way to block access to popular fiction or nonfiction that is less than 6 months old. We do have users that request these, and we have to almost always reject them as 1.) they are always checked out, and 2.) they are not available through WisCat which is our Wisconsin public library union catalog.
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 loan requests for articles that are in fact available full text online with active links in better CDI records. This causes problems both for resource sharing and for researcher expectations. The WorldCat 3rd party index is not a good source for article searching for our institution, where CDI article records provide better discovery and access. We would like to be able to exclude article records from the WorldCat 3rd party index scope. We recognize that other institutions may want and use these records, so we would request the ability for institutions to select what resource types to include/exclude from a WorldCat scope, as is possible with CDI resource type selection in Central 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
- Don't see your idea?