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.
1160 results found
-
Display times in Back Office according to local timezone
Currently Primo Back Office displays all times according to the server timezone. This is particularly relevant to scheduled pipes. For smoothest operation these need to be coordinated with Alma jobs, which are scheduled against local timezones. Differences in daylight savings times mean we have to update our conversions between the two timezones at least twice a year.
Being a multi-tenanted environment, the underlying server timezone can't easily be changed. But my suggestion is to make the display of any times in Back Office depend on a configurable timezone. ie
1) Allow institutions to configure a timezone
2) Where times and…
20 votes -
Create link for patron to report issue with Primo Central Record
This idea comes from a ticket submitted by a professor last week regarding a journal article resource that was marked as "peer reviewed" in PCI incorrectly. She reported it to us and we reported it to ExLibris, but it would seem more efficient to include a link that could report the problem directly to ExLibris for PCI content. I imagine something similar to the "report an issue" link found in google books: https://www.screencast.com/t/BdLZo2tR6D
57 votes -
Set default language in Primo Back Office
It would be useful if Primo Back Office users were able to set their own default language preferences (e.g. for content of the code tables) rather than have to select the language every time.
5 votes -
Add configuration option for displaying time as military or non-military
Libraries should be able to choose whether to display time as military or non-military, based on local preference. It would be optimal if there was a per-view configuration option for making this choice.
6 votes -
Untick the box "specific edition only" on the resource sharing form
On our user's resource sharing form, the box "specific edition only" is automatically ticked.
It's not efficient and helpful because almost nobody untick this box. And when we search the book and don't find the "right" edition, we don't know if the tick is desired or just by default.
So each time we meet this situation, we have to contact our user and it's a waste of time.If the box "specific edition only" is untick at the beginning, we know that we could trust in.
3 votes -
Copy parts of Normalization Rules Sets to other fields in the same set
It would be very useful to be able to copy subsets/blocks of a Normalization Rule Set to other blocks/fields in the same set, instead of manually copying very complicated rules. This was a NERS request from the Free University of Bozen (4440), but it did not receive enough votes.
38 votes -
Send the same enriched query (stemming, synonyms, etc) to both local index and Primo Central PC index ( important for blended search )
As default behavior, Primo not only looks for the patron's query, but according to the guessed language enriches the original keywords of the user with additional terms, in order to improve the performance. Linguistic features ( https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Technical_Guide/120Linguistic_Features ) may be customized by the systems librarian, for example removing or adding synonyms. But these changes affects only the results coming from the local index (i.e. the index built with records coming from the library's pipes for the catalogue, the institutional repository etc.). Primo Central (PC) records are not affected: for PC records the query enrichment is run separately and using the…
19 votes -
Show the terms added to the patron's query by the linguistic features (i.e. stemming, synonyms etc.)
As default behavior, Primo not only looks for the patron's query, but enriches the original keywords of the user with additional terms, in order to improve the performance.
The system first tries to guess the language of the query, and then tries to enrich it, using a variety of steps described in the Linguistic Features section of the documentation: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Technical_Guide/120Linguistic_Features
For example, a query for the string: Birne
if recognised as German, is enriched with following synonyms (dictionary file as to March 2017):gluehbirne(normal),gluehlampe(normal),lampe(normal),leuchte(normal),leuchtkoerper(normal),haupt(normal),kopf(normal),ruebe(normal),schaedel(normal)
The point is that the whole thing is a blackbox for both the librarian and the…
57 votes -
Set default encoding level for Export RIS in New UI
In the New Primo User Interface the Export RIS functionality requires users to select an encoding level.
In the classic UI UTF-8 was selected by default.
Can the default encoding level please be an option in the New UI.
Many of our users are confused by which encoding level to select, and we would like to present them with a default option selected to help ease the confusion.80 votes -
Remove or de-emphasize reference entries in Primo Central results
I was told by someone at Ex Libris that the only way to get rid of "Reference entries" (such as a single word definitions from a dictionary, or an encyclopedia entry) showing up at the top of search results, would be to de-activate the subscription to the source item (the dictionary).
This is upsetting. If you happen to subscribe to several encyclopedias and dictionaries that reference a term, the "Reference Entry" items multiply and crowd out the books and articles, which is probably what users are searching for.
We should be able to set the results ranking level for these…
11 votes -
Track the date of when a record is deleted
If primo is given a record to be deleted, it is removed from the source record table. This means that there is no indication that Primo ever had the record. Continuing to track the record id would allow the search PNX tool to tell the user when the record was deleted. This would be useful in tracking down problems of missing records that are expected to be in Primo.
5 votes -
new option/checkbox: "expand my results with synonyms"
The Primo Search Engine includes synonyms by default to expand the result list. This often leads to results which are fuzzy and hardly explainable.
Instead of including synonyms by default we want to see an option to include synonyms by explicit user decision.
This option ("expand my result using synonyms") could be included into the facets section or should be visible close to the search button.
78 votes -
Primo - My Account : Differentiate normal loans & reading room loans
We would like it to be clear for a patron which loans he has at home and which loans are in the reading room. Currently in Primo, there is no differentiation between the two. Is there some way to do this in Alma and or Primo? Thanks
6 votes -
Improve Misleading Links/Terminology in Results
The prominent "Use Get It To Request" link on results with multiple versions, in the case where another version is an immediately available local copy, is not a good thing to have displayed.
We have also noticed the new interface offers direct "Online access" links from the results page (even with direct linking deactivated) which arbitrarily lead to what can be one of several possible destinations, each with different date coverage ranges. So in the case of embargoed content, for example, a user can be misled to think current access is unavailable.
13 votes -
copy a normalization rule set from sandbox to production server
We need the possibility to tranfer NR testet in the sandbox environment to the production server.
8 votes -
Context sensitive help
have a default context sensitive help file(s) in the new UI that can be adapted locally, with local edits being highlighted for change, but not over written when Primo is upgraded and the help text amended centrally.
2 votes -
unix-like tool for working with normalization rule sets
to compare two normalization role sets or for finding spezial references in a rule set we need some tools:
- to compare 2 rule sets we need a tool like the diff command in unix
- to find references to a (mapping) table or occurences of fields in a NR we need a tool like grep in unix
9 votes -
Sliding publication date range bar option
At the moment in Primo the publication date filter gives you only the option to retype the year or to use the up and down arrows. We would like to see something similar to the option in Summon where you have a slider bar which you can drag across to reduce the date range ie: 2006-2017
20 votes -
Add the option to restrict PCI results for resources when only a physical manifestation of those resources exist in the library’s inventory
If we have a physical book/journal in stock (item status could be anything: lost / on loan / available etc.)
and we have PCI collections activated that happen to also include these titles,
then
Primo will display the PCI results for the electronic version of these Books + their chapters & Journals + their articles and present them as ‘Full text available’ with ‘View online’ tabs – even when we do not have access to the online version of the titles.This leads to an error message + makes for a confusing experience for staff and students. We understand from…
23 votes -
Include an option to set Primo Alert for specific latest issue of a Journal TOC (table of content)
Include an option in Primo Alert for specific latest issue of a Journal TOC (table of content) as in the case of Ebscohost Alert Notification attached.
7 votes
- Don't see your idea?