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.
1134 results found
-
Clearer messaging around simultaneous user restriction in Alma Digital
We would like a configurable message that lets the user know they have been denied access to an item in Alma Digital because of the simultaneous user restriction. Currently, we are only able to configure a generic access denied message.
Without specific messaging it causes a lot of confusion with users and work for staff explaining what the issue is.
4 votes -
Show ALL data recorded in faceted fields
When a search is done on a faceted field, not all the possible results in any given facet are shown. There is no logical resulting display of faceted values. For example, if one searches for the keyword "Novels" in our sandbox, and then goes to the Creator Demographic Group facet (data from MARC 386 field), you get a choice of some terms like Algerians (53), Americans (1464), Austrians (353) and so on. But Canadians and Germans are not shown in this list, even though there are many records that have 386 Canadians or Germans. If you do a keyword search…
6 votes -
Display Peer Reviewed and Open Access icons when coming to Primo via OpenURL
Our clients can benefit from having the Peer Reviewed and Open Access icons display in Primo when clicking through from a Database or Google Scholar. We would like to meet our clients where they are searching for articles and these two indications are important to them.
Example title: Biological invasions, ecological resilience and adaptive governance
There are Peer reviewed or Open access indications when linking back from Google Scholar: https://sun.primo.exlibrisgroup.com/discovery/openurl?institution=27US_INST&vid=27US_INST:27US_V1&volume=183&date=2016&aulast=Chaffin&issn=0301-4797&spage=399&id=doi:10.1016%2Fj.jenvman.2016.04.040&auinit=BC&title=Journal%20of%20environmental%20management&atitle=Biological%20invasions,%20ecological%20resilience%20and%20adaptive%20governance&sid=google
but we do see these indications when searching the title directly in Primo VE
https://sun.primo.exlibrisgroup.com/permalink/27US_INST/2fbt29/cdi_proquest_miscellaneous_18267127762 votes -
Edit Labels of Primo Saved Items
It would be good to change the text of an existing label(s) used on saved items.
For instance to be able to change a label from "ethics" to "research ethics".
3 votes -
Differenciate display of GetItOther depending on search scope slot
We're in a consortium, with the search scope slots
- IZ
- NZ + CDIIn both search scope slots we want to display the call numbers of all consortium libraries in the full title display.
It is possible to collapse the call numbers from outside our IZ:
https://www.carli.illinois.edu/products-services/i-share/discovery-interface/custom_package_collapsegetitotherBut we'd like to differenciate:
- collapsed in search scope slot IZ
- open in search scope slot NZ + CDI1 vote -
Add a Deploy button to all screens that require a deploy
So may times we forget or don't know that a deploy is required for a change to be implemented into production.
- It would really nice that any feature that requires a deploy a deploy now button be included on the screen (some sections already have this feature)
- It would be even better if there was a banner at the top of the admin panel if there were changes that require a deploy to implement pending so that Administrators can easily see that a deploy is required.
1 vote -
Primo VE - Local Resource Type order to match Primo BO functionality
When defining Local Resource Types in Primo VE, there is no option to adjust the order that the rules are checked, unlike in Primo BO. Being able to define the order of rules can help arranging them from most specific to least specific.
1 vote -
Collection Discovery – enable alphabetical sort for each language
Hi
We are planning to use collection discovery by subject area and would like to sort the collection overview page alphabetically by title of collection.
Our Primo VE interface is multilingual. We'd like to translate the collection names, with correct alphabetical sort in all interface languages.
At the moment this is not possible: alphabetical sort is by the English titles.
0 votes -
New customization package = force browser cache refresh
Primo VE's browser cache is much too strong.
After the upload of a new customization package I have to check the changes in a new private window and tell my colleagues to test in a new private window.
Recently I got sent a fresh screenshot by a patron which showed a styling element that we have changed several months ago.
We can't ask our patrons to use Primo VE in a private browser window if they want to see the up to date version.
=> When uploading an adapted customization package, there should be a forced refresh of the cache…
18 votes -
Registros OA en Primo VE
Actualmente Primo VE muestra registros como OA cuando los mismos refieren a enlaces de recursos suscriptos por la biblioteca.
Una solución podría ser la de eliminar el icono de OA, pero este cambio aplica para todos los registros, incluyendo los que efectivamente enlazan con recursos de OA, de momento no es posible modificar un registro en particular o un conjunto.
Esperamos que se pueda solucionar este problema y que los registros que enlazan a recursos suscriptos no muestren el icono de OA.
19 votes -
Normalization rule to add related links in PNX record
Currently Primo generates Related Links from the 856 field in the MARC. It would be very useful to be able to create a normalization rule that creates links in the PNX that Primo then turns into Related Links. This is possible in Summon, it should be a feature in Alma as well.
3 votes -
Let patrons collapse elements of the full title display
Hi
There should be a setting in the patron account where they can decide which elements of the full display of a title are collapsed and which are open.
The patrons are confronted with a lot of information of which only a small part is relevant to them – but which part they consider relevant can be different.
You can collapse 'Get it from other institutions' (https://www.carli.illinois.edu/products-services/i-share/discovery-interface/custom_package_collapsegetitother) – in the same way it's probably possible to collapse the other elements, too.
21 votes -
Have Location Facet appear ONLY AFTER a Library facet is selected
For large library systems, many locations of stacks, eg. exist making the location facet appear very confusing to users. The LibraryLocation facet is problematic because many library locations are beyond the limit of 20 that's possible to view.
2 votes -
Increase the number of local fields for search and facets
If the library has many specialized and local fields it should be possible to improve the user search without the build-in restriction of 10 locally defined fields. There should not be a limit to use of local fields.
83 votes -
More granular statistics for the actions menu in Primo Analytics
More granular statistics for the actions menu when clicking in brief display, expanded and not expanded (with 3 options), and clicking in full display.
1 vote -
show license
We would like the 'show license' button to be only visible for logged in users. Could you make this button's visibility based on login status?
Thank you!1 vote -
Improve the Export to Mendeley
Include abstracts and subject headings in the Export to Mendeley function
6 votes -
Allow boosting IZ records when displaying FRBR groups
As a member of a consortium, we would like to see our local records displayed first while looking at FRBR groups.
The current sorting and prioritization methods do not help with achieving this.
10 votes -
Allow boosting IZ records when displaying FRBR groups
As a member of a consortium, we would like to see our local records displayed first while looking at FRBR groups.
The current sorting and prioritization methods do not help with achieving this.
2 votes -
Allow custom scopes for CDI records, for an "articles only" drop-down search profile
Currently, custom scopes that allow for setting conditions include only local data from Alma, and do not include any CDI records, even if blended with CDI. This means it is not possible to create a search profile with a custom data scope of with "Resource type: articles". Instead, in order to limit a search to only articles, the user must use the facets on the left-hand side of the page. I think this is a common search parameter that should ideally be available in the drop-down menu to the right of the search bar.
20 votes
- Don't see your idea?