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.
272 results found
-
Allow institutions to exclude the 776 from the CDI holdings file
Proposal: allow institutions to exclude the 776 from the CDI holdings file
Problem: sometimes local services for book title X in a series get matched to CDI records for book title Y (a different title in the series). Users click on the service and are taken to the wrong book, which is frustrating. According to Ex Libris, Alma uses the 776 field to generate the holdings file that is sent to CDI to calculate availability, and this is what causes the incorrect matching.
The solution of removing identifiers from the 776 as outlined in this Knowledge Article is not feasible,…
2 votes -
Book Covers en ALMA- Very good service for the user.
The Spanish Conference of Bookstore Guilds and Associations (CEGAL) has created a functionality on its All Your Books platform with which to automatically include book covers.
Information that other Integrated Library Management Systems are executing this functionality.
https://www.baratz.es/todos-tus-libros-nueva-opcion-para-las-portadas-automaticas-en-absysnet/1 vote -
Export to Leganto from OneSearch - course information
Export to Leganto from OneSearch under 'full Record Services' - to include course information in addition to the already existing reading list information. Or, e.g. allow the lists to be searchable by typing e.g. the title/name
− Role: Course instructors
− Proposed feature: Be able to additionally see the course information as well as the existing reading list pneumonic/title when making a selection from the list, or be searchable by typing in the name of the list
− Feature’s benefit: Make it much easier and quicker to find the right resource list to add the title to. It is currently…
3 votes -
Linked Open Data - Discovery of Person Entity with HKCAN name authorities
With the Primo VE May 2024 release, an option to enrich our library catalogue with linked open data of person entities is available. We understand that currently this enrichment is only available to personal headings linked to LC name vocabulary. However, in all of JULAC libraries, Chinese, Japanese, and Korean personal headings are mostly linked up with HKCAN name authority vocabulary. So, a vast amount of our records are not enriched with the linked open data. We'd like to propose extending this linked open data enrichment to person entities with HKCAN name authorities. Thank you for considering!
Salesforce ref. 07228906
1 vote -
Research Assistant suggested subjects
In Research Assistant, it may be beneficial to offer users a list of relevant Primo subjects. Users may go to Primo VE & look excatly for the subjects suggested by the Research Assistant.
1 vote -
RIS
We have found that many tags are missing from RIS record export files. And we have no way of adding a tag to the “Export Mapping for the RIS, EasyBib, and EndNote Actions” code table.
In particular, the language is missing: tag “LA”.
We'd like to be able to add at least a few tags on our own.1 vote -
Provide option to disable course information being indexed for search in Primo VE
We have chosen not to display course information in our Primo VE but found that local records appear higher in our search results when they are attached to a Leganto reading list. Support tell me that 'it is part of OTB and by default it will be indexed’.
In the ‘Search Section Mapping’ part of the 'Mapping to the Display, Facets, and Search Sections in the Primo VE Record' Knowledge Center page, it says: 'Course information – Primo VE indexs the course name, code, and instructor for records associated with course reading lists.'
We don't understand why course and instructor…
22 votes -
Add Linked Data functionality for DOIs in records to find and present related content
Where a record contains a DOI, it would be great if Primo could look up the DOI (vis CrossRef?) and find the DOIs and metadata for any related content, and present them in an Info Card on the full record display, in the same format as is used for the Person Info Card. This would allow linking between an article (published or present in an Institutional Repository) and its dataset or software, or any retraction or corrigendum related to the article. It would help us to present research outputs within their context and improve research reproducibility.
3 votes -
Allow Online Services Order to sort by current access
We need the ability to move to top of View It a service with current access (this means the coverage statement is open-ended, ie Available from 1998 - current).
Users get overwhelmed with the long list of services often displayed, and ordering the list according to interface or electronic collection name doesn't address the most important aspect, whether there is current access or not. As an example, on Proquest interface Z, journal title X may provide current access, but journal title Y on the same Proquest interface Z may only have archive access. We only want to put journal title…
212 votes -
Expand Primo VE Browse Search to include dc:subject tags from Discovery Import Profile targets
The Primo VE Browse Search currently includes only those bibliographic items that are managed within Alma.
Since Discovery Import Profiles bring external data sources into the Primo VE search index, it would be an improvement to incorporate harvested dc:subject (or similar) fields into the Browse Search.
Often libraries have collections - especially digital ones - managed outside of Alma, but metadata is brought into Primo VE in order to provide a true all-of-library-collections search. Adding the ability to run a Browse Search across this imported metadata would be a useful feature.
1 vote -
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.
7 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…
7 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.…
57 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…
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
- Don't see your idea?