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
-
Display Number of Renewals on Patron Library Card in Primo VE
Currently, Primo VE does not display the number of renewals for a patron’s loans on the patron’s library card. We propose an enhancement to allow the number of renewals (used and/or remaining) to be displayed in Primo VE for patron loans. This should appear on the patron’s library card.
Providing this information directly in Primo VE would improve transparency for patrons.4 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 -
IZ level view configuration
As a library network with a large number of Primo views, it can be extremely laborious to update every single view for configuration options that are identical in each view. These include in particular all configuration options that can be found in the General, Links, Advance Search, Brief results, Brief record display and Full Record Services tab of the view configuration menu.
This kind of centralised view management would need to be available at the IZ level as it does not fulfil the same purpose as the possibility to distribute configuration from the the Network Zone to the various Institution…
124 votes -
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 -
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 -
Related titles in Primo VE records display: separate window
When records have bib-to-bib relationships via 8XX (or 7XX), the list of related titles is displayed in the Details section of the series/host record. Unfortunately, the list is currently sorted alphabetically by the title, which is very user-unfriendly with a large number of linked titles.
This behavior has already been criticized in this idea. Unfortunately, it is still not possible to sort the related titles logically by sequence or volume.
The Austrian Library Association (OBV) uses Primo BO and has implemented a user-friendly solution for displaying related titles:
In the case of multi-volume works and series, the individual volumes are…145 votes -
Resource Recommender by user group or campus
Resource Recommender in Primo VE can only show suggestions based on search tags or “Display Always.”
There’s no way to show recommendations based on who the user is — for example, their user group, campus, or department.
This means libraries can’t personalize results - such as:
Business students see business databasesThis would make the discovery experience more relevant and user-friendly.
7 votes -
Configuration for cubicle or space reservations
Currently, the resource and space reservation functionality in Primo VE is very limited. It is necessary to enable configurations that make the reservation process faster and simpler. Among the required improvements are:
• Adjusting the available reservation times according to the Library's opening hours, avoiding displaying time slots that are not relevant.
• Allowing the Library team to configure only certain days, instead of automatically enabling all days.
• Unifying the calendar system so that a single calendar is used to select the reservation date, instead of one for the start and another for the end.1 vote -
Integrated Library Mapping and Analytics for Primo VE
Develop an integrated library mapping module for Primo VE featuring interactive floor plans with clear, step-by-step directions. Seamlessly integrate this module into Primo VE's existing infrastructure, ensuring a user-friendly interface accessible to all patrons.
Benefits:
• Enhanced user experience: Streamline the path from digital search to physical item retrieval, reducing frustration and improving overall user satisfaction.
• Valuable collection analytics: Gain insights into patron behavior, optimize collection placement, and make data-driven decisions about space allocation.
• Streamlined workflow: Replace third-party solutions, reducing complexity and simplifying library operations.
• Improved accessibility: Ensure all users can easily navigate the library by providing…112 votes -
Allow institutions to exclude the 776 from the CDI holdings file
Proposal: allow institutions to exclude the 776 from the CDI holdings file
Problem: sometimes local services for book title X in a series get matched to CDI records for book title Y (a different title in the series). Users click on the service and are taken to the wrong book, which is frustrating. According to Ex Libris, Alma uses the 776 field to generate the holdings file that is sent to CDI to calculate availability, and this is what causes the incorrect matching.
The solution of removing identifiers from the 776 as outlined in this Knowledge Article is not feasible,…
84 votes -
Users should be able to request individual volumes from multi-volume record
We have a record that has multiple volumes of the same manga in it.
The individual volumes are impossible to request for the user. This has to be done on the Alma side by a staff person. We would like records like this that have multiple volumes to have requestable individual volumes.
6 votes -
Add autocomplete to embedded searchbox
Please add autocomplete to the embedded searchbox API for a consistent user experience.
1 vote -
Support for Numeric Subfields (e.g., $0, $1) in MARC to PNX Mapping in Primo VE
Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.
Please map at least subfields $0 and $1 to PNX
This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .Use Case Example:
A record with multiple subject headings (650 fields) includes…35 votes -
Continue as Guest link on the authentication page
To encourage more users to sign in to Primo, we would like to provide more links on our public website, in emails, and through signage that direct users to specific pages in Primo, such as the AI Research Assistant or My Library Account. These require authentication first. While this works for our current staff and students, such links may also be clicked by people who do not have an account.
In this scenario, they are stuck on the authentication page with no option to opt out and get to the landing page. There is no top menu for them to…
1 vote -
AI based tool for suggesting alternative search queries to users with saved searches and email alerts
I was wondering if there could be an AI based tool for suggesting alternative search queries to users who have saved searches and have set email alerts. When they receive an email alert they could be suggested an AI generated search query (similar to what the AI Research Assistant could elaborate, with synonyms and boolean operators) to be checked for more results.
1 vote -
Person entity - add an option for users to request more information about a person
Many Person Info Cards have little/no information. An option for users to request more information about a person would give user communities agency to prioritize authority work by information professionals.
5 votes -
Person entity - add an expandable text option that can be customized by institution
Add an option to add explanatory text to the Person Info Card and Person Page, so that institutions can provide users with more details about these features in the interface. Transparency around the data presented by libraries in discovery interfaces is increasingly important with the proliferation of ai-generated content and users' understandable lack of trust.
5 votes -
Granular Control for Alma Viewer and Digital Versions Tab in Primo NDE
Description:
In Primo NDE, the rule “Hide service: Representation Delivery Service” affects both alma-viewer-content and the Digital Versions tab (nde.brief.results.tabs.digitalVersions). In contrast, Primo VE allows institutions to independently control visibility of the Alma Viewer and the Digital Versions tab.
This enhancement request seeks to restore this level of granular control in Primo NDE. Specifically, institutions should be able to:
Hide the Alma Viewer for certain representations (e.g., auxiliary or restricted content)
Still display the Digital Versions tab for those same representations
This would provide the flexibility needed for managing multiple representations of a record while ensuring users can discover digital…
3 votes -
Pair display of 880 fields with their linked MARC field
When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).
In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare…
115 votes -
Allow Print option in Primo VE to print Quick Access representation along with metadata
When using the "Print" command in a Primo full view record, the print screen shows a record's metadata. However, if the record has a digital representation in the "Quick Access" section (as might be the case in a record managed by Alma-D), the image is not included in the print page. Having the option to include the representation would be helpful in cases where a printed image is needed alongside its metadata.
2 votes
- Don't see your idea?