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.
1129 results found
-
Add "Locate" link to Primo Analytics
We would like to find out how often users are clicking on the Locate item within the Primo VE record to view the map where the item is located; this is the label nui.locations.locate in the ViewIt table. Ex Libris support has confirmed that this link currently cannot be tracked in Primo Analytics because there is not a beacon call associated with the link. We would like to request that the Locate link be added to Primo Analytics tracking.
82 votes -
Add option to filter out Global title index results without any offer
When creating a scope that include CDI records non filtered per availability (Rapido-CDI expanded index), Global title index without any offer (no Get it section, no view online section and no item available in the Rapido tile) are retrieved (example). These records are owned by libraries participating in any POD (outside of ours) of Rapido.
We would like to have an option to exclude the Global title index results without an offer.
82 votes -
• Records without a date at the bottom of results list when sorting on date oldest
At this moment, the sort option “Date oldest” displays the records without a date on top of the results list. This is confusing and not relevant for users; when there are several records without a Creation Date they probably conclude that sorting on date oldest doesn’t work. Our request is to display the records without a date always at the bottom of the results list when a sort option on date is used (thus as well for date oldest as for date newest)
80 votesHi all,
This is to update that this is currently not planned to be developed. We might evaluate it again in the future.
Therefore we are removing the "Under review" status for now.
Best regards,
Yael.
-
Set default encoding level for Export RIS in New UI
In the New Primo User Interface the Export RIS functionality requires users to select an encoding level.
In the classic UI UTF-8 was selected by default.
Can the default encoding level please be an option in the New UI.
Many of our users are confused by which encoding level to select, and we would like to present them with a default option selected to help ease the confusion.80 votes -
Enable Public Notes display for content within Database-type collections
It would be very helpful if Public Notes could be displayed for individual content (articles, etc.) within Database-type collections. Currently, Public Notes for Database-type collections can only be placed on the record for the collection itself, and they are not displayed on individual content. So if a user searches for the name of the database (such as
ProQuest Congressional Hearings Digital Collection: Part A (1824-1979)) they can see the Public Note below the View Online link -- but if they search for an article held within that collection (such as Committee Business. Congressional Hearing, 1980-07-31), there is no public note…80 votes -
DEDUP/FRBR data in Primo VE analytics
DEDUP/FRBR data in Primo VE analytics isn't available. It is available in standard Primo.
This would be useful for identifying issues around records that aren't matching.
Apparently Primo PNX records and pipes subject area are not available for Primo VE customers as yet.
80 votes -
Enable authority Record Enrichment in Primo VE on local subject fields
In addition to the indexing of bibliographic metadata, Primo VE indexes preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records. However, this works only in the generic advanced search Subject field.
We need Primo VE to enable authority record enrichment on local fields as well.
Indeed, we have configured local subject fields that are more specific than the default Subject field. These enable searching only on specific subject vocabularies. But configuring such fields does not include the enrichment capability.
79 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…79 votes -
PCI to recognise the elements of a DOI to find the item
Errors in search results are likely to occur when users are searching for DOIs from citations. DOIs are often formatted differently in citations or online but the user will naturally just copy-paste the DOI as it appears. If the user searches for this 10.1016/j.acalib.2008.10.014 in Primo Central - you find the article. However if you search for http://dx.doi.org/10.1016/j.acalib.2008.10.014 as it might be displayed in a citation, the article is not found. Anything preceding the DOI registry number (including doi:10.1016 for eg) will not result in a successful search.
78 votes -
Stop the difference in the item display between Alma and Primo when the description field is filled in
I would like to see all monograph items display as such in the Primo location tab.
Currently if an item (even if tagged elsewhere as a one time monograph) contains anything in the Items description field Primo is treating the item as a serial.
For an explanation of how Primo does this see the following knowledge center article: https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Difference_in_the_item_display_between_Alma_and_Primo_when_the_description_field_is_filled_inThis is a problem as it prevents users from easily seeing the availability information.
See for example the attached screenshot where the number of available titles does not display.Please change the logic in Primo so that it does not treat…
78 votes -
Make configurable preference of source in deduplication
Preference of records coming from differente sources in deduplication is hardcoded in Primo and it causes undesired situations, for example poor SFX records have preference over rich ILS records and the information from ILS records is discarded. Order of preference of sources should be configurable through Primo Admin interface instead of being hardcoded
78 votes -
new option/checkbox: "expand my results with synonyms"
The Primo Search Engine includes synonyms by default to expand the result list. This often leads to results which are fuzzy and hardly explainable.
Instead of including synonyms by default we want to see an option to include synonyms by explicit user decision.
This option ("expand my result using synonyms") could be included into the facets section or should be visible close to the search button.
78 votes -
error page for samlLogin internal server errors
Currently any SAML error on POST /primo_library/libweb/samlLogin results in internal server error response (HTTP 500) and shows a corrupted paged from the old UI (see attachment)
Please implement a SAML NUI error Page for these types of errors including the SAML Error description which is currently only written into library_server.log files, e.g.:
2019-09-17 08:36:39,773 ERROR [t-ajp-bio-7701-exec-19] [c-Saml20MessageValidators] [O -(540627545,1652141697,null)] - SAML failure: This reponse samlSessionId does not match ours
2019-09-17 08:36:39,773 ERROR [t-ajp-bio-7701-exec-19] [c-SAMLLoginServlet] [O -(540627545,1652141697,null)] - SAML failure: Response was not verifiedEvent though the end user may not understand the technical details, theses SAML messages are at least…
73 votes -
Export to Excel
We would like the "Export to Excel" functionality to be configurable. For exemple, we would like to remove the permalink column from the file.
73 votes -
Option to deactivate the Resource Sharing Request Service for records without physical item of electronic/digital services
Dear colleagues,
this idea is for adding the option to deactivate the Resource Sharing Request service in Primo VE for some groups of records without physical item of electronic/digital services, without having to deactivate the Resource Sharing Request rule in Discovery Interface Display Logic.This deactivation should be applicable only to local records (catalogued in Alma) and the single institutions should be able to decide if enable it or not.
We would like the same behavour that exists for Primo also for Primo VE (for example, indicating to Primo VE that when the availability is "no inventory" ILL must be…
73 votes -
Primo Analytics - add the ability to monitor availability link clicks by availability category
Currently usage statistics may be generated using the "Click on availability statement" Analytics action, however there is no way to differentiate clicks on say, "Available at" (for physical resources) and "Check online access".
We would like the ability to extract availability clicks by category:
Check online access
Available at
No full text
etc.General use cases:
To help us decide what types of links should display where and in what order in Primo.
More specific use case:
To help us understand how patrons are accessing electronic resources. For instance, we have added the BrowZine PDF fulltext link to Primo. We…
70 votes -
Hover-over article abstract in PRIMO VE
Currently, patrons need to go into the full article record from the brief results page to read abstracts.We would like to suggest that PRIMO VE provide the user with a hover-over article abstract on the brief results page so patrons can skim abstracts before going into the full record.
69 votes -
Free text input should be blocked in Resource Sharing Form
When users request items with multiple volumes in the resource sharing form (NERS Enhancement - Request ID #4856), they can select a specific volume from the pull down list, also freely input any information in the text box. Errors of manual input may lead to inefficiency or failure of handling the requests, for example, user input “1” in the text box instead of selecting “v.1” from the list, the request can be created successfully, but information of requested volume cannot be shown in Alma, neither “Borrowing Requests” of Borrowing Library nor “Pick from shelf” of Lending Library, the libraries need…
69 votes -
send eMail for logged in users only
Currently, Primo can be used to send spam via the sendTo in the details tab. Anyone can send a message to everyone. Sending E-Mail should be possible for loggedIn users only. Indeed, there is a google reCaptcha service, but activating it is yet not acceptable due to data protection policy issues of many universities.
68 votes -
Changing the language in Primo should also update the preferred language in Alma
We have a mix of users with different languages at our university, but we cannot get a reliable language setting from the SIS feed. Therefore it is important that the users can edit the language preference themself to get letters from the library in the correct language.
Today, changing the language in Primo only changes the interface language in Primo, but we would like it to also update the preferred language in Alma.
68 votes
- Don't see your idea?