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.
362 results found
-
Allow themes to overwrite/override SASS files
One of the biggest difficulties when theming Primo VE is getting link, background, and search bar colors consistent across the different page types. Because the underlying theme uses lighter and darker variations of colors, just editing the color file isn't enough. This leaves us looking for every variation of selector using browser inspect tools, which is time consuming and very hit-or-miss.
Being able to override the SASS, even if it's only for the complete list of color and font selectors, would be extremely helpful and make theme development more clear-cut and efficient.
Related: Esploro Portal - Enhance color settings, https://ideas.exlibrisgroup.com/forums/929326-esploro/suggestions/45208306-esploro-portal-enhance-color-settings
1 vote -
Signed in user should be able to set their preferred search profile
We have decided to place the Library catalog search profile first in the search box as this is what most of our users need. However, some of our users find this irritating and request for the All or International articles option to be put first. This is obviously a choice that's always going to make somebody unhappy!
To get around this issue, we suggest that a signed-in user should be able to set their own preferences as to which search profile comes first in the search box.
6 votes -
Ability to boost newer editions as 5 publication dates does not do this job well.
Currently we have older editions showing above newer editions in Primo VE. It would be helpful to be able to boost editions by the number of the edition. Currently the date boost has only 5 possible options in Primo VE. This means you can only add 5 separate years to regulate newer editions showing above old ones. Uses date ranges doesn't work as the edition between the range get same boost. Either you need to increase the number of date boost entries or create an ability to boost by edition.
21 votes -
Purchase Request - only allow certain users to put in a request if identifier finds a match on our holdings
If a purchase request finds a match on our holdings, it will warn the patron of it existing on our catalogue and provide a link to view the record, but still provide the option to submit the request afterward.
Would like it so the option to submit request can be made hidden from certain groups of users (Display Logic Rule?). i.e. Make it so Students won't be able to submit a request if it exists on our holdings, but still allow it for Staff
1 vote -
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 -
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 -
Primo Analytics - language usage
On Primo Analytics, make it possible to see which language users are selecting e.g. Welsh and English.
27 votes -
Remove journal categories
Make it possible to remove or hide irrelevant HILCC categories from the Browse Journals by Category feature. Currently, trying to remove a category from the hierarchy leaves a gap in the visual display. Because the hierarchy has a very US-focused perspective, many of the categories are not relevant for institutions outside of the US.
1 vote -
Report a problem - allow users to add an attachment
When patrons are reporting a problem in Primo user interface, usually adding a screenshot is very helpful for support.
Can "Add attachment" be added to the Report a problem form?
Petra
52 votes -
More thumbnail source options or additional parameters needed for Primo VE
Would like the ability to either pull from CDI source fields for thumbnails for example the way the CDI for Naxos can use {{control/sourcerecordid}} to build the link for online access. We need to be able to use this same field to pull in the thumbnail automatically. Alternately or in addition another option would be to allow additional logic from another Marc field to determine whether a field should be used. e.g. Use 035a for $$LinkingParameter1 IF 040a = Naxos.
1 vote -
Default sorting order in Loan Display
We would like to have an option to select the default sorting order from "Due Date - newest", "Due date - oldest", "Title" in "My Library Card > Loans > Active Loans" and "My Library Card > Overview > Loans" display.
1 vote -
One index in Primo VE for browing call number
Currently, call numbers with different call number types must be browsed separately, using different call number indexes.
It will be beneficial for both library staff and clients to be able to Browse only one call number index (combining different call number types in the one index) in Primo VE without having to think about which index their call number belongs to.
1 vote -
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.
7 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 -
Generic Field in Resource Sharing Request Form
We use the ILL request form in Primo VE and use the Generic Field to get users to confirm they've checked whether the resource is in stock. This is working well but now for every request it includes the text from the field "Please tick to confirm you have checked Library Search - we will not buy items that are already available.:true" in the note and request note field on the borrowing request. This makes it hard to see specific notes.
We'd like to have the option to stop the generic field text being copied to the fields.
23 votes -
Resource Types set in an Institution Zone should overwrite those set in a Network Zone
The definition of the local resource type depends on the owner of the record.
If the record is owned by IZ - the definition will be taken from the IZ.
If the record is owned by NZ - the definition will be taken from the NZ.
If the record is linked to NZ - the definition will be taken from the NZ.This is inconvenient if some of the institutions in a consortium, but not all, want the general r.type.
Typically, the majority of the data is owned or linked to the NZ.The current situation does greatly reduce flexibility…
17 votes -
Make databases categories field distinguished by institution also for searching
In consortial environment, if the label of a database category assigned in IZ A for a database AAA is the same in IZ B but for another database BBB, this database BBB is also found in IZ A.
Using different local extensions per each IZ doesn't help.
As categories usually are defined with generic names that are used in several IZs, this funtionality is not usable as is in consortial environment.15 votes -
request
Place "request" link (i.e. physical item request) against availability locations as opposed one "request" link that currently appears against the whole availability section of a search result in PrimoVE. As Alma expects items from the same location to behave in the same manner, surely physical item availability in PrimoVE should opperate in the same way - here the "request" link should only appear against a location where all items are on loan and not against the full availability for all locations where physical items may be on the shelf and where a Library may not want "on shelf" requesting. The…
4 votes -
Expandable facets beyond the number we set
Recently it has become possible in VE to display up to 50 facets. 50 tries the patience of the average user but may be what it takes to help those with more specific needs. In some cases CDI limits the number anyway. It would be better if more facets are available this could be noted at the bottom by a "more" link which would then display more than the default number. This would be more consistent with other ways Primo displays complexity.
39 votes -
Filter for which record types, local or community zone, you want to generate the hypertext.
When working with Community Zone records, we see that linking tags, such as 776, appear in Primo in the Related Titles option, and the resource it links to does not return any results. If we deactivate the hypertext link for related titles, the links that were from our records and that are correct would also be affected. We suggest that you can somehow filter for which record types, local or community zone, you want to generate the hypertext.
6 votes
- Don't see your idea?