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.
672 results found
-
Customise Purchase Suggestion Form material type list
The Purchase Suggestion Form in Primo VE currently offers a drop-down menu of all possible material types, including things like Ephemera, Toys, and Vinyl LP, which we don't want to turn off as a material type option but we also don't want to offer as a purchasing possibility. At the moment there's no way to switch off material types from that dropdown without removing them as an option for new items completely. We would like an option to customise this purchase suggestion form material type list with more flexibility.
91 votes -
purchase request form - expand where option of auto-populated form can appear
Currently with Purchase Request forms, if there is already a physical copy in stock, depending on the display logic rules set up - the purchase request form link will appear (useful for librarians wanting more copies) this will auto populate the form. However this will only appear when there is a physical copy as it appears in the get it section of the full record view.
For items available only electronically, I can add a GES to allow librarians to go to the blank purchase request form, but it won't auto populate.
This doesn't give parity or a similar experience…
2 votes -
Pair display of 880 fields with their linked MARC field
When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).
In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare…
115 votes -
Primo Collections: Allow NZ records
For consortial users, it would be very helpful to be able to include NZ records in Primo Collections, instead of just IZ records.
3 votes -
Resource Recommender: allow users to dismiss
This is important especially on small screens, where RRs can get in the way when not pertinent to a user's needs.
4 votes -
Portfolio Order
Logic Rules often become complex in showing exactly which holdings to display. We would like to have the ability to rank(or order) portfolios based upon institutional needs and have an easier way to exclude portfolios that we do not want displayed, without creating an endless amount of display logic rules that can inevitably cause issues.
3 votes -
Allow lowercase Boolean operators
When searching in Primo VE, Boolean operators must be entered in all caps. Many databases and search engines allow either uppercase or lowercase Boolean operators, so this requirement may trip up users and prevent them from getting the results they were looking for.
3 votes -
Add Search within "Journals by Category" results
Journals by Category is less useful since each category could have hundreds of results. For example, searching by the category "Psychology" produces 623 journals. EDS' journal search allows you to search within that category--so in this case, you'd be able to search a specific topic among only the 623 psychology journals identified. We have professors who require students to find ten articles in Economics/Accounting journals that are published in the USA. A search within the category Economics journals for a topic, and perhaps even the location facet, would help these students out!
5 votes -
Display import profile name also for for failed import jobs
Currently, the scheduled job "Import Data to Primo VE" gives us the name of the import profile/external data source that was harvested, but only if the job ran successfully. If not, only the name of the job will be given, but not which profile it ran on. This is true both in Alma and for the corresponding e-mail notifications. We would be glad if this could be changed so that the profile name is always displayed, as the current behaviour is making troubleshooting issues with the import profiles quite cumbersome, especially if several are affected at once.
37 votes -
Primo VE mobile device enhancement
When using Primo VE on a mobile device, such as a mobile phone, if you change from portrait to landscape and then back to portrait, half of the page will become blank, which is not conducive to readers' viewing.
107 votes -
Enable person entity functionality at the view level
The new feature (May 2024) for person entities is either on or off for all views.
For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.
Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from…
56 votes -
Improve Citation Action
We would like to summarize in this idea exchange several issues we have run into with the citation action that inhibit the usefulness of the functionality for our customers greatly. Most of these relate to a lack of language sensitivity on the incoming side of the citation action. We would think it would be good if Ex Libris could work towards an improvement here, maybe together with the Citation Styles Language Project.
The formatting for the page count should be p.DDD-DDD or p. DDD-DDD in 773 $$g according to Ex Libris. The issue with this is that when our cataloguing…
52 votes -
Use "Receiving Date" as a search facet to allow for the configuration of "New Arrivals" pages/searches.
being allowed to use the "receiving date" field, rather than the "creation date" as a facet will help libraries to be able to display new arrivals to the collection; items that are actually in the library and read to circulate. As the "creation date" is often the date of the order, these items are not available for use for many months depending on the supply chain.
9 votes -
Open Access articles to display in full text results
Currently, if only displaying CDI results with full text, articles tagged as open access aren't included. These are only displayed if the user toggles to show results with no full text.
Ideally, articles tagged Open Access would also be included when displaying results with full text. The tag would need to bypass the link resolver process so those results are also included.
This would reduce the number of users putting in ILL requests when they didn't realised the article was available OA.
20 votes -
Primo VE, Quicklinks and "Available Online" indication
We’d like the "Available Online" text in be suppressed if Quicklinks are displayed for the citation in the brief results display.
As the librarians put it:
"to turn off the "Available Online"
link/message if the quick links are available. “And alternately, "... make the "Available Online" link go directly to the article like the "Read PDF" Quicklink option does? "
Reducing the number of possible links to click on would improve Primo VE.
Thanks.10 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…38 votes -
Make DOIs active links in full record display
It would help users connect to content if the DOI in the Identifier field were an active link. This could either be through adding "https://doi.org/" in front of the DOI to display a complete URL, or by simply adding that to build active links behind the scenes. For example, use https://doi.org/10.48331/scielo.LS5RKD rather than DOI: 10.48331/scielo.LS5RKD
This would be especially helpful for open access content in the CDI that is often displayed to users without any links to follow. Copying and pasting the DOI by itself into a browser search produces inconsistent results that often fail to go to…
3 votes -
Create/add in the ability to show and filter ALL content by place of publication and other data point relevant for decolonising collections
With linked data being such a big part of what has being talked about so far in relation to NDE and AI being used in some new projects such as Primo:Research Assistant, we feel that it's the best time to think about using this data and the data in the CDI records to try and develop tools to identifying, show, filter place of publication or nationality of authors.
We have developed our own facet using local fields, regular expressions and information in the MARC 008 to display the place of publication for items in our collection and filter by facet…
5 votes -
Include authentication in QR Code link for favourites
On Primo VE you can generate a QR Code for the page you are viewing.
If the page is a search the QR Code link works, once scanned the search is replicated.
If the page is from your account, LibraryCare, My Loans, My Requests, when the code is scanned it invokes authentication.However, for Favourites, when the code is scanned it shows a "blank" screen if the user isn't already authenticated on the scanning device.
I would like to propose that the link generated for Favourites invokes authentication in the same way as pages for Loans, Requests etc,
1 vote -
Add clickable logo option next to search bar
Some libraries like UCLA have edited their customization packages with custom javascript, CSS, and HTML to add a logo with an embedded link that will take the user back to the main Primo page. This is a useful feature, especially if the default upper left logo is pointed at a library's main web page instead of to Primo, but implementing similar code in other institutions' customization packages can be challenging--especially if it interferes with existing code for other functions. Having a second default logo with link option in this Primo location would be helpful for libraries that want this configuration…
8 votes
- Don't see your idea?