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
-
Allow Indexing and Display of 788 Field
Would like for the indexing and display of 788 field in Primo VE.
The 788 field allows catalogers to make discoverable parallel descriptions in another language https://www.loc.gov/marc/bibliographic/bd788.html and https://www.oclc.org/bibformats/en/7xx/788.html
1 vote -
Harvard Business Review Digital Articles
Indexing Harvard Business Review Digital Articles for Primo
3 votes -
Enable more fields for export to Mendeley, at least the permalink to the record
It would be very helpful for users if the permalink to the record could be exported to Mendeley.
2 votes -
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, because it goes against correct cataloging practice. Even if we were to remove the 776 in our local bib, it would get overwritten with the next bib update.
Why Do CDI Records for Book Series Titles Appear Incorrectly as "Full Text Available"? How Can I Correct This? - Ex Libris Knowledge Center https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Why_Do_CDI_Records_for_Book_Series_Titles_Appear_Incorrectly_as_%22Full_Text_Available%22%3F_How_Can_I_Correct_This%3FThe 776 should not be used to calculate availability, as it is not an indicator of whether a particular institution has access to the alternative format, only that the alternative format exists. Therefore, institutions should have the ability to exclude the 776 from the holdings file published to CDI.
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,…
75 votes -
"Remember all filters" should be selected by default
We want "Remember all filters" to be selected by default. It confuses our users who expect that their filters will remain while they change their search, only to find that they had to click "Remember all filters" first. We'd rather them have to de-select "Remember all filters" if there's a reason they don't want to retain them in their searching.
Relates to https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/34854556-make-facets-sticky-by-default-for-the-session, where the "default" part was never instituted.
13 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 difficult and time consuming.
Thank you!
Natalia Klaaser
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 -
Do not interpret words in phrase searches as Boolean operators
At ETH Library, we use UDK classification. The UDK notations are always in capital letters, and some contain words as “AND” or German “UND”. “AND” and “UND” are defined as Boolean operators in our Primo VE. This leads to the following problem: when a user clicks on an UDK notation that contains such a word (e.g. on “PFLANZEN + BÄUME + BLUMEN (MOTIVE IN KUNST, LITERATUR UND FILM)” in this record: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990015558430205503), a search for “subject equals exact phrase” in the advanced search is triggered. Although a phrase search is performed, the word UND is interpreted as a Boolean operator, and therefore the search returns 0 results.
We think that the search in Primo VE should be improved so that no word in a phrase search is interpreted as Boolean operator. Since it is not possible for a phrase to contain a Boolean operator, the current search behavior is a bug and should be fixed.At ETH Library, we use UDK classification. The UDK notations are always in capital letters, and some contain words as “AND” or German “UND”. “AND” and “UND” are defined as Boolean operators in our Primo VE. This leads to the following problem: when a user clicks on an UDK notation that contains such a word (e.g. on “PFLANZEN + BÄUME + BLUMEN (MOTIVE IN KUNST, LITERATUR UND FILM)” in this record: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990015558430205503), a search for “subject equals exact phrase” in the advanced search is triggered. Although a phrase search is performed, the word UND is interpreted as a Boolean…
6 votes -
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.4 votes -
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 names should be considered in a search over bibliographic data when we are not displaying any course data in the results. It affects user confidence in the search results and is another thing our subject librarians need to explain.
We strongly believe it should be optional, as I believe it was with Primo BO (where 'Course reserve information is not published to Primo unless Alma is configured to publish course enrichment information'), hence it is another Feature Alignment issue with Primo VE in comparison to Primo BO.
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…
32 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 X at the top, not journal title Y.
Solution: add a configuration to Online Services Order to move to top a service with current access (Until Year/Until Month/Until Day/Until Issue fields are empty).
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…
231 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 -
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 not a solution for this.
This context info (besides the url of the record in Primo) would allow a more efficient handling of the messages in a CRM or ticketing system. Based on this information, added to the Subject of the message, the question or problem report could be automatically assigned to the relevant person/department.Our suggestion is to allow via configuration to put the source field (or more generic, to support other use cases: a specific field) from the Primo record in the subject of the mail sent by the feedbacktool.
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.
Please create another option within Entire Network Inventory to display All Physical Inventory (regardless of availability). We would like to be able to see and use our own records.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.…
49 votes
- Don't see your idea?