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.
651 results found
-
Feedback tool : option to integrate with ticketing system via webhook
We'd like to integrate the feedback button with our ticketing system via webhook instead of via sending mails.
We expect this will give better opportunities for integration eg. mapping the e-mail address of the customer to the customer e-mail address field in the ticketing system.
See also
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45350419-feedback-tool-for-primo-ve-allow-user-s-email-as19 votes -
Can the feedbacktool for Primo VE provide more information about the end user
Referring to the Idea : https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45653308-the-new-give-us-feedback-tool-should-provide-infor that has been closed, our question is: can the information be provided whether the user is signed in.
If there is a single sign on of the proxy with Primo, this information is also useful when handling issues with access to e-resources.
19 votes -
Suppress Resource Sharing Request Form when consortium-owned items are unavailable
Please provide a pathway, via Display Logic Rules or otherwise, that would allow us to suppress the Resource Sharing Request Form in instances where an item owned by another institution in our consortium is UNAVAILABLE. Right now, all we can do in this case is modify a text message at the top of the form and hope that the user understands that s/he will need to use the interlibrary loan request form instead.
3 votes -
Feedbacktool to provide extra info from the Primo record in the Subject of the message
Additional context information of the record such as the source (Alma, CDI, external source) allows problem reports to be dispatched more efficiently to the relevant person / service that can solve the problem.
Our use case is the following: external sources (like institutional repository, archives,..) that are imported into the library catalogue are not managed in Alma. Questions about these records need to be forwarded to the managers of these sources, often to other departments outside of the library. The user is usually not able to make this distinction between records of different sources, so the use of categories is…
18 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.…
46 votes -
replace "Do not show as Full Text available in CDI even if active in Alma" with a pair of show local / show CDI checkboxes
To avoid duplicates when we have both local portfolios and CDI records, we can rely on the "Do not show as Full Text available in CDI even if active in Alma".
Enabling this feature will show in Primo local IZ portfolios, and is very good when local records are rich and CZ records are limited/poor.
Sometimes however CDI records are richer and provide indexing at chapter level. In such a case we would like to hide IZ local portfolios and show CDI records instead.
It would be therefore useful and clearer to replace the "Do not show as Full Text…97 votes -
Prepositions, conjunctions and articles must be written in lowercase in the "Journal Title" facet.
In Primo in the facets section there is one called "Magazine Title" where prepositions, conjunctions and articles such as "Of", "And", "The" appear with letters in capital letters which is incorrect,
since they must be shown in lowercase .
I attach a sample image.
Thank you.
En Primo en la sección de facetas hay una llamada "Título de la revista" donde aparecen las preposiciones, conjunciones y artículos como "De", "Y", "La" con letras en mayúsculas, lo cual es incorrecto, pues deben mostrarse en minusculas.
Anexo una imagen de muestra.
Gracias.
1 vote -
Consolidated booking calendar view for patrons in Primo
Ability for patrons to view all bookable items in a single calendar.
Our library uses bookings for 9 student student rooms, so students may have to begin 9 separate booking requests before finding an available room. This is a tremendous frustration and waste of their time.
A consolidated booking calendar should allow students to preview availability of all rooms before attempting to place a request.
1 vote -
Consolidated booking calendar view for patrons in Primo
Ability for patrons to view all bookable items in a single calendar.
Our library uses bookings for 9 student student rooms, so students may have to begin 9 separate booking requests before finding an available room. This is a tremendous frustration and waste of their time.
A consolidated booking calendar should allow students to preview availability of all rooms before attempting to place a request.
1 vote -
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…
10 votes -
Display portfolio public notes in brief record display
We add important public notes to portfolios, with access instructions for users. Currently these only display on the full record screen.
Users often miss these instructions. It would improve the user experience to also include these notes in the brief record display, where they have a greater chance of being noticed.6 votes -
Display print journal coverage dates in brief record display
We have activated the display of online journal coverage dates in the brief record display.
We would like to further enhance the user experience by also displaying the coverage of our print journals.
This will deliver a more consistent experience to our users.Ex Libris has recommended posting this suggestion on the Idea Exchange (#07262867).
9 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.
13 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…
79 votes -
Make brief availability statement continuous across calendar year changeover
The brief availability statement in Primo VE (see attached screenshot) cannot compensate for the changeover of the calendar year. If we have the following coverage dates:
Portfolio #1: 1/1/1869-12/31/1984
Portfolio #2: 1/1/1985-presentThen the brief availability should read "Coverage: 1869-present." Instead, it reads "Coverage: 1869-1984, From 1985."
Jan. 1 always comes after December 31, so the algorithm should be able to compensate for this. I know it's a small thing, but I'd love to see this fixed!
3 votes -
New export all function without be logged in
To use the new “Export ALL results” feature in Primo VE, we've noticed that you need to be logged in.
we would like to be able to use this feature without being logged in, like the other ways of exporting results.1 vote -
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…52 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…112 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…
37 votes
- Don't see your idea?