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.
679 results found
-
Add an "audiobook" indicator to CDI records
We want to make it possible for our users to facet to and search more effectively for audiobooks.
In CDI records, both non-musical and musical audio materials have the same resource type, audio, and there is no way to distinguish between non-musical and musical audio materials. Our researchers have identified this as an accessibility issue and barrier for use because they are not able to identify audiobooks in our Primo catalog. Locating audiobooks is important both for general research and to provide access for those needing audio formats.
For local records, we can identify audiobooks by creating local/secondary resource types…1 vote -
Primo NDE - Display Availability and Access Rights Indicators on Brief Result Cards in Collection Discovery
User Story:
As a library user browsing digital collections,
I would like to see availability statuses and access rights indicators (e.g., "Open Access", or a restricted access icon) directly on the brief result cards (thumbnail and list views) in the Collection Discovery lobby,
so that I know immediately if a digital file is accessible to me without having to click through to the Full Record Display.Current Problem:
Currently, brief result cards for Alma-D records in Collection Discovery lack any visual indicators regarding an item's availability. Users frequently click on items only to discover they do not have the rights…2 votes -
Allow changes to Rapido expected delivery date
While most Rapido digital requests are delivered within 24 hours, we experienced cases in which this was not true. Patrons come to expect this rapidity and are disappointed when the article arrives after more than one day.
If we could alter the expected delivery date (not just the hours label), it would be helpful. Even if most requests are received within 24 hours, changing patrons' expectations would be helpful.
Thank you for considering this idea!
3 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 -
Code free Primo Customizations - Like modern web builders that allow customization without knowing html and css coding.
A lot of web builders have the ability to create fully functional web sites with fully editable text, images, colors, fonts, etc. so that users don't need to know any coding language, like WIX... it'd be great to see that kind of ease of use when configuring Primo NDE for things like background images, quick link boxes, custom text fields, etc.
6 votes -
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 -
"Library" sort for Network Zone participants
Primo searches for Network Zone participating libraries can be configured to include NZ-linked records that are not held by a user's home library/institution. In these types of searches, non-available content is often ranked above available content (see "problematic ranking" screenshot). Users can use facets and/or different search profiles to just see what is available at their home library. We'd like for there to be something of a compromise between these two extremes (getting buried in non-available content vs only seeing available content). It would be something akin to the "Library" sort available to WorldCat Discovery users, where available content would…
12 votes -
Following GDPR Compliances in Digital Wallet App Development
With the rapid growth of digital payments, data privacy and security have become major concerns in eWallet app development. Since digital wallets handle sensitive financial and personal information, complying with regulations like the General Data Protection Regulation (GDPR) is essential for protecting user data and building trust.
GDPR requires businesses to implement strong data protection measures such as user consent management, secure data storage, encryption, data minimization, and the right for users to access or delete their personal data. For companies developing digital wallet apps, ensuring compliance with these regulations can help avoid legal risks while also improving transparency and…
1 vote -
Publish the algorithm to create permalinks
Currently the permalinks in Primo contain a secret key which customers can't generate programatically. Using a secret key at all in a URL that is a permalink is questionable.
Permalinks that are dependent on internal secrets and operational details are not in the spirit of nature of long-term commitment.
Permalinks that can't be programatically created based on public available data are also very hard to debug and integrate with external services.
Permalinks should not be dependent on any operational details (for which no long-term commitment can be guaranteed).
Publish the algorithm how this secret key can be calculated or make…
17 votes -
Apply the Primo NDE color theme to Primo Research Assistant
In the Primo NDE interface, the selected UI color theme is not applied to the Primo Research Assistant (RA).
Even when a custom theme color is configured for the NDE view (e.g., orange), several RA interface elements still appear in the default blue color, such as:
- the AI stars icon
- the "Start a new topic" button
- navigation arrows in the RA interface.According to Clarivate support, this behavior is expected because the RA interface is controlled by CDI rather than Alma customizations.
Expected behavior: The selected NDE UI color theme should also apply to the Primo Research…
38 votes -
Support MARC field 857 (Web Archive Links) in Primo VE
Please add support for MARC field 857 in Primo VE so that links stored in this field can be displayed in the Links section, similar to MARC field 856.
Field 857 is increasingly used by libraries to store links to archived versions of web resources (e.g., web archive snapshots). Currently, these links are not displayed in Primo VE, even when the field is present in the MARC record.
Supporting field 857 would allow libraries to expose web archive links and preserved web content directly to users and better support web archiving and digital preservation initiatives.
Why this helps many institutions:
…
1 vote -
Dedup and FRBR Test Utility
Could the Dedup and FRBR Test Utility (Configuration/discovery) have the ability to remember the last MMS ID numbers that were looked up? We seem to spend a lot of time going back and forth to the same records trying to get them to match and having to find and paste in the MMS of both, e.g. the print and the eBook records - usually from the Primo URL where I invariably pick up the preceding word, Alma. It would be great if it retained the last couple of MMS searched for to save a bit of time and effort.
1 vote -
NDE UI - Improving UX locations section
The request buttons on item-level are not easily found by our users.
Please note, we have activated item-level requesting for all records, because it seems more logical and straightforward to have all the request buttons in one place. We do not believe returning to title-level requesting is the solution here, but enhancements in the locations section in the NDE UI could improve the experience.The various UX-issues of the locations-section are:
The 'arrow' button is not a clear button
Customers gave us feedback that they find it hard to see you can elapse or collapse cards. They blantly state that…
-
current-situation-4.png 4 KB -
current-situation-3.png 95 KB -
improvement-with-CSS-customization-3.png 76 KB -
improvement-with-CSS-customization-4.png 76 KB -
current-situation-1.png 48 KB -
improvement-with-CSS-customization-1.png 23 KB -
current-situation-2.png 75 KB -
improvement-with-CSS-customization-2.png 57 KB
29 votes -
Allow an institution (IZ) (Alma/Primo VE) to exclude in retrieval 7XX fields with $5 from another institution within the same Network Zone
In our Network Zone, we work with unique bibliographic records shared by several institutions. The MARC21 7XX subfield $5
is used to indicate local information specific to each IZ.Currently, in Alma and Primo VE searches, 7XX fields containing a $5 from other IZs are included in retrieval and affect
the Dedup and FRBR grouping processes within an IZ. We can only hide these fields from user display by configuring Primo VE rules.
As a result, records retrieved in a Primo VE view of one IZ may include data that are strictly local to another institution and may
even influence…15 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 -
Ability to configure the Update Password option in My Library Card by user type
We have both internal and external users in Alma. We want to display the option to Update Password to internal users who have their passwords stored in Alma and hide the option for external users who are authenticated via SSO and cannot update passwords via Alma. However at the moment it shows for all users, which is confusing to external users who cannot use this functionality.
17 votes -
Separate display configuration for names in Primo
To configure the order in which a user's first name and last name display in Primo VE (which displays as initials in the top right corner of the screen of NDE) we need to configure the Alma User Details settings. However, in Alma it is easier for us to work with names ordered 'last name, first name' however in Primo we need to order user names 'first name last name' for their initials to show correctly.
Please provide Primo VE with its own configuration settings for the display of a user's name.
5 votes -
Add a field "Author Affiliation"
Could you please add the field "Author Affiliation" for display? Currently, "Author Affiliation" is not displayable in Primo but only in search.
1 vote -
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 -
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
- Don't see your idea?