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.
508 results found
-
Allow Online Services Order to sort by current access
We need the ability to move to top of View It a service with current access (this means the coverage statement is open-ended, ie Available from 1998 - current).
Users get overwhelmed with the long list of services often displayed, and ordering the list according to interface or electronic collection name doesn't address the most important aspect, whether there is current access or not. As an example, on Proquest interface Z, journal title X may provide current access, but journal title Y on the same Proquest interface Z may only have archive access. We only want to put journal title…
231 votes -
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…134 votes -
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…109 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,…
75 votes -
Modernize purchase request from customisation
The Rialto purchase request form has a much improved user experience for requesters, a modern style and simpler, more flexible configuration. Its downfall is that it has NO authentication. The product team have reviewed this idea (https://ideas.exlibrisgroup.com/forums/940011-rialto/suggestions/46699696-enable-authentication-on-purchase-request-web-form) and advised that adding authentication does not fit with the Rialto roadmap.
There are some disappointed Rialto customers at this news. Libraries have indicated that they cannot use the Rialto form because it has no authentication.
However, providing an improved UX for the purchase request form used in Primo would benefit many more libraries and their thousands of customers - and…49 votes -
Create option within Entire Network Inventory to display All Physical Inventory (regardless of availability)
This concerns Custom Local Data Scopes. Currently, the only physical option within Entire Network Inventory is to display Available Physical. This means that when there is a physical item that only we hold within our consortium, but is out on loan, that we cannot see our own item in PrimoVE. And for this reason, we also cannot order the item via interlibrary loan – because there is no record. Further, the record will exist in other catalogs (e.g., WorldCat), but when the user clicks on our institution from those other catalogs, it results in a dead-end loop for the user.…
49 votes -
Primo VE mobile device enhancement
When using Primo VE on a mobile device, such as a mobile phone, if you change from portrait to landscape and then back to portrait, half of the page will become blank, which is not conducive to readers' viewing.
103 votes -
Enable person entity functionality at the view level
The new feature (May 2024) for person entities is either on or off for all views.
For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.
Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from…
61 votes -
Provide option to disable course information being indexed for search in Primo VE
We have chosen not to display course information in our Primo VE but found that local records appear higher in our search results when they are attached to a Leganto reading list. Support tell me that 'it is part of OTB and by default it will be indexed’.
In the ‘Search Section Mapping’ part of the 'Mapping to the Display, Facets, and Search Sections in the Primo VE Record' Knowledge Center page, it says: 'Course information – Primo VE indexs the course name, code, and instructor for records associated with course reading lists.'
We don't understand why course and instructor…
32 votes -
Resource Recommender Statistics for Individual Items
Primo Analytics for Resource Recommender analytics currently shows only number of selections by resource category but not for individual records within each category. We would like to use detailed statistics for annual usage review and and RR maintenance. Particularly for databases, we would like a more straightforward option to see clicks through RR.
From two previous ideas that were both closed: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/30982855-better-analytics-for-resource-recommender-to-tell#{toggle_previous_statuses}
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45030058-resource-recommender
21 votes -
Display import profile name also for for failed import jobs
Currently, the scheduled job "Import Data to Primo VE" gives us the name of the import profile/external data source that was harvested, but only if the job ran successfully. If not, only the name of the job will be given, but not which profile it ran on. This is true both in Alma and for the corresponding e-mail notifications. We would be glad if this could be changed so that the profile name is always displayed, as the current behaviour is making troubleshooting issues with the import profiles quite cumbersome, especially if several are affected at once.
40 votes -
Improve Citation Action
We would like to summarize in this idea exchange several issues we have run into with the citation action that inhibit the usefulness of the functionality for our customers greatly. Most of these relate to a lack of language sensitivity on the incoming side of the citation action. We would think it would be good if Ex Libris could work towards an improvement here, maybe together with the Citation Styles Language Project.
The formatting for the page count should be p.DDD-DDD or p. DDD-DDD in 773 $$g according to Ex Libris. The issue with this is that when our cataloguing…
54 votes -
Allow Customization of Link Prioritization in the Merged Record to prioritize OA
Currently, when there is a merged record with multiple links, the links are prioritized according to a fixed set of prioritization rules (https://knowledge.exlibrisgroup.com/Primo/Content_Corner/Central_Discovery_Index/Documentation_and_Training/Documentation_and_Training_(English)/CDI_-_The_Central_Discovery_Index/050CDI_and_Linking_to_Electronic_Full_Text#Link_Prioritization_in_the_Merged_Record). In general, the rules prioritize links to paid content over links to unrestricted (OA) content. For example, if all records in a merged group are coming from collections using link in record, Link in Record links for subscribed content are prioritized over OA links. As another example, if some records in a merged group use the link resolver, and some use link in record, link resolver links for subscribed content are prioritized over the OA…
40 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…
43 votes -
Index Item Description in Primo VE
We record the monographic titles of periodical issues only in the Item Description field and not in the periodical bibliographic record.
This item field is searchable in Alma but not in Primo VE.
We need that the Item Description field to also be searchable in Primo VE.41 votes -
Primo VE - Allow normalization of Esploro records
As a discovery tool Primo VE is supposed to deliver a unique gateway to many Library Resoures, including the a Institutional Repository (i.e. Esploro ).
To do so in a blended search one must be able to normalize records from different sources. We used to do that in Primo Classic, with a Pipe and a Normalization Rule. This is however not possible in the newer Primo VE.
Please allow manipulation and normalization of Esploro assets so that we can show them in the catalogue in a consistent way.42 votes -
Change how permalinks work
The permalinks provided by Primo do not link to a specific Alma record; instead, they save the result of a search in Primo. This means that when we copy a permalink for a title included in a course, what we are doing when using it is initiating a search for that title in the recommended bibliography collection. Therefore, if that title is no longer included in a course, the permalink we had copied stops working. This is not very useful.
We request that the permalinks provided by Primo be truly permanent and always direct to that Alma record, without changes.…11 votes -
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…
30 votes -
Discovery collections handling
When creating or updating an Alma collection (adding/removing titles), the change is not automatically reflected in the Discovery Collections and it is necessary to trigger the reindexing for a correct display.
This workflow is problematic when titles are removed: records are taken out from a collection but are still present in Primo VE because a reindexing is needed. They can no longer be found by searching for the collection in Alma. Depending on the collection, it might also not be possible to find them all via a single search and it might be necessary to manually add the records to…104 votes -
Customise Purchase Suggestion Form material type list
The Purchase Suggestion Form in Primo VE currently offers a drop-down menu of all possible material types, including things like Ephemera, Toys, and Vinyl LP, which we don't want to turn off as a material type option but we also don't want to offer as a purchasing possibility. At the moment there's no way to switch off material types from that dropdown without removing them as an option for new items completely. We would like an option to customise this purchase suggestion form material type list with more flexibility.
47 votes
- Don't see your idea?