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.
409 results found
-
Add double dashes to subject heading displays between subdivisions
The standard display of subject headings, as seen in the Library of Congress, is to place double dashes between their subdivisions. So "$a Germany $x Politics and government $y 19th century" would be displayed as "Germany--Politics and government--19th century." However, Primo VE only places the subdivisions together without distinction, resulting in "Germany Politics and government 19th century." This is is less visually clear to users and isn't consistent with standard practice; it should be a simple matter for Primo VE to place double dashes where a subfield indicator belongs.
4 votes -
collection discovery
Currently grid items in Collection Discovery can show title, resource type and thumbnail. We would like to add creator/author and or creation/publication date if possible. My suggestion is to add configuration for changing what is displayed in the item grid elements in Collection Discovery.
25 votes -
OpenURL resolving - BaseURL configurable for extension to consortial network
If an OpenURL request comes from external to Primo VE, then only the inventory in the IZ is considered and there is no possibility to extend the request to the physical inventory of the corresponding consortial network.
Suggestion for an enhancement: the BaseURL for OpenURL-request should be configurable in a way that the argument "consortial network" can be included in the request [i.e. with the configuration it can be decided whether only
a.) the inventory of the IZ (or Campus)
OR
b.) also the physical inventory of all libraries of the consortial network should be displayed (i.e. analogous to "search_scope")”51 votes -
Add target_url to DisplayCTO output
There is a feature in Primo VE to debug OpenURLs. You add to the OpenURL the parameter &displayCTO=true, e.g. https://uzb.swisscovery.slsp.ch/discovery/openurl?institution=41SLSP_UZB&vid=41SLSP_UZB:UZB&id=pmid:24881163&sid=Entrez:PubMed&displayCTO=true
Now you find between the metadata and the inventory a button "DISPLAY CTO". If you click there, you get an XML file with the metadata details that are available to Primo VE at the moment as well as data for the online services Primo VE will offer the user. However, one important information is missing: The target URL the service will link to is not displayed.
If you, however, use the debug URL of the Alma Link Resolver: https://slsp-uzb.alma.exlibrisgroup.com/view/uresolver/41SLSP_UZB/openurl?svc_dat=CTO&debug=true&debug=true&id=pmid:24881163&sid=Entrez:PubMed
You…
88 votes -
1 vote
-
"Exclude all CDI Books from all different reference types"
Make it possible to exclude ALL CDI ebooks even from databases
16 votes -
Add 007 to MARC control identifiers for display and search normalization
This would enable normalization rules to target specific resource types.
In cases where MARC data may differ based on current practices (MARC 245 $c: Side B titles vs. Statement of Responsibility), we would be able to differentiate records that may contain uniquely catalogued data.
25 votes -
Improve indexing of in press articles in CDI
The Central Discovery Index (CDI) includes many in press articles (i.e., articles that have been accepted for publication in a future issue). However, because these records do lack a pub date, volume, or issue number, the Alma link resolver cannot reliably determine whether an institution has access to these articles. We ask that Ex Libris improve they way in press articles are indexed in CDI so that the link resolver does not return false positives for content the library does not actually own.
486 votesThis improvement is planned for the 2024 Roadmap.
-
Configure new searches to automatically exclude facets from result list (2022)
As a user, I want to configure Primo to automatically exclude certain facets from search results so patrons do not have to exclude the item with every new search
The solution would be configurable.
The default configuration would have no exclusions defined.Using Resource Type: Reviews as an example:
- The institution uses the solution to exclude Resource Type: Reviews.
- The solution adds [facet=rtype,exclude,reviews] to the query. The behavior would be the same as if the user clicked the Exclude button next to the resource type: reviews.
- Users would be able to modify their filters like usual.
Query without configuration:
/discovery/search?query=any,contains,Carrots&tab=Everything&search_scope=Everything&vid=[institution…19 votes -
Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation
When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.
What we wish to achieve is the following:
When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of…
659 votesHi all,
We are currently reviewing this idea together with Alma.
We will update with any new information we have.
Best regards,
Yael.
-
Sorting of multiple copies according to item policy "available for loan"
Our library for medicine offers a large number of copies of some standard works. Some of them are not borrowable because they belong to the reference collection (item policy 63). Other copies have the item policy "available for loan, 1 day" (item policy 59) or "available for loan, 28 days" (item policy 01).
Example; https://slsp-network.primo.exlibrisgroup.com/permalink/41SLSP_UBE/hnud4r/alma99116892929105511In the details display (get it), the items that can be borrowed for 28 days are displayed last and are very difficult for users to find.
Ideally, the filter function should be adapted to contain the option "available for loan", so that patrons can choose…85 votes -
Physical items sort routine by date - enable I J K descending, but A B C ascending
Hi
We're running into a problem with the Physical items sort routine - Sort according to date.For journals, we want to sort the latest item on top, this works correctly with
Sort according to chronology I/U/K (year/month/day) - DescendingBUT
The same sort routine is also used for multi volume monographs.
We found out that if we only fill out conditions for Chronology I J K, but those fields are empty, the barcode gets used for sorting.
Which leads to wrong sorts.So we had to add
Enumeration A, B, C as a condition.This leads to…
91 votes -
Extend the limit on the Summary Holdings Display to more than 10 holdings.
If a title is held at more than 10 locations, its holdings summary will not appear on the Locations page—however, the more locations, the higher demand for checking the range of the coverage. Therefore, please display all summary holdings regardless of the number of holdings.
48 votes -
Ability to set default purchase request library for all users with Purchase Request Form
We would like the option to set a default purchase request library that is selected/displayed automatically in the purchase request form in Primo VE, regardless of whether the patron submitting the form has a purchase request library selected in their Alma record. This would allow the purchase request form to come to us in Alma with the correct Owning Library filled in automatically (as we only purchase via one of our libraries).
1 vote -
Uploading images for New Tool-Give Us Feedback
An image means more imformation, it will help us to understand the questions of reader better. Of course, it would be nice if there was an instant chat window.
17 votes -
Improvement of the Calculate queue button on request forms
In July 2020 a new button for calculating the patron’s place in queue when requesting a physical title was introduced. The function was a welcome attempt to make it clearer to the patron how long he/she might have to wait to get the book, but with the current design we find it more confusing than helpful. The function does not take into account if any items are available in the library or if all items are on loan to other patrons.
When a user places a request on a title that is available in the library the current message is…
6 votes -
Purchase/Resource Sharing request forms - autofill details with ISBN
Would be very handy for end-users to be able to use the ISBN to autofill the details of an item on the generic Purchase request/Resource Sharing request forms.
At the moment it only autofills the details if using the request form on a Primo record (as it uses the metadata from there), or by using DOI/PMID on the Resource Sharing form.
4 votes -
Primo VE: Re-instate the A-Z browse function for DATABASES
Re-instate an A-Z browse option for Primo VE Database Search, like the one available for Primo Classic.
201 votesThank you for this idea. We are currently examining it also as part of the NERS voting (7820).
-
Collection discovery display shut off independent of collection path display
We would like the ability to have a collection not display with other collections in collection discovery but yet still have the collection link available in the collection path to give a results list for students of all items in the collection.
Just a toggle on or off for collection discovery display is needed. Right now, we have to suppress the collection to avoid display, but then it removes the collection path link too.
1 vote -
Display snippets in brief results for physical records when search terms appear in formatted content (5xx) fields
It would be helpful for Primo VE to display highlighted snippets in brief results for physical records (like the full-text snippets for CDI records) when a user's search terms match on text that is in a formatted contents field.
For example, if a patron currently searches for the title of a volume within a multi-volume set (and the search terms used for that volume title do not match on any other fields present in brief results), the record for that multi-volume set will appear in the search results, but with no obvious indication as to why (although the matching search…
1 vote
- Don't see your idea?