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.
1133 results found
-
Add the creation date to the titles in the Saved Search Letter
Users can set an alert on the Saved Searches page and will then receive the Saved Search letter by email whenever there are new results for their saved search. However, a new result is not necessarily a new publication. The Saved Search letter could also contain older publications which are new to the inventory of the discovery system. For the users, it would be helpful to already see in the Saved Search letter the creation date of the titles, so that they know which results are real new publications. In Primo VE, however, it is currently not possible to add…
7 votes -
Fiscal/Calendar Year fields for Primo Analytics
Please provide the fiscal year and calendar year fields for Primo Analytics. To show trends, it is helpful to compare by fiscal/calendar years.
12 votes -
Allow manual control of thumbnails in Primo records
Primo uses Syndetics to supply thumbnails of book covers for records within Primo. However, when Syndetics provides an incorrect image based on their data, it requires a ticket and often several weeks to correct it. In contrast, some records have no thumbnail at all and use a default gray book icon. Libraries should have the option to use this default icon when Syndetics is providing an incorrect image, or to upload and use local images in cases of records that have no images in Syndetics (for example, with archival and special collection books that are old enough that they have…
4 votes -
Show only Uniform title when FRBR key contains field 130 information
When records are grouped together in Primo VE because they have the same uniform title in MARC field 130, the display of the title and creators in the Brief results display for this group is not ideal.
The group shows the title and creators of one of the records in the group, which can be confusing to the user.
What would be more ideal in these cases is that when the Uniform Title is used to generate the FRBR key, to only display the Uniform title from field 130 in the Brief results display for the grouped records, and no…
4 votes -
Make is possible to display Available From Date and Available To Date to users in Primo
The "Control the Availability of Portfolios Automatically at a Pre-defined Date" feature, introduced in the February 2023 release (https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2023/Alma_2023_Release_Notes?mon=202302BASE), allows libraries to enter an Available From Date and Available To Date in portfolios, and the portfolio will be automatically deactivated after the Available To Date. This feature is designed to be useful in cases where libraries lease a piece of content (typically, a streaming film) for a limited period of time.
In this Idea, we suggest that we should be able to display the Available From Date and Available To Date to end users in Primo. This is…
26 votes -
Sort Book Chapters in correct order when using PrimoVE in 'Everything' search
When using the ‘Everything’ search in PrimoVE you can't consistently sort book chapters into the correct order. Even when using the facets to filter and sort results, it still returns chapters in a variety of orders.
For example, searching for the following book and filtering by ‘Book Chapters’, refining the year to ‘2015’ and sorting by ‘Title’ still returned the chapters in the wrong order (see attached screenshot).
“Meeting Health Information Needs Outside of Healthcare” Kreps, Gary L.; Neuhauser, Linda (2015)
It may not be possible, due to the variety of way book chapters can be structured. However, if it…
1 vote -
My Library Card: Digital LOANS
It would really be helpful to have a tab or include borrowed digital books under patron loans so that its easy for them to renew or see what digital books they borrowed and need to return. Currently there is no ability for a patron to see what digital books they may have borrowed and need to return.
3 votes -
Primo VE webhook search blending
In terms of usability, it would be good if Primo VE webhook search results could be blended to the combined search results (local resources and articles). Blended results feature should be able to select on a search-by-search basis e.g. if you apply search for AI-based article search portals or whether to apply search for printed resources from the repository libraries.
32 votes -
Enable user personalization for their default "Expand my results" and "Search in full text" options
Currently, institutions set a default for "Expand my results" and "Search in full text." Users can toggle these settings, but unlike other filters, these toggles are not "sticky" and it does not seem possible to "lock" them. When the session is reset or the user selects "New Search", the institutional default is re-applied. The user who prefers other settings must therefore constantly re-toggle their desired options.
We find vastly different needs between our faculty, graduate students, professional practitioners, and undergraduates in their search behaviors and preferences. Currently, we have default settings designed for the least sophisticated searchers (undergraduates), but many…1 vote -
Option to bulk export normalization rules Primo VE
We would like to make a bulk export for backup of the normalization rules that we have set up in Primo VE.
At the moment this functionality does not exist but would be very helpful for us. At the moment if we make changes to the normalization rules it is easy to accidentally delete the entire set of rules for one field. It is also not possible to easily roll back a change that we made.
Therefore it would be useful to have the export option, to have an extra copy of all the normalization rules as a backup.
2 votes -
Consistent UX or labelling for Collection Discovery search box
Ideal solution: The Collection Discovery search box should be persistent and always search at the item level within all collections (as it does in the lobby) in order to provide a logical, consistent user experience.
Secondary solution: the label text should be editable for each search box separately to make it clear what is being searched on the page.
Problem:
- The lobby search box is for everything
- The top-level collection search box is for the title of sub-collections in that area only
- The sub-collection search box is for items in that sub-collection only.
Yet, all three options say "search" and…
4 votes -
Allow suppression of GES based on Primo View
Currently a GES (General Electronic Service) link can be suppressed or shown based on certain characteristics of the record or though Alma Display Logic Rule, through characteristics of the logged in user or presence / absence of other GES links. We would like the ability to control the display of GES links based on the current Primo view. This would allow us to show or suppress links in certain Primo views before asking the user to login.
6 votes -
Display the item "process type" label in Get It
In get-It, we would like to display some of the "Process type" labels from our local item processes.
For example, we think that the information "In the process of scanning" would be interresting for the users, instead of the general label "In process".
This would highlight projects in progress that are eagerly awaited by users.3 votes -
Quotation marks: align the behavior of Alma and CDI records
When using quotation marks in a search, Alma and CDI records behave differently:
CDI records:
« » → not considered for the search
„ “ → considered for the search only for some languages
“ ” → considered for the search only for some languages
" " → considered for the searchFor local records:
« » → not considered for the search
„ “ → not considered for the search
“ ” → not considered for the search
" " → considered for the searchWith this idea exchange we propose to align the behavior of Alma and CDI…
8 votes -
Streamline favourites by adding the ability to create labels from the item.
It would be great if once you clicked the add to favourites button for an item you were either presented with a "Would you like to add a label" option, or the ability to add labels/tags from the ellipses menu, rather than having to go to the favourites menu.
23 votes -
Separate the Primo My Account Update Login Credentials form into two different forms for PIN code and Password
As a user, I would like to have two different forms for Pincode update and Password update (Update Login Credentials in My Account > Personal Settings) so I am sure that I can also change only one of the two. With the current design (=one form for PIN and password update), it is suggested to me that I always have to update both.
10 votes -
Support "Exact year" date search in Advanced Search
If a user knows the exact year they want to limit to, they have to type it in twice, whether they are using the facet option or the Advanced Search dropdown for Date Range. It would be helpful if the Advanced Search had a "Exact year" option with a single field to fill in.
4 votes -
Do not display private fields in “display source record” or full record in Primo VE.
Marc 21 coding is used to identify some marc record fields/subfields as private. As an example, the indicators in the 541 tag are used to indicate that data in the field is ‘private’ to the organisation. Primo VE should automatically hide these fields from the source record and full details display in Primo VE. If an organisation wishes for the field to be made public they can adjust the record coding as appropriate. Alternatively organisations should be able to select to suppress private fields (as identified in marc 21) from public display.
68 votes -
Banner - start and end date
We're using the banner to promote different library related events/workshops etc that run throughout the year. Currently we would have to manually enable and disable banners.
If there was something that allows us to determine how long the banner would display then it would make it easier, and not having to make sure a member of staff is available on certain days of the year just to switch on/off a banner.
1 vote -
Title in "digital collection" section
In Primo VE, within the "Digital Collections" section, digital records currently display the entire content of field 245 as the title. This results in excessively lengthy titles for certain entries. Ideally, we would prefer that only subfield 245$$a be shown as the title within the "Digital Collections" section.
6 votes
- Don't see your idea?