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.
258 results found
-
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…102 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.
97 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 -
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…
53 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 -
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.
36 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…35 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.41 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…
28 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…101 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.
44 votes -
More DEDUP keys
The implementation of the FRBR keys is affected by the DEDUP keys, so it would be desirable to add a new key in the DEDUP keys that includes the label 250.
106 votes -
Exclude Esploro assets with no inventory from Primo blended searches
We would like an option to be added the Primo configuration to enable only Esploro records with inventory to be searched in a blended search with Alma and CDI records.
In the current configuration a search profile slot can be created in Discovery > Configure Views > Search Profile Slots to search across all resources (Alma, CDI, Esploro etc.). It is possible to include the ResearchHasInventory option in this slot but the result of this in Primo is that it only allows users to search either the blended (Alma and CDI) option OR the ResearchHasInventory option but doesn’t enable both…
22 votes -
Allow customization of CDI resource types in Resource Type Filter Bar
We are using the Resource Type Filter Bar with general satisfaction, with one major problem. Since Articles and Magazine Articles are separate CDI resource types now, and it isn’t possible to select more than one resource type pre-filter (in Simple or Advanced Search) -- it’s not possible to allow the user to search within both types of articles. There are some magazine articles that seem good to exclude, but there are others that are scholarly sources, even Peer Reviewed, and I fear our users may miss them. Ideally, we might want to enable the search within both types and allow…
6 votes -
In the Display Logic Rules, add the option to "hide service" with "Availability by the network" for Network Zone Resource Sharing
In the Display Logic Rules, add the option to "hide service" with "Availability by the network".
We are in a Network Zone consortium that does Resource Sharing. Right now, we can hide services like "Purchase Request" if the item with "Availability by the institution" or "Ownership by the Institution" is true, but we also want to hide it for availability in the network, so that patrons are forced to try Resource Sharing in our network first, rather than submit a Purchase Request.
14 votes -
Automate SSL/TLS certificate management
For hosted Primo sites that have custom domain names, the current process for deploying SSL certificates involves time-consuming manual steps and hand-offs, many of which must be repeated each time a certificate is renewed. [1]
Several institutions will soon require SSL certificates to be renewed every 90 days, at which point the current manual process will become utterly unmanageable for both Ex Libris and its customers. [2]
I propose that Ex Libris adopt an ACME-like service (such as Let's Encrypt) to fully automate SSL certificate management. The customer's responsibility would be to set up a DNS record (as they do…
216 votes -
Person Entity – Option to hide or suppress the Person Page and Person Info Card at the individual level
We propose adding the option to allow institutions to hide or suppress the Person Page and Person Info Card at the individual level.
We've received complaints that some person entities display incorrect information on their pages. As updating information directly at the data source (Library of Congress, Wikidata, or Wikipedia) is neither sustainable nor predictable in terms of when data changes will be reflected, we propose providing an option for institutions to exclude specific person entities from being displayed in Primo.
Justification:
1. Updating Wikidata and other data sources entries directly is not a sustainable solution and is not predictable…8 votes -
Person Entity - Ability to Opt Out from Wikidata
We propose adding an option to opt out of using Wikidata as a data source for the Person Entity feature in Primo at the institution level and the individual entity level.
We have received complaints that the data provided by Wikidata for the Person Info Card and Person Page is incorrect or misleading for certain individuals. Currently, the only way to address these issues is by editing the Wikidata entries directly, which is not a sustainable solution and is dependent on the timeliness of weekly updates. To provide a recent example: we updated a Wikidata entry to correct the occupation…
8 votes -
Holding and coverage details in brief record display for physical records
Primo VE can show the title, general physical availability, and other details in the brief record display of a given record, but it lacks the ability to show coverage information that's contained in a holding record. All current details that Primo VE can show appear to be either bibliographic or system data, but not holding record data. We'd like to have this kind of coverage information available to users at a glance without their needing to enter a record to see which issues/years/etc. of an item that we have.
7 votes -
Journal Search: Consider the NZ activation for e-resources with Inventory Management Groups in the IZ
Our consortium activates Open Access e-collections in the Network Zone so that they are available in every IZ of the network. Electronic collections for Open Access e-resources are activated without any Inventory Management Group assigned to it. It should display for every IZ and every Inventory Management Group within the IZ.
Some of the licensed e-collections in the IZs also cover e-resources that are activated in the NZ as Open Access. (Journals can have partial Open Access) The IZs are using Inventory Management Groups, and the local views are assigned to the campuses of the specific Inventory Management Groups. The…51 votes
- Don't see your idea?