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.
1130 results found
-
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…79 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.
103 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, …
58 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.
60 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…54 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…
30 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…
38 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…
189 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…48 votes -
Ability to edit the OTB (Out-of-the-Box) search and facet rules in Primo VE
We would like to be able to edit the OTB search and facet rules. This is necessary for parity with PBO. There are several things that we were able to do in PBO that we cannot reproduce in VE because of the lack of this functionality. In the PBO OTB author search and facet, we were able to include dates and qualifiers from names in the LCNAF, which improved precision. In the OTB language facet, we were able to include intertitle, caption and audio description languages, which are not currently included in the VE OTB index. On the other hand,…
391 votes -
Item - Searchability of Public note in Primo VE
We use the Public note of the item for provenance information. For this reason, the field contents should be searchable in Primo VE.
68 votes -
Primo VE: enable search fields for the deepURLs
InPrimo VE, in the "search" : {} section of the PNX record there are some fields that are still not searchable,
like the "unimarclocalfields". It would be nice if all these would be accesssible with the deepURL query parameter
I.E.: query=unimarclocalfields,contains,XYZ.32 votes -
Reference to public licenses of other institutions within the consortium
Public licenses can be viewed in Primo VE's electronic holdings information area, but public licenses are not displayed in the electronic holdings display area of other institutions.
I would like to be able to display public licenses from other institutions within the consortium on my own institution's Primo VE.
Without this function, I think that being able to view information on other institutions' electronic holdings would have little effect.
Detailed information is attached.45 votes -
Remove the total number of results
It would be useful if the total number of results are hidden by default from the search results page, but patrons have the option in their user account settings to enable the total number of results.
3 votes -
Enhance Primo Subject to Track the usage statistics by MMS ID and country
Enhance Primo subject to track the usage statistics (specifically downloads and views) by MMS ID and country of download.
9 votes -
Add option to filter out Global title index results without any offer
When creating a scope that include CDI records non filtered per availability (Rapido-CDI expanded index), Global title index without any offer (no Get it section, no view online section and no item available in the Rapido tile) are retrieved (example). These records are owned by libraries participating in any POD (outside of ours) of Rapido.
We would like to have an option to exclude the Global title index results without an offer.
82 votes -
Privacy in patron letters
Currently, patrons receive detailed item information in patron letters. We would like to make it possible for patrons to turn off letters (such as when they do not want this detailed information living in their email accounts).
In testing, we found that the current 'Personal Details' configuration in Alma (https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/060Library_Card_Configuration/Configuring_Personal_Details_Settings_for_Primo_VE) does not allow us to limit patron changes to ONLY the notification preferences.
24 votes -
Make the PIN code field in Primo My Account a secure text field with eye icon to show/hide the PIN
As a user, I would like to have the possibility to hide the values I have entered in the Pincode field (Update Login Credentials in My Account > Personal Settings) so that the data isn't visible to others. In order to check for typos, I would like to have the possibility to display the data (e.g. by clicking on an eye symbol)
93 votes -
Allow "Exclude cdi ebooks" to apply only to the filtered search
The Exclude CDI eBooks option on the Define a Custom Search Profile page allows you to remove CDI ebooks from both the filtered and expanded searches in Primo VE. This is useful for removing duplicate ebook results while keeping book chapter results. However, because it also removes those results from the expanded results, it diminishes the value of the expanded search for discovery and for initiating ILL requests. A more useful function would allow us to apply the "Exclude cdi ebooks" option just to the filtered search and not to the expanded search.
48 votes -
Enhance DC XML normalization routines for external sources (PrimoVE)
In Primo Back Office, there is 86 inbuilt transformational routines for MARC21 and Dublin Core data normalization (e.g. “Take first words”, “Get highest number and normalize last digit”, and “Remove HTML tags”). Most have been translated for MARC21 in PrimoVE by various people but, because of limited regex and Xpath functionality, few have been translated into Dublin Core XML normalization routines for PimoVE.
We would like to see the implementation of full regex and/or XPath / XQuery functionality (or similar) to allow all Back Office normalization routines to be created for PrimoVE.
55 votes
- Don't see your idea?