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.
493 results found
-
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 -
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…
53 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…
52 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.
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.38 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.
46 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…92 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…
24 votes -
Inform patrons about Pick from Shelf
This is something we are really missing since we switched to Primo VE.
I find a book I want to borrow, my library has it, but it's open stacks, which means I can't request it online to be picked up in the owning library.
In our older catalog we had a pop up message to inform the patrons that they can fetch the item from the shelf themselves.
DTU (https://findit.dtu.dk) solves it like this, which is exactly what we need - see screenshot dtu1.png
Under B, we'd show the possible pickup locations, as we do now.
A is…
35 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 -
Primo Header is cut off at a certain Window Size
When one reduces the size of the browser window, the button for the advanced search moves into the “hidden” menu. Right before it disappears, it is cut off and can no longer be read. Furthermore horizontal scrolling is required in order to visually grasp the other menu items such as "Login" and "Menu". As far as we could check, this affects a browser window size from around 600px to 800px.
This does not depend on local CSS modifications. It is a general UX issue that affects responsive design and furthermore is breaking with the WCAG accessibility guidelines (WCAG 2.1, 1.4.10, …
61 votes -
HTML Language Tag customizable for Screen Readers
In order to improve the accessibility of Primo, it would be helpful if one would be able to choose country-specific language settings for screen readers by the HTML language tag. We would be interested in the language setting “de-AT” to be available to recognize the Austrian variety of the German language. This could also be interesting for a lot of other languages.
63 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…
20 votes -
Improve resource accessibility with a new field «Request accessible document» in “Digitization optional parameters”
To provide better access to resources for users with disabilities, ETH Library would like to offer its users accessible digital copies. This service requires an additional field in the digitization request form in Primo VE, in which users can indicate if they would like to request an accessible document. This field could be named “Request accessible document” and be added to Discovery > Configuration > GetIt > Digitization optional parameters, so that libraries can enable and disable the field as they like. We think that it would be best if there was a dropdown list available for this field with…
48 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 -
Article level records from Alma should populate resource sharing form correctly
Article records from CDI will populate the Primo VE resource sharing form correctly, as a document delivery option for when there is no full-text available.
However, when it comes to article level records from Alma, the Journal title is incorrect (instead, the article title is entered into this field) and other information is missing, like publication year, volume, etc. Overall the article is not recognized in the Context Object as an article, but instead treated as a journal - thus omitting all fields not relevant to a journal record.
Example:
1 - Go to: https://kbdk-kgl-psb.primo.exlibrisgroup.com/permalink/45KBDK_KGL/1pioq0f/alma99124396529705764. See that the resource…50 votes -
Remove resource sharing links from records for electronic and print books, but not chapters
It is currently not possible to create a GES or DLR that would prevent RapidILL resource sharing links from appearing on CDI records for electronic and print books. The only way to do so is by removing them from ALL books, which would also exclude the link from book chapters. "Exclude CDI ebooks" helps by removing some of these records from results, but there are exceptions with e-books in database type collections. This more granular functionality is highly needed, as requests for entire books cannot be granted through RapidILL and must be cancelled.
12 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…
207 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 -
Open Access articles to display in full text results
Currently, if only displaying CDI results with full text, articles tagged as open access aren't included. These are only displayed if the user toggles to show results with no full text.
Ideally, articles tagged Open Access would also be included when displaying results with full text. The tag would need to bypass the link resolver process so those results are also included.
This would reduce the number of users putting in ILL requests when they didn't realised the article was available OA.
18 votes
- Don't see your idea?