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.
405 results found
-
Add Limiter to Select PCI Collections in Primo VE Advanced Searches
I'd like to suggest that libraries have the option of adding a limiter to the advanced search area of Primo VE that would allow users to pre-select particular PCI indexes to search. Currently, this can only be done by applying the limiters once search results have been generated.
It would be beneficial if users had the option of pre-selecting which PCI collections to search prior to actually running the search.
0 votes -
Adding Faculty Affiliation and Patron Degree Level to Resource Sharing Form
We would like to add two drop-down fields to the Primo RS form:
1. Faculty affiliation of requester e.g. Humanities, Social Sciences, etc...
2. Degree level of student e.g. BA, MA, PhD etc...These fields would obviously need to appear on the Alma form and be retrievable via Analytics
18 votes -
Display 6XX fields with $v form subdivisions intact
Primo VE is configured to map 6XX $v form subdivisions to a separate display field, breaking the subject string. In some cases, the form subdivision is plucked out of the 6XX, leaving the surrounding string incomplete. For example:
600 10 $aO'Keeffe, Georgia, $d1887-1986 $vExhibitions
displays in Primo VE as:Subject O'Keeffe, Georgia, 1887-1986
Genre Exhibitions
651 #0 $aRome (Italy) $vMaps $vEarly works to 1800
displays in Primo VE as:Subject Rome (Italy)
Genre Maps
Early works to 1800And so on, for all 6XX $v form subdivisions. This cannot be reconfigured. Additionally, each occurrence of the form subdivision is displayed…
251 votes -
Control Purchase Request Display in Primo by Material Type
Using display logic rules there is no easy way to show the Purchase Request link based on material type. We want to enable the purchase request link for ebooks, but not ejournals. I did come up with a hackey workaround by creating a GES that only does the identification of the journal and then a display logic rule to hide the purchase request if this GES is present, but there seems like there should be a better way to do this?
192 votes -
Improve Display Logic in Alma Uresolver to show all variant coverage statements in a collapsed menu
Ideally, Alma should be able to display ALL unique variant coverage statements when showing a collapsed menu.
If a library uses the Display Logic rules to for example show Proquest as an option only once in a services menu, this works very well where a journal may be in 12 Proquest databases with the same coverage.
However, when the coverage varies significantly between these databases, Alma uresolver will still just show one of the coverage statements and a user will only see a subset of holdings and believe this is all the library has. (eg Nursing standard in Proquest is…
159 votes
- Don't see your idea?