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.
411 results found
-
Configure fields included in Course Information
We would like to be able to modify the default configuration of Course Information field displayed in the details view of the full record in Primo VE, adding to or deleting the default elements (Course ID, Department Name, Course Instructor Name) or changing their order. For example, an institution may want to include only Course ID and Instructor Name but not Department Name here. This is not currently possible.
157 votesHi,
This is to update that this issue is still not planned to be developed in the current road map. We will continue to evaluate it for a future release.
Therefore we are keeping this under "Under review" status.
Best regards,
Yael.
-
Provide LibGuides Type Functionality in Studio
Expand the new Primo Studio functionality to include an ability to create content like many of us are using through LibGuides. A simple content management system that would allow us to create simple web pages would allow us to replicate things like subject guides directly in Primo. If that content can also be indexed and searchable through the Primo VE search box that would be even better! This would avoid the need for seperate systems like LibGuides.
7 votes -
Remove 490 from Browse Index
We would like the ability to remove certain fields from the Browse Index - specifically the 490 field. We still want it included in the Keyword Index, but not in the Browse Index. The reason for this request is that the 490 series description field is displaying in the Browse bib headings in Primo and Alma. This results in two series fields displaying, when there is only one series.
12 votes -
Improve Author/Creator search results
We want more control over Author/Creator search results. Ex Libris has informed us that the author/creator searching norm rules are hard coded and cannot be changed. Currently our results include MARC fields 245 (statement of responsibility) and 600, 610, 611 (names as subjects). We don't want these fields included and would like to be able to sculpt search results through MARC field editing. Inclusion of these fields confuses users in author searches and returns results that are irrelevant when searching for works of a known author.
12 votes -
Allow Search Box Placeholder Text to Be Customizable by VIEW
The search box placeholder text is customizable in the Code Table (nui.search.placeholder) but the change is global. It would be much more useful if the default could be set in the Code Table and then further customized in each view if desired. Or, if that isn't possible, to remove it from the Code Table and just make it a customizable field in each view. Or, if that isn't possible, at least a check box in the view settings that would allow us to remove/hide the placeholder text that was set in the Code Table.
It's great that we can make…
5 votes -
Do Not Highlight Stop Words in the Results of a Keyword Search
There is no value to highlighting words in the search results of a keyword search that were considered STOP words when the search was conducted.
Words such as AND, THE, OR, IN, TO, etc., provide no value on their own and should not be highlighted. Not only does highlighting them add visual noise to the search results, it sends the wrong message to users about how to construct a strong search string.
As the screenshot shows, the highlighting is only adding noise.
299 votes -
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…
250 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?
193 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?