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.
544 results found
-
Change how permalinks work
The permalinks provided by Primo do not link to a specific Alma record; instead, they save the result of a search in Primo. This means that when we copy a permalink for a title included in a course, what we are doing when using it is initiating a search for that title in the recommended bibliography collection. Therefore, if that title is no longer included in a course, the permalink we had copied stops working. This is not very useful.
We request that the permalinks provided by Primo be truly permanent and always direct to that Alma record, without changes.…21 votes -
Enable person entity functionality at the view level
The new feature (May 2024) for person entities is either on or off for all views.
For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.
Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from…
61 votes -
Support for Numeric Subfields (e.g., $0, $1) in MARC to PNX Mapping in Primo VE
Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.
Please map at least subfields $0 and $1 to PNX
This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .Use Case Example:
A record with multiple subject headings (650 fields) includes…13 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…
32 votes -
Resource Recommender Statistics for Individual Items
Primo Analytics for Resource Recommender analytics currently shows only number of selections by resource category but not for individual records within each category. We would like to use detailed statistics for annual usage review and and RR maintenance. Particularly for databases, we would like a more straightforward option to see clicks through RR.
From two previous ideas that were both closed: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/30982855-better-analytics-for-resource-recommender-to-tell#{toggle_previous_statuses}
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45030058-resource-recommender
21 votes -
Pair display of 880 fields with their linked MARC field
When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).
In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare…
50 votes -
Display import profile name also for for failed import jobs
Currently, the scheduled job "Import Data to Primo VE" gives us the name of the import profile/external data source that was harvested, but only if the job ran successfully. If not, only the name of the job will be given, but not which profile it ran on. This is true both in Alma and for the corresponding e-mail notifications. We would be glad if this could be changed so that the profile name is always displayed, as the current behaviour is making troubleshooting issues with the import profiles quite cumbersome, especially if several are affected at once.
40 votes -
Improve Citation Action
We would like to summarize in this idea exchange several issues we have run into with the citation action that inhibit the usefulness of the functionality for our customers greatly. Most of these relate to a lack of language sensitivity on the incoming side of the citation action. We would think it would be good if Ex Libris could work towards an improvement here, maybe together with the Citation Styles Language Project.
The formatting for the page count should be p.DDD-DDD or p. DDD-DDD in 773 $$g according to Ex Libris. The issue with this is that when our cataloguing…
54 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…
40 votes -
Index Item Description in Primo VE
We record the monographic titles of periodical issues only in the Item Description field and not in the periodical bibliographic record.
This item field is searchable in Alma but not in Primo VE.
We need that the Item Description field to also be searchable in Primo VE.41 votes -
Primo VE - Allow normalization of Esploro records
As a discovery tool Primo VE is supposed to deliver a unique gateway to many Library Resoures, including the a Institutional Repository (i.e. Esploro ).
To do so in a blended search one must be able to normalize records from different sources. We used to do that in Primo Classic, with a Pipe and a Normalization Rule. This is however not possible in the newer Primo VE.
Please allow manipulation and normalization of Esploro assets so that we can show them in the catalogue in a consistent way.40 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…
32 votes -
Ahead of print articles
I would love to see some regulations or procedure set in place for articles not yet published from being published in primo. I understand this is a vastly complex issue but curious if anyone else has had these issues as well and ideas on the topic.
Per Ex Libris
Ex Libris's goal is to reflect the provider’s content and metadata and cannot directly make changes in our databases without the provider making these changes. If the provider has sent us a record for an article that is not yet published, or not yet assigned to a specific volume/issue, you will…14 votes -
Disable default search for related titles without direct links
It would be helpful to be able to deactivate the often-problematic default search Primo conducts whenever you click on a related title without a direct link to a corresponding record, since this search frequently returns irrelevant records.
1 vote -
Add more than 7 lines – Advanced searches only include a maximum of seven search criteria lines
Could we have the capability to include more than seven lines in the advanced search function? In Summon, Web of Science and numerous other platforms, there is an unlimited possibility to select more lines.
Given that our users frequently search using both Danish and English keywords, the seven-line limit is often reached when both languages are used in an 'OR' search.6 votes -
Customise Purchase Suggestion Form material type list
The Purchase Suggestion Form in Primo VE currently offers a drop-down menu of all possible material types, including things like Ephemera, Toys, and Vinyl LP, which we don't want to turn off as a material type option but we also don't want to offer as a purchasing possibility. At the moment there's no way to switch off material types from that dropdown without removing them as an option for new items completely. We would like an option to customise this purchase suggestion form material type list with more flexibility.
50 votes -
Dublin Core field to display external links (like an 856)
We would like to have a way to link users to external resources from a Dublin Core record, similarly to how an 856 is used in MARC. Example: a digital object in Alma could link to a related finding aid in ArchivesSpace.
Perhaps the field(s) most appropriate to display in this manner would be dc:relation, dcterms:isPartOf, dcterms:replaces, dcterms:requires, dcterms:conformsTo and dcterms:isVersionOf.. but only if those fields utilize (dcterms:URI). If any of those fields are not tagged as a URI, that field should display as it does now.We are agnostic to whether such hyperlinks should be displayed in the "links"…
9 votes -
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…102 votes -
Influence the algorithm in the display format for hits on large broad subject searches where local repository records appear.
In our library we have decided that Primo should also display records from a local repository. This is a database of references to research publications produced by our researchers at our university. It is not always the case that we have electronic access to the titles in this local database. And it's not always the case that we own the physical works.
So we would like to have the titles in our catalogue, but we are well aware that at best they are reference titles that have to be obtained/borrowed.
We are planning to display more local repositories through our…9 votes -
Add library location name and/or code to advanced search options
I'd like to submit for reconsideration an idea that was posted back in 2020 but which unfortunately didn't receive enough votes to be considered for future development at that time. My own library has only been using Primo VE since May 2024, so we didn't get a chance to vote for the original post.
The previous post is at:
The earlier post was limited to adding the library location name as an advanced search drop-down filter. I'm expanding it somewhat here as a request to add library location name and/or location code as filter options. This is something we…
2 votes
- Don't see your idea?