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.
659 results found
-
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…
135 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.
35 votes -
Enable search and browse also for item call numbers, not only holdings
Hi
We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.
https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel
"Item Call Number – is it in Primo VE search indexes?
• The item call number cannot be added as a Primo VE search index.
• Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are…
582 votes -
"Exclude all CDI Books from all different reference types"
Make it possible to exclude ALL CDI ebooks even from databases
19 votes -
Enable retrieval with/without/compound hyphens in Hebrew
It is very important to enable the search in Primo with and without hyphen to retrieve all relevant records (with hyphen, without hyphen and as compound words).
Some examples of current discrepancies in retrieval are:צפון-קרוליינה retrieved 2 results
צפון קרוליינה retrieved 486 resultsעת-מול retrieved zero results
עת מול retrieved 83 results, including the title עת-מול : עתון לתולדות ארץ ישראל ועם ישראל. searching using the pre-filter Title and limiting to 2010-2021 for
ארצות הברית retrieves 71 results
ארצות-הברית105 votes -
"Feedback Tool" for the New Primo UI: insert the e-mail of the logged in user automatically
Currently the field "e-mail" in the Feedback form is defined as optional.
As well as with the current e-mail functionality of bibliographic citations, we would expect the e-mail to be automatically pre-filled when a user is logged in. But unfortunately this does not happen.
Please insert the e-mail of the logged in user automatically or at least give us the possibility to set this option in the Primo backend.
Thank you in advance!
P.S.: Please see also this Idea:
Feedback Tool for Primo VE - allow user's email as addressFrom in Report a Problem Letter
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45350419-feedback-tool-for-primo-ve-allow-user-s-email-as19 votes -
Add Generic Record Actions
In View Configuration > Brief Record Display > Record Actions, implement the function of adding generic icons to the Full Display.
It should be possible to add:
- An icon file
- A label
- A URL template(if possible using variables)This would decrease the amount of programming necessary to add new features and expand on the amount of information that can be added(Eventhough you can already add a lot of features)
9 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…
90 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 -
1 vote
-
Facet "Availability" : display order
I would like to be able to choose the order in which items are displayed in the "Availability" facet, and thus put the most important ones first.
In the backoffice, a "display order" column exists. I created a case to know why the display did not correspond to my choice. The person who answered, told me that it was not used in the user interface, and that it was considered as an improvement request.
1 vote -
Allow removal of main title enlargement upon hover in Resource Recommender banner
The default (and expected) behavior of the Resource Recommender banner results in an enlargement of the text entered for the main title field. We are unable to modify this behavior via CSS, find the transition jarring, and would like to have the option of no hover effect or, at minimum, a less extreme one.
4 votes -
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…22 votes -
Option to highlight the edition statement in brief results
Hi, in a recent student survey we received feedback that the edition of a work should be more prominently labelled. It would be good if this text was more obvious in the brief results, perhaps with a different colour, positioning or size?
5 votes -
Display Logic Rules - Access Model
Add the ability to configure display logic rules based on access model of items. For example if the same title is available from one collection as DDA, but is UA in a different collection, display (or prioritize) the UA link.
5 votes -
no javascript required for Embedding a Primo Search box
separate the search filters such as "any,contains," from the actual query terms so, javascript is not required for creating embedded search boxes
many places do no allow any javascript from endusers on their CMS
4 votes -
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…89 votes -
Primo does not work with some date formats used for old material and rare books.
Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.
Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are…
59 votes -
WISO Videos Technik
WISO Videos Technik is already added as a (portfolio)- selective collection to the ALMA CZ.
Please also bring in the CDI functionality as well.
The databases from GBI GENIOS are a very valuable resoruce within the German scientific community.Provider: GBI-Genios Deutsche Wirtschaftsdatenbank GmbH
Freischützstr. 96
81927 München
wiso@genios.de
+49 (0) 89 99 28 79 - 0Thank you very much!
Best,
Bärbel4 votes -
"Feedback Tool" for the New Primo UI: possibility to define the e-mail field as a mandatory field
We have been using the feedback tool for a few weeks now and have unfortunately received many requests where the users did not provide an e-mail address.
As a result, we have no way to ask a question or explain the reported behaviour (as it is correct).Therefore, we would be glad if the e-mail field can be defined as a mandatory field in the Primo back office.
A user can of course still enter a fake e-mail address, but then this is a deliberate action.Thank you in advance!
13 votes
- Don't see your idea?