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.
- or
No existing idea results
- ~ No ideas found ~
508 results found
-
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 in terms of when data changes will be reflected.
2. It takes several weeks before updated data is reflected in Primo VE.
3. Reliability of Wikidata where everyone can update it.
4. Relying on complaints is not the right approach and can/will lead to reputational damage to the institution.
5. Manual workarounds can lead to technical debt.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 data displayed for an individual. The new data was not reflected in Primo VE for several weeks. Ex Libris advised this may be due to further processing times from the Wikidata servers prior to their call data being updated.
Justification:
1. Updating Wikidata entries directly is not a sustainable solution and is also dependent on the timeliness of weekly updates.
2. It takes several weeks before updated data is reflected in Primo VE.
3. Reliability of Wikidata where everyone can update it.
4. Relying on complaints is not the right approach and can/will lead to reputational damage to the institution.
5. Manual workarounds can lead to technical debt.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…
9 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).
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 -
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 Zones (in our context, we have two IZs for different types of libraries, with different configuration requirements).
Indeed, this could be of interest not only to a library consortium but to any standalone library that manages several views.
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 -
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 the Primo form already has authentication.Please enhance the purchase request form:
-publication year - date picker/validation to capture only 4 digits
- longer input areas so users can see what they have entered (reduce errors)
- wider, less cramped layout
- form header & footer text/html for user help and context setting
- easier configuration methodThe Rialto form offers a logo upload though that might not be critical if the PR form uses the Primo header in any case, but some institutions might want that too.
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 -
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 clear navigation for all users, regardless of mobility.
Additional Details:
• Provide an option to upload location maps into Alma, associating them with call number ranges for stacks or shelves.
• Display the relevant map within Primo VE search results for physical items based on call number, with clear directions to the shelf.Conclusion: This integrated library mapping solution will change the way patrons interact with physical collections, bridging digital search and physical retrieval, while gaining deeper insights into libraries' collection usage.
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 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 link in record link. However, some libraries would like to prioritize unrestricted links over restricted links (for example, in order to support Open Access and provide the alumni and the public with unrestricted access to resources). This idea proposes that libraries should be able to customize whether or not to prioritize OA link in record links in the merged record.
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 -
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 displayed via a link in a separate window. There the volumes can be sorted by publication date, relevance etc.Example: Opere di Francesco de Sanctis, https://permalink.obvsg.at/AC01614297
Austria is working with PLK fields for their solution. During the publishing process from Alma to Primo, the related records are added as PLK fields to the source record. For an example, please see here the source record for Opere.
In Primo VE we would like to be able to add the relationships to the source data set, as it is the case in Primo BO with the PLK fields.
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 -
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 the user to post-filter as desired. Initially, I thought we might be able to create a local resource type to combine Articles & Magazine Articles, but of course that can't be done in Alma, since these are CDI types. I would like to advocate for a combined Article type option (including both Journal and Magazine articles) within the CDI especially for use in Resource Type filtering, AND/OR the ability to customize the Resource Types in the Filter Bar by combing two or more types or other local configurations, including CDI-only resource types.
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 -
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 -
Unpaywall - displaying both GETPDF and Interloan links for some resources
This suggestion has been logged at the suggestion of Ex Libris in response to our Salesforce Ticket #07049766 .
Unpaywall content sometimes displays both GETPDF and "Interloan" links. This confuses users, who regard the Interloan link as the safer option, and place an interloan request when they can directly access the PDF full text via the GETPDF link.
There are overhead costs to managing this problem and redirecting the users to the correct link.
Example record in Primo VE with both GETPDF and "Interloan" links:
https://tewaharoa.victoria.ac.nz/permalink/64VUW_INST/1m9iv9v/cdi_openaire_primary_doi_211a156b24c44785a740e56954ab1501Ex Libris has reviewed this case and requested that it be placed in the Idea Exchange to gather additional input from the wider community and to decide on the scheduling of a fix.
Your endorsement and support will be warmly welcomed.
Thank youNgā mihi
Brenda Norton
Brenda Norton RLIANZA | Library Systems and Discovery Librarian |
Systems and Integration Development | Te Pātaka Kōrero |Phone +64 4 463 6185 | E-mail Brenda.Norton@vuw.ac.nzThis suggestion has been logged at the suggestion of Ex Libris in response to our Salesforce Ticket #07049766 .
Unpaywall content sometimes displays both GETPDF and "Interloan" links. This confuses users, who regard the Interloan link as the safer option, and place an interloan request when they can directly access the PDF full text via the GETPDF link.
There are overhead costs to managing this problem and redirecting the users to the correct link.
Example record in Primo VE with both GETPDF and "Interloan" links:
https://tewaharoa.victoria.ac.nz/permalink/64VUW_INST/1m9iv9v/cdi_openaire_primary_doi_211a156b24c44785a740e56954ab1501Ex Libris has reviewed this case and requested that it be placed in the…
7 votes -
Resource Recommender Banner: allow multiple, randomised Banners
We find the Resource Recommender Banner in Primo VE incredible useful for promoting exhibitions, programs and other library events, but the click through rate on the Banner is extremely low.
One of the reasons for this, I suspect, is the static nature of the banner - once activated, the same image appears every time a search is conducted and it quickly just becomes "noise" on the catalogue that is either ignored or dismissed.
We'd like to see this feature further developed to allow for multiple banners to be active at once (say, up to 5) and then have a different, randomly selected banner displayed each session. This would allow libraries to use the banners to promote more than one thing at a time (e.g. an exhibition, new Collection Discovery additions, research guides, etc) and increase the "noticability" of the banners by having something different displayed over subsequent catalogue visits.
As an additional enhancement, it could also be useful to "boost" one of the active banners so it appears more often than the others so something can have higher prominence.
We find the Resource Recommender Banner in Primo VE incredible useful for promoting exhibitions, programs and other library events, but the click through rate on the Banner is extremely low.
One of the reasons for this, I suspect, is the static nature of the banner - once activated, the same image appears every time a search is conducted and it quickly just becomes "noise" on the catalogue that is either ignored or dismissed.
We'd like to see this feature further developed to allow for multiple banners to be active at once (say, up to 5) and then have a different,…
8 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 to be searched together.
It is possible to create a custom local data scope to add Esploro records to a blended search and enable Esploro records to be searched alongside Alma and CDI records but this searches across all Esploro records rather than only the ones that have inventory.
We’d like the option to exclude Esploro assets without inventory from a blended search so users can only find records that lead to full text when conducting a Primo search
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
- Don't see your idea?