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.
1129 results found
-
Set default language(s) in PBO
When managing the various mapping and code tables in the PBO, it gets complicated because I'm constantly having to set the language column. It would be great if we could have that narrowed by default to just the ones we need. To support multilingual institutions, it would need to allow for multiple defaults if possible.
3 votes -
Make Title Search in Journals A-Z Left-Anchored
When we search for a title such as "Science" or "Nature" in the current A-Z journal list, the search is not left-anchored and thus finding titles of this kind involves scrolling through several pages of results.
15 votes -
Citation generator is inaccurate
The citation in the existing and new UI for books is not valid MLA or APA.
The PNX information that populates the citations is stored in a hidden mapping table that cannot be edited. For example, I can see that series information for a book comes from addata/seriestitle. Primo will use the entirety of the field in the citation. For this particular record, this is the content of that section:
Rowling, J. K. Harry Potter Ser. ; 2.
Likewise, book titles come from addata/btitle. For this record, this is the entirety of the section:
Harry Potter and the Chamber of…
13 votes -
Ignore call number prefix (subfield k) when indexing for Call Number Browse
Primo's browse search "By Library of Congress Call Numbers" includes the call number prefix (holdings record field 852 $k) when generating the browse list. At UGA, we use that prefix for oversize volumes (Folio, Ff), and for a variety of branch locations, special statuses and shelving areas (Juv, Ref, Vet Med, etc.).
As a result, any holdings with a prefix do not show up alongside holdings in the same call number range, essentially hiding many titles from patrons interested in browsing the shelf list. (This would be an issue for staff as well, but shelf list browsing works correctly in…
145 votes -
Total number of records in PCI
In Summon, one can leave the search box blank and press enter. The result page will indicate the number of total records in the central index and the Resource Type facet also provide a breakdown of record numbers by material type. It allows institutions to track the growth of their content and their distribution by format. It will be great the Primo can offer such statistics.
4 votes -
[Primo] - frbr - improve algorythm - consider all keys and not only the first matching key
In Primo FRBR documentation is explained that (I added ** signs):
"
In the FRBRization process, the keys are compared. If a record has a matching key with another record, it is added to the same FRBR group. Once a match is found, the system does not continue searching for matches since a record can belong to one FRBR group only.
"
In our experience this may lead to false positives. When comparing keys between frbr candidates, the system should consider instead the whole set of matching keys, not just the first matching one. And for example do not group…118 votes -
Allow customization of "Show source records" feature
Since february 2017 relase, it is possible to display MARC record in UI, using "Show source records" feature. As this feature was very much in demand with our users and librarians, we are very pleased.
Unfortunately, the feature's look and feel doesn't live up to our expectations. In the attach file, you can compare the display our users are used to and the actual display of "Show source record". It lacks of clarity.
It would be great to be able to customize this feature's display in order to adapt it to our users needs and to preserve the consistency of…
15 votes -
Index Ebsco API "abstract" Results so they don't appear in Primo "Full-Text" Results
All Primo results from the EBSCO API are searched and displayed "on the fly," and there's no option to sort the abstract-only content from full-text in Primo results.
So even though our default in Primo is to display ONLY "full text" results -- Primo is returning EBSCO "abstract only" or "may be full text" links in our Full-Text searches. Our users are confused, and call us wondering why they don't have full-text access in our Primo full-text search results.
Finding a way to sort the Ebsco abstract-only content from the full-text content, so it's working correctly within the Primo search…
17 votes -
Modify Primo display to use standard MARC holdings.
We're migrating well-formed MARC holdings with 85x/86x pairs but Primo cannot use them for generating displays. Instead Alma must run a job to copy that data into 866 fields for Primo to be able to display them. Primo displays should make use of standard MARC fields/subfields (our 15 year old current system's public interface can do this)
22 votes -
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
60 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
- Don't see your idea?