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
711 results found
-
Primo VE - Linked open data person entity - option to display additional authority record fields
We contribute to the Library of Congress Names Authority and add associated group fields (MARC 373) with iwi affiliations for Māori authors and creators. Currently this field is not displayed in Person entity cards. Could this and other authority data be made configurable for display?
9 votes -
NDE landing page labels
With the new Landing Page configuration, it is now possible to customize the NDE starting page.
Under Discovery Configuration > View Configuration > Landing Page > Links, it is possible to configure the labels for the Links section. However, other Landing Page labels are managed at IZ level under Discovery Configuration > Labels > Landing Page Labels.
For consortia or institutions with multiple views, this creates a limitation: labels that are not part of the Links section cannot be customized per local view in the configuration menu, but only by creating view level labels in the code table. As a result, the usability of this solution is poor and the new Landing Page configuration is of limited use for our environment.
Please make all Landing Page labels configurable at View level directly in the dedicated configuration menu.
With the new Landing Page configuration, it is now possible to customize the NDE starting page.
Under Discovery Configuration > View Configuration > Landing Page > Links, it is possible to configure the labels for the Links section. However, other Landing Page labels are managed at IZ level under Discovery Configuration > Labels > Landing Page Labels.
For consortia or institutions with multiple views, this creates a limitation: labels that are not part of the Links section cannot be customized per local view in the configuration menu, but only by creating view level labels in the code table. As a…
7 votes -
Restore the "Other" A–Z browse category for Journal Search in Primo VE/NDE
Primo Classic Journal Search includes an Other browse category for journal titles beginning with punctuation or other non-alphabetic characters. Primo VE and the NDE Journal Search currently provide only 0–9 and A–Z, leaving journals whose titles begin with punctuation without an intuitive browse location. Please restore the Other browse option (or otherwise provide equivalent access) to maintain feature parity with Primo Classic and ensure all journal titles are discoverable through browsing.
Some titles that might make good examples for this would be:
@Tic : revista innovació educative
+E
# Tear
3 votes -
Add an option to disable direct linking for newspapers
The Alma Direct Linking configuration (see https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Direct_Linking_configurations_for_Alma_and_Primo) at the Alma Configuration > Fulfillment > Discovery Interface Display Logic > Direct Linking menu allows us to choose to "Disable direct linking for journals." This is an important option to select because we often have access to the same journal through multiple collections (a backfile collection, a current subscription, and an aggregator, for example), and each one might have different coverage dates. We want to disable direct linking for journals because direct linking would not allow the user to see the different portfolios with their different coverage ranges and select the one with the year coverage they needed. Direct linking takes the user to one of the portfolios, but not necessarily the one with the coverage they need.
The exact same scenario applies to newspapers: newspapers, just like journals, often can be accessed through multiple collections, each with different coverage dates. We do not want to use direct linking for newspapers either, as our users need to be able to look at the different newspaper portfolios to find the one with coverage dates they need. However, Alma does not have an option to disable direct linking for newspapers.
For example, see the record https://go.rutgers.edu/RULQS-kir2mhy3 in our Primo (also shown in the attached screenshot), which is for a newspaper, the St. Louis post-dispatch, which has several portfolios. Direct linking takes the user to the first portfolio on the list, Access World News, which only has coverage back to 1988. Some users, however, might need coverage back to 1923 and might need to use the ProQuest Historical Newspapers: Global portfolio instead.
This is made more confusing for the user by the way the direct link summarizes the coverage available across all portfolios. In this case, the direct link says "(Available from 1923)" because it is including the coverage from the ProQuest Historical Newspapers: Global portfolio. This makes the user think that clicking the direct link will take them to coverage back to 1923. However, clicking the direct link takes the user to the first portfolio on the list, Access World News, which only has coverage back to 1988.
Thus, I would like to suggest that because, for the purposes of direct linking, journals and newspapers essentially have the same considerations, and libraries who want to disable direct linking for journals will almost certainly want to disable it for newspapers as well, Ex Libris should either:
1) Change "Disable direct linking for journals" into "Disable direct linking for journals & newspapers" (if everyone agrees the use cases are identical) OR
2) Create a separate "Disable direct linking for newspapers" checkbox option (if anyone can think of cases where a library would want direct linking for one but not the other)I will attach mockups showing each of these options. Thanks for considering this!
The Alma Direct Linking configuration (see https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Direct_Linking_configurations_for_Alma_and_Primo) at the Alma Configuration > Fulfillment > Discovery Interface Display Logic > Direct Linking menu allows us to choose to "Disable direct linking for journals." This is an important option to select because we often have access to the same journal through multiple collections (a backfile collection, a current subscription, and an aggregator, for example), and each one might have different coverage dates. We want to disable direct linking for journals because direct linking would not allow the user to see the different portfolios with their different coverage ranges and select the…
-
Direct%20Linking%20configuration%20screen%20with%20new%20newspapers%20option.png 36 KB -
Direct%20Linking%20configuration%20screen%20with%20journal%20option%20changed%20to%20journals%20and%20newspapers.png 33 KB -
Primo%20newspaper%20result%20showing%20different%20coverage%20ranges%20for%20different%20portfolios(1).png 64 KB
3 votes -
-
Calculate and display physical availability on brief display for CDI records
For Primo VE/NDE, please calculate and display the physical availability on the brief display for CDI records.
Currently, in the results page, many records that are print plus online show only their online holdings in the results page for the brief records.
When a user opens one of these records, only then are the physical holdings calculated and displayed. Then when the user goes back to the results page, the physical holdings are now displayed in the brief record, but only after they have viewed the full record, not before.
This is an inconsistent user experience which is likely to cause confusion.
Consistently displaying the physical availability alongside the online availability on the initial results page at the brief record level, instead of only the online availability, would create a more consistent user experience as users review potential relevant records.
Thanks for considering. Sandra.
For Primo VE/NDE, please calculate and display the physical availability on the brief display for CDI records.
Currently, in the results page, many records that are print plus online show only their online holdings in the results page for the brief records.
When a user opens one of these records, only then are the physical holdings calculated and displayed. Then when the user goes back to the results page, the physical holdings are now displayed in the brief record, but only after they have viewed the full record, not before.
This is an inconsistent user experience which is likely to…
38 votes -
Make MyInstitution configurable: allow excluding specific record sets
SUMMARY
Libraries cannot currently exclude specific record sets from the out-of-the-box MyInstitution scope in Primo VE / NDE.
PROBLEM
MyInstitution (and derived profiles such as MyInstandCI) is a fixed, all-inclusive scope that cannot be modified.
This makes it impossible to centrally exclude a specific set of records (e.g. a whole digital collection) across all search profiles and views.
The recommended workaround is to create custom scopes and search profiles (e.g. “MyInstitution minus X”). However, this:
Requires duplicating and maintaining multiple configurations
Leads to inconsistent behaviour across tabs and profiles
Breaks existing permalinks that rely on the standard search profiles
This last point is especially critical, as Ex Libris recommends permalinks for stable access and sharing. Replacing out-of-the-box profiles can result in links that no longer resolve correctly or display the intended content.
PROPOSED SOLUTION
Allow institutions to exclude specific record sets from MyInstitution, either either by configuration (e.g. based on metadata or collections) or by allowing controlled adjustments to the scope itself.
For example:
Exclude records based on specific fields (e.g. MARC 990)
Subtract a defined collection or scope from MyInstitution
Apply global filters across all search profiles using MyInstitution
BENEFIT
This would enable consistent, scalable control over content visibility without breaking existing links, and remove the need for complex and fragile workarounds.
SUMMARY
Libraries cannot currently exclude specific record sets from the out-of-the-box MyInstitution scope in Primo VE / NDE.
PROBLEM
MyInstitution (and derived profiles such as MyInstandCI) is a fixed, all-inclusive scope that cannot be modified.
This makes it impossible to centrally exclude a specific set of records (e.g. a whole digital collection) across all search profiles and views.
The recommended workaround is to create custom scopes and search profiles (e.g. “MyInstitution minus X”). However, this:
Requires duplicating and maintaining multiple configurations
Leads to inconsistent behaviour across tabs and profiles
Breaks existing permalinks that rely on the standard search…
26 votes -
Allow configuring default view (List vs Thumbnail) in Collection Discovery
SUMMARY
The default Thumbnail view does not support effective browsing for text-based collections in Primo NDE.
Currently, libraries cannot configure the default display mode (Thumbnail view vs. Detailed/List view) for Collection Discovery pages. We request the ability to define List view as the default, or to configure this per view or collection.
PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS
Thumbnail view prioritizes visual browsing, but many collections do not contain meaningful or distinctive visual material.
This applies in particular to:
- Student theses
- Scholarly publications
- Institutional repository contentThumbnails are often missing, non-informative (for example showing the first page of a PDF), or highly similar across records.
As a result, the interface shows very limited metadata, often only the title. Important information for selection and comparison is not visible, such as:
- Publication year
- Availability status (open access, embargo, or restricted)
- Abstract or summary
- Author informationThis makes browsing inefficient and forces users to open multiple records to find relevant items.
USER STORIES: METADATA-DRIVEN DISCOVERY
Student (exploratory browsing)
As a student exploring theses or scholarly publications, I want to quickly scan metadata such as year, topic and availability, so that I can identify useful examples without opening each item.Academic staff
As an academic staff member reviewing output, I want to see structured information (year, title, supervisor, completeness) directly in the results list, so that I can efficiently assess coverage and quality.Researcher
As a researcher browsing a publication collection, I want to compare items using metadata, so that I can identify relevant materials without relying on visual cues.
USE CASE: CURRENT VS DESIRED BEHAVIOUR
A user opens a thesis or publication collection in Primo NDE.
In the current Thumbnail view:
- Only titles are clearly visible
- Thumbnails are absent or not meaningful
- Key metadata is hidden
- The user must open multiple recordsIn a Detailed/List view:
- Multiple metadata elements are immediately visible
- Users can scan and compare efficiently
- Fewer clicks are required
- The browsing experience matches the content typePROPOSED SOLUTION
- Allow configuration of the default display mode for Collection Discovery (Thumbnail view or List view)
- Allow configuration per collection or per view, so institutions can match the view to the content type (e.g. images vs text-based collections)
This flexibility would significantly improve usability and reduce the need for local customizations.
SUMMARY
The default Thumbnail view does not support effective browsing for text-based collections in Primo NDE.
Currently, libraries cannot configure the default display mode (Thumbnail view vs. Detailed/List view) for Collection Discovery pages. We request the ability to define List view as the default, or to configure this per view or collection.
PROBLEM: THUMBNAILS DO NOT SUPPORT TEXT-BASED COLLECTIONS
Thumbnail view prioritizes visual browsing, but many collections do not contain meaningful or distinctive visual material.
This applies in particular to:
- Student theses
- Scholarly publications
- Institutional repository contentThumbnails are often missing, non-informative (for example showing the first…
29 votes -
Provide confirmation when item has been added to a reading list
In both Primo VE and Primo NDE, no confirmation is given to the user after adding a title to a reading list. The Add to Reading List box simply closes with no indication about what has occurred.
Recommend adding a status message so that users are aware the item has been successfully added, avoiding uncertainty and potential repeated actions.
3 votes -
Option to have more than 5 results from Primo Research Assistant query
In the current release of Primo Research Assistant, it provides the 5 most relevant results with an instant overview. Sometimes, a query returns more than five highly relevant results. Hopefully, the Research Assistant will offer users the option to view more than 5 results in the future.
1 vote -
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 -
Re-design NDE Get it section
Our suggestion (see attached file and image) is to re-design the get it section for the NDE, so that it become more compact and reduce the number of clicks needed to display all information.
In this idea it remains fundamental that libraries can configure which information display and in which order, that is optimized also for mobiles, that it works well with journals and that "filter" by number or year option keep on working
The status of the items could also be indicated using colors: for example, Item in Place in green, Out of Library in grey, ...Note: we did add also "loan" and "digitization" options at item level in this mockup, but we strongly believe that these should moved in the "Request" section.
Our suggestion (see attached file and image) is to re-design the get it section for the NDE, so that it become more compact and reduce the number of clicks needed to display all information.
In this idea it remains fundamental that libraries can configure which information display and in which order, that is optimized also for mobiles, that it works well with journals and that "filter" by number or year option keep on working
The status of the items could also be indicated using colors: for example, Item in Place in green, Out of Library in grey, ...Note: we…
4 votes -
PRIMO Advanced Search: Reduced Usability After Latest Update
Hello,
In the latest PRIMO update, the Advanced Search has become less efficient and less intuitive for daily use.
Previously, it was possible to quickly edit search fields directly within the interface. Now, even small changes (such as editing a title) require reopening the edit screen, which adds extra steps and slows down the workflow.
For librarians who rely on Advanced Search, this reduces usability and productivity. I would appreciate it if you could consider restoring the previous, more intuitive and streamlined editing experience.
Thank you.
2 votes -
Integration of Institutional AI Research Tools with Primo Research Assistant
Primo Research Assistant should support integration with external AI research platforms, such as LeapSpace, Scopus AI, Web of Science Research Assistant, Elicit, and other emerging research tools. This would enable researchers to access insights and capabilities from multiple AI-powered services through a single Primo interface, eliminating the need to switch between platforms.
Currently, researchers often need to move between multiple AI platforms to access different features and content sources. Integrating these tools with Primo Research Assistant would create a more seamless research experience and position Primo as the central hub for AI-assisted discovery.
Benefits of this enhancement include:
• A single point of access to AI-assisted research services.
• Reduced need for users to switch between multiple platforms.
• Improved researcher productivity and workflow efficiency.
• Better utilisation of institutionally licensed AI tools.
• More comprehensive responses by drawing on multiple trusted scholarly sources.
• Greater flexibility for institutions to integrate current and future AI research platforms.This enhancement would help libraries maximise the value of their AI investments while providing researchers with a more unified and efficient research experience.
Primo Research Assistant should support integration with external AI research platforms, such as LeapSpace, Scopus AI, Web of Science Research Assistant, Elicit, and other emerging research tools. This would enable researchers to access insights and capabilities from multiple AI-powered services through a single Primo interface, eliminating the need to switch between platforms.
Currently, researchers often need to move between multiple AI platforms to access different features and content sources. Integrating these tools with Primo Research Assistant would create a more seamless research experience and position Primo as the central hub for AI-assisted discovery.
Benefits of this enhancement include:
• A…7 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 -
Add the funtionality of Add Row to all Labels
As of now it possible to create copies of Labels to be used in specific views, so that the Label better correlate with the intended user group for that view, by the funtion Add Row.
However, this isn't an option an all different kind of labels. We suggest that this functionality should be available on all labels, so that the library better can customize their different views.
4 votes -
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.
4 votes
.png){kind=link}
- Don't see your idea?