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 ~
651 results found
-
More DEDUP keys
The implementation of the FRBR keys is affected by the DEDUP keys, so it would be desirable to add a new key in the DEDUP keys that includes the label 250.
108 votes -
Map location
When "Location" is selected for an item, open an image of the map within the record instead of a separate window.
1 vote -
Primo VE: Facet «Publication format» displays entries with capital letters and suppresses apostrophes
We noticed that the facet "Publication format" displays the entries with capital letters at the beginning of each word, and sometimes suppress the apostrophe too (see enclosures). This is a problem, because we never do display words in this manner in French or German. It really looks weird and we would like to avoid that for our users.
Thanks !
22 votes -
Privacy in patron letters
Currently, patrons receive detailed item information in patron letters. We would like to make it possible for patrons to turn off letters (such as when they do not want this detailed information living in their email accounts).
In testing, we found that the current 'Personal Details' configuration in Alma (https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/060Library_Card_Configuration/Configuring_Personal_Details_Settings_for_Primo_VE) does not allow us to limit patron changes to ONLY the notification preferences.
25 votes -
Exclude suppressed records from browse results
Currently, records that are suppressed from discovery still appear in users' browse search results. As explained in the documentation below:
"If a heading contains suppressed or restricted records:
- These records will be included in the heading's record count.
- When a user selects the heading, these records will be omitted from the results, and the system will display the following message: Some records are not displayed since they are restricted / suppressed from display"We expect that records suppressed from discovery should be suppressed everywhere, including browse. We strongly suggest Ex Libris implement a fix to consider the suppression status of record when delivering browse results.
Currently, records that are suppressed from discovery still appear in users' browse search results. As explained in the documentation below:
"If a heading contains suppressed or restricted records:
- These records will be included in the heading's record count.
- When a user selects the heading, these records will be omitted from the results, and the system will display the following message: Some records are not displayed since they are restricted / suppressed from display"We expect that records suppressed from discovery should be suppressed everywhere, including browse. We strongly suggest Ex Libris implement a fix to consider the…
8 votes -
Display only one of each resource recommender type
Currenlty the default is two of the first listed Type listed in Resource Recommender displays in PrimoVE. Would like to change it so that just one of each type of Resource Recommender displays to diversify results patron sees on page.
6 votes -
Add the option to sort results in Collection by newest acquisitions
We would like to be able to sort results in a Collection in Primo VE by newest acquisitions at the top. So perhaps sorting by date created of the record in Alma.
This way we could make collections that display the newest purchases in our library at the top.
11 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 creators or contributors.
For example: https://catalogue.leidenuniv.nl/discovery/search?query=any,contains,Rgveda&tab=Everything&search_scope=MyInst_and_CI&sortby=rank&vid=31UKB_LEU:UBL_V1&lang=en&offset=0 (the group of 32 records)
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 -
Include Citation type as a configurable field in Purchase request form
When a purchase request is made from Primo selected in Citation type: Book, the order line that is created is of type Physical-One time, and cannot be modified.
It would be nice to modify this default configuration.
1 vote -
Add option to control the visibility of collections in Primo and Collections Lobby
Give customers the option to control the visibility of individual collections in Primo and on the Collections Lobby page.
Use case: Our institution would like to have a limited number of centrally curated and managed collections that can be viewed in the Collections Lobby. But we would also like to give librarians the option to create their own collections for special projects, exhibits, or courses, which would not be displayed in the Lobby but could still be made accessible via direct link. Ideally, this could be achieved by adding checkboxes to the Collection Editor page - one controlling the collection's visibility in Primo and another controlling its visibility in the Collections Lobby.
Give customers the option to control the visibility of individual collections in Primo and on the Collections Lobby page.
Use case: Our institution would like to have a limited number of centrally curated and managed collections that can be viewed in the Collections Lobby. But we would also like to give librarians the option to create their own collections for special projects, exhibits, or courses, which would not be displayed in the Lobby but could still be made accessible via direct link. Ideally, this could be achieved by adding checkboxes to the Collection Editor page - one controlling the collection's…
2 votes -
"Search inside" option in PrimoVE for Journal titles - prevent this option for print only titles
Currently in PrimoVE, when a journal title search is undertaken for a title that is held in print format only, the "search inside" option is present. This is extremely misleading for users. If they undertake a search using this function, where the title is held in print format only, the user is shown articles from other titles.
Our idea therefore seeks that the leader, 007, 008 marc fields are used to identify when the title is a print only title and therefore prevent the "search inside" option from appearing against such titles in PrimoVE.21 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 of our more advanced users are expressing frustration with these settings. They would be much happier if they could use other settings by default. It would be a great help to them if "Expand My Results" and "Search in Full Text" could be added to Primo VE's personalization options for signed in users, like Results Per Page. The ability to set a preference in Personal Details and Settings, "lock" the toggles like the filters/facets, and/or have the system remember and retain the user's last selection could all be big improvements to the user experience and satisfaction.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…2 votes -
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 -
Display item enumeration on location level under Get It for Primo VE
We would like to be able to configure the information displayed under Get it in the location/holding level for Primo VE to contain information from the enumeration fields from the item level.
This used to be possible in Primo BO (see attached screenshot), but unfortunately not anymore in Primo VE.
When there are many holdings and items the user, as a consequence, will have to perform many clicks through all the holdings and checking all the items to find the volume that they are looking for.
It would then be more useful if they could see on the location level already which holdings contain which volumes.We would like to be able to configure the information displayed under Get it in the location/holding level for Primo VE to contain information from the enumeration fields from the item level.
This used to be possible in Primo BO (see attached screenshot), but unfortunately not anymore in Primo VE.
When there are many holdings and items the user, as a consequence, will have to perform many clicks through all the holdings and checking all the items to find the volume that they are looking for.
It would then be more useful if they could see on the location level…3 votes -
add a link to the location section
We would like to be able to create an embedded link to the location section in PRIMO VE (please see image attached)
This embedded link would then be added to a libguide to provide real time information on the location of the item
1 vote -
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.
16 votes -
Language field in Brief Record Display ought to use the Language codes Labels (VE)
For institutions with multi-lingual collections, the out-of-the-box Language field can be a useful addition to the record display. When Language is added to the Full Record display, the "Language codes Labels" code table is used to convert the abbreviated codes used in metadata records into generally understood language names–e.g. the code 'gle' displays as 'Irish'.
When the Language field is added to the Brief Record display, however, the labels are NOT used and the code is displayed as-is. Ex Libris recognizes this as a defect (case #06659538) but a solution is not part of the current development work plan. We are dismayed, as we hoped to add this field to our brief record display to remedy student difficulties demonstrated during usability interviews. The Language field is included in our Full Record display, but it is less visible there than it would be in the Brief Record.
Scenarios where having the language label in the Brief display would be helpful for users:
Students can have trouble distinguishing which titles are foreign language material because the metadata is primarily or solely in English. This sort of confusion can lead to item requests for material that a student cannot read and thus cannot use, which wastes the time of the student during their research, wastes the time of library staff who processed the request, and sometimes costs the library money for postage/fees incurred to process the request. For online resources, this confusion leads to inflated usage statistics that can be misleading for calculating cost per use and making renewal decisions. Image: eng metadata jpn contents
Titles can be in a different language than the contents of the text while the record metadata is in a third language. Numerous older titles, for example, are in Latin, which can be misleading about the linguistic nature of their contents. This confusion has similar impacts as described in the first scenario. Image: eng metadata latin title irish text
The Language facet is not sufficient to distinguish the primary language of the material from the presence of supplemental text in that language, like subtitles on a film. Patrons who are seeking resources in specific languages can be frustrated by this. For example, the film Parasite remains in search results after the English language filter is applied, even though the dialogue is in Korean and French while English is only present as subtitles. In those same filtered results, you can see the film Transfer, which is in German and French. Image: eng filter koreanFrench dialogue
Since the code is displayed in the Brief Record, we cannot add it for our users–it would cause more confusion than it would resolve. The out-of-the-box Language field needs to be fixed so the "Language codes Labels" code table is invoked for the Brief Record, as it is for the Full Record.
For institutions with multi-lingual collections, the out-of-the-box Language field can be a useful addition to the record display. When Language is added to the Full Record display, the "Language codes Labels" code table is used to convert the abbreviated codes used in metadata records into generally understood language names–e.g. the code 'gle' displays as 'Irish'.
When the Language field is added to the Brief Record display, however, the labels are NOT used and the code is displayed as-is. Ex Libris recognizes this as a defect (case #06659538) but a solution is not part of the current development work plan. We…
14 votes -
Have the sort order for libraries affect the pickup location order in Primo
There is currently a library sort order in Discovery for Primo VE. Our wish was to have the main campus appear first and then the branches. However we discovered that while we have options to try sorting by IP or by a custom order, this configuration does not apply to the request screen - pickup location order. We confirmed this with a ticket, and develop noted that only the alphabetical order applies to this area. We believe, it would be helpful to allow libraries with multiple libraries to put the main library at the top as that is the one that most users will select anyway.
There is currently a library sort order in Discovery for Primo VE. Our wish was to have the main campus appear first and then the branches. However we discovered that while we have options to try sorting by IP or by a custom order, this configuration does not apply to the request screen - pickup location order. We confirmed this with a ticket, and develop noted that only the alphabetical order applies to this area. We believe, it would be helpful to allow libraries with multiple libraries to put the main library at the top as that is the one…
16 votes -
Display Licenses for Results from CDI if holdings are associated with a license
For Primo VE search results, display the license for results obtained from the CDI. Primo already displays the license terms of results obtained from Alma holdings. License terms are displayed next to a Primo VE result that is from an institution’s Alma holding if the Alma holding has a license assigned to it (shown in the Electronic Collection Editor’s General tab in Alma), but the license is not currently displayed when Primo VE search results are obtained from the CDI for the same holding (that does have a license assigned to it.). This would benefit ILL staff who rely on license terms displayed in Primo to know if they can lend items.
For Primo VE search results, display the license for results obtained from the CDI. Primo already displays the license terms of results obtained from Alma holdings. License terms are displayed next to a Primo VE result that is from an institution’s Alma holding if the Alma holding has a license assigned to it (shown in the Electronic Collection Editor’s General tab in Alma), but the license is not currently displayed when Primo VE search results are obtained from the CDI for the same holding (that does have a license assigned to it.). This would benefit ILL staff who rely on…
19 votes -
Ability to reduce limit for number of links in "View It"
Ability to reduce the limit for full text links in "View It"
At present, the limit for links in "View It" is set to 25, see: https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/View_It_is_limited_for_25_resources
However, it is not possible to reduce the number and lower the limit (as it was possible in the SFX environment).We would like the ability reduce the limit for links in the "View It" section of a Primo record.
23 votes
- Don't see your idea?