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.
302 results found
-
Allow libraries at primary Alma campus to be prioritized in Primo displays
Currently on an item brief display, when multiple holdings exist, the availability statement shows whichever holding library comes first alphabetically, and on the results pages the Libraries facet lists libraries in alphabetical order. This alpha setup is problematic for multi-college / multi-library institutions that use per-campus Primo views. If the campus holds the item, its holding, not another campus that comes first alphabetically, should display in the availability statement. In addition, the Libraries facet should either prioritize the primary campus, or be sorted in order of number of hits (as most facets are) rather than alphabetically.
14 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…
14 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…
14 votes -
Move the Sort by options to top of results
We would like the Sort by option to be at the top of screen, for consistency with other databases. Users are used to seeing Sorting options at the top of the page. These options are hard to locate within the other filtering options in the panel to the left/right of the Primo results.
13 votesHi,
We would like to update that this is planned to be developed in the Primo Next Discovery Experience User Interface.
More details on the new interface plans can be found here -
Best regards,
Yael.
-
Citation generator is inaccurate
The citation in the existing and new UI for books is not valid MLA or APA.
The PNX information that populates the citations is stored in a hidden mapping table that cannot be edited. For example, I can see that series information for a book comes from addata/seriestitle. Primo will use the entirety of the field in the citation. For this particular record, this is the content of that section:
Rowling, J. K. Harry Potter Ser. ; 2.
Likewise, book titles come from addata/btitle. For this record, this is the entirety of the section:
Harry Potter and the Chamber of…
13 votes -
Extend hypertext linking for Relation, Is Part Of, and Uniform Title to remote records
Enhanced hypertext linking for ispartof, relation, and unititle was introduced in the November 2017 Primo Release. These new fields joined existing hypertext linked fields for creator, contributor, and subject.
However, a key difference for the three newer fields is that they only show lateral links in the UI for local records. This limitation is hardcoded, and is confirmed but not explained (Case: 00486499).
Like many sites, we have configured our Primo environment without search scopes with a source-agnostic design, with the underlying premise that users do not care who owns an item or where the record comes from, only that…13 votes -
Auto correct typos
Primo search should have the ability to auto correct common spelling errors and typos.
A current review of our zero result searches has shown that many zero result searches are typos and misspellings.
Users are used to systems that can auto-correct or suggest corrections for misspelled words.
Auto correct of typos would greatly improve the user experience.13 votes -
Adding a hierarchical tree display option to Collection Lobby
Please add a hierarchical tree display option to Collection Lobby. When a top-level collection has many sub-collections across all depth level, it's too hard to browse individual collections and titles.
13 votes -
Make Journal titles hyperlinks
Hi there, users would be helped if search results didn't just bring back links to articles but also had the journal title hyperlinked to take them to the journal's home page or contents page. To help further there could be text box that instructs the user to search for the article they're looking for in the journal's site. Deep links to articles are the most common to fail so this improvement would help students find the articles within journal/publishers sites. Saving time and making them give up less easily.
Thanks for your consideration.
Cheers, James12 votes -
Resource recommender
Currently there isn’t any option to order resources other than alphabetically for the resource recommender.
We have control over the order that the ‘Types’ of resources display by (e.g. Databases, People, Websites …), but as all of our resources are databases, we are limited to the default sort.
Would like more flexibility on this.
12 votes -
Index local in Advanced search
We have a local index with a closed list of values and we would like to present only this list of values to users doing an advanced search.
An example with the local index "Original language" based on the 905 field. This field contains three possible values: Yes, No, Bilingual.
We would like for an advanced search, when the user chooses the Original Language index, to present the closed list that shows three possible values: Yes No Bilingual
12 votes -
Accessibility Menu
Primo need Accessibility Menu Plugin
11 votes -
Embed Advanced Search on Browse/Journal search pages
We have had requests to include the Advanced Search on the Browse and A-Z pages. If one wants to run an Advanced Search one has to return to a new (basic search) search and then click Advanced Search. I had submitted a SF case but the response was that this is not a functionality available in Primo. We believe this would improve usability.
11 votes -
Facets for location of item within a library as well as library
Currently it is only possible to filter search results by the holding Library. The ability to filter search results to a specific location or locations within a library would be useful - for example, to filter the results to copies held at the "Student Library" location and not those held at the "Old Library" location as students cannot borrow items from the Old Library and only want to see the copies they can borrow (those held at the "Student Library" location).
11 votes -
Show exact number of results when browsing instead of 20+
When browsing subjects in Primo, if a result has more than 20 results attached to a single subject entry, that subject displays "20+ records" instead of a specific number, which is what Primo shows for any total less than 20. This happens because Primo uses the Alma browse functionality, but this is not as informative to users as it should be. Instead, users have to click the heading before they can see the exact count of associated records.
11 votes -
FRBR generic: make display of the generic record customizable
We use FRBR generic (in Primo VE) because we deem FRBR preferred to be too confusing for our patrons.
We can't fix the duplicate display of contributors' names.
Example:
https://basel.swisscovery.org/discovery/search?query=any,contains,Homer%27s%20Iliad%20translated%20by%20Richmond%20Lattimore&tab=UBS&search_scope=UBS&vid=41SLSP_UBS:live&lang=en&offset=0, see also screenshot.Lattimore is displayed three times, Martin twice.
As this is supposed to be a generic display, no contributors should be displayed here.
We got the following response from Ex Libris in our case:
"
With the 'Generic record' option enabled, when conducting a search in Primo, in the list of results for a FRBR group, you will see a very generic record which is hardcoded and…11 votes -
Allow customization of the item status field in Primo
The item status field is misleading for material that is on order. Primo displays a message saying “Item not yet received, expected on DD/MM/YYYY”. This date can be several weeks in the future. It is calculated by adding a set number of days specific to a vendor to the date that the order was sent to the vendor. The number of days is set according to when it is judged to be appropriate to claim items which have not been received. We therefore tend to set it as eight or so weeks in the future for many vendors. In reality…
10 votes -
Ability to delete lines from advanced search
At the moment in advanced search in the new UI you can add up to 7 new lines but not delete any of them if you change your mind about a search query and want to delete a line you have added. Clearing just takes you back to the beginning again
10 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 -
sorting gets lost when switching scopes
If a user sets the sorting of the result list, her predefined sorting gets lost on switching between search scopes. In this case, the sorting returns to the default, e.g. "by relevance".
We see this in the new UI as well, but think that users should not be forced to select their preferred sorting again and again.
Please consider this to enhance user experience.
9 votes
- Don't see your idea?