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.
1133 results found
-
Actions - email record function - Please give indication an email has been sent
When emailing a record (via Actions - email ) it would be great if there was some indication that an email was sent. We often get several emailed records from clients regarding the same item – and one has mentioned it would be great to know it’s been successfully sent. Currently the pop box for entering email details just disappears once submitted.
7 votes -
Primo does not distuinguish between see references and see too references
Please see public ticket 423179 opened by our University.
Sadly we have discovered that "Primo does not distuinguish between see references and see too references". In our opinion this would be an useful improvemet28 votes -
Add a prm-alma-mashup-after angular directive
It's hard to work with the alma-mashup without the prm-alma-mashup-after directive and the lack of the directive is inconsistent with the rest of the markup in Primo.
21 votes -
sortedy by call number
The current "Sorted by" options are Relevance, Date-oldest, Title, Author, and Date-newest. It would be helpful to also have the option of "Call Number."
25 votes -
"Save query" for zero results
Add the "Save query" option to zero-results pages (similar to how it already appears on results pages) for when you want to be notified of expected future results. For example, you might want an alert for a recently published article not yet in PCI, or an emerging topic that nothing has yet been written about.
24 votes -
German search character conversion - combined vowels representing umlauted letter as well as umlauted letter
In German, an "umlaut" over a letter can be represented with the two dots over the letter, or as a vowel combination, e.g. Anfänge or Anfaenge. If the user searches any of these (or just the un-umlauted letter), we'd like them to see results that contain all the variants.
Ex Libris investigated the configurations for character conversion in searching/indexing, and suggested filing a Primo enhancement:
" it is not currently possible to convert ü into u and also into ue. This would be an enhancement request. "
Which we will do, but wanted to float it here also.
4 votes -
Display virtual browse by shelf mark as default (without mouse-over)
The new PRIMO Ui virtual browse has changed the display of the shelf mark information. You need to do a mouse-over to see the shelf mark. The suggestion is to make shelf mark display as default (as in the old UI), publication year as an option in back office or maybe have both shelf mark and publication year on different rows (without mouse-over solution).
1. Will all users understand it’s a mouse-over solution here?
2. Will all users be able to display the shelf mark with mouse-over? Compatible with all major web browsers? The mouse over doesn’t work in Safari…6 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 -
Subject words also in brief display
We would like to have the option to show subject words in the brief display mode. This would help users determine if hits are relevant faster.
3 votes -
New books link in Primo home page
We would love seeing in the Primo home page link to new books added to the collection. after developing the new book facet it'll be easier to implement this feature using the data added to the PNX.
103 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 -
[Primo] - UI - show Call Number in My Library Card - Requests
The information about the shelfmark and physical position of an Item (i.e. the Physical Location and the Call Number) in not displayed in the Requests section of My Library Card. It is not displayed even if you expand the row (see attachment).
The same happens in the old UI, if you click on Details. It might look like a minor issue, but it's not. Users looking at their requests have no clue where they books are actually located. They are forced to perform the search again for each item they requested. Consider that in many cases items are not moved…
29 votes -
Read-only permission set for back-office users
As both a training tool and for wider understanding of the primo product, we would like to have a read-only permission profile where heads of public service or others could look up configuration/normalization settings, but not commit permission changes. As it stands now, each permission set has the ability to write to at least one area of back office. We would like a 'do-no-harm' account that senior or technically abled library staff could review/suggest changes without having the ability to make the change.
15 votes -
Primo Analytics: ability to report on Primo API usage
Idea: Ability to report on Primo API usage (e.g. number of searches, search terms and source of API calls).
Include usage of Primo Front End and API as part of Primo Analytics so that both can be aggregated and analysed.
Developer Network API Analytics is not sufficient and does not provide the essential information we are looking for, e.g. search terms.
26 votes -
Pull database recommendations from Alma holdings
The resource recommender in Primo currently requires us to manually upload files which list databases or other resources we want to recommend.
Given that most/many? Primo users are on Alma as well, it would be good for primo/alma institutions to have autopopulated database recommendation choices (that can be turned on or off at will) from Alma local holdings.
This is similar to how Summon's database recommender works with 360core knowledgebase.
This creates better efficiency compared to creating seperate lists for the database recommender because if the URL changes or the resource gets cancelled, one would have to update one place…
11 votes -
New UI - allow full results to be opened in a new tab
In the old interface and in summon it is possible to open full details pages in a new tab while keeping the full results list open.
In the new ui this is not possible. As one of our academics says
"I prefer to review the results page first, opening potentially useful results in new tabs (using 'ctrl+click' ) so that they load 'in the background'. Then I can review each tab without disrupting the original search results (and come back to them later if necessary). "In the new UI the full record opens over the results list and has…
2 votes -
Improve RTA Holdings status information for checked out / unavailable items for Alma consortiums
For Alma / Primo customers in a consortial resource sharing network, when an item in an institutional view is checked out, in the brief results display, an RTA availability statement is replaced with a "Check Holdings" link. Upon clicking on the title and viewing the full display of the record, RTA is checked for all institutions, including the institution of the view the user is in, updating the RTA status. When the user clicks out of the full record, the correct status (e.g., Checked Out) displays in the RTA section of the brief record in the results list.
Users should…
100 votes -
Getit2 of PrimoCentral records lists irrelevant local resources (missing date check)
Records from Primo Central have a getIt2-Tab which lists print resources from local catalog for an article. The problem is that the publication date of the article and the listed resources do not match and therefore cause confusion. Think of an current article from a Journal and you get old volumes suggested from the library. Only print resources containing the article should be listed.
In other words: The function would be usable if the getit2 lists print resources with the same publication date.Suppressing the get-it tab according to the documentation (http://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Remove_GetIT!_Tab_When_No_Print_Version%2C_Only_Electronic_Records_from_Alma) has no effect.
The issues were…
26 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 -
Sort date of FRBR groups in date-sorted results lists
When sorting a brief results list by date, obviously always the sort date of the earliest member of a FRBR group is taken to represent the whole group. We would expect that in sort order "year (ascending)" the publication date of the earliest member record is taken, and in sort order "year (descending)" the publication date of the latest member.
6 votes
- Don't see your idea?