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.
- or
No existing idea results
- ~ No ideas found ~
672 results found
-
My Account - Loans & Requests: Bibliographical Details of ILL article requests
Currently, users cannot see the full bibliographical details of their Resource Sharing "Article" Requests in their account,. Although all the details appear in Alma, in Primo the Journal Title, Year, Volume, Issue and Pages are missing - so in fact they can only see the Article Title and Author in the Full View mode.
Obviously, this is not very helpful for citation purposes or even for tracking orders - especially if there are many similar requests.
Thanks
43 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 Alma.)
Please reconfigure Primo's browse search to ignore (but, ideally, still display) the call number prefix when generating this index.
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…
148 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 records having more non matching keys than matching keys.In attachment an example where the books share the title and only 1 of the authors. This is not uncommon in case of exhibitions catalogues where the artist works together with the curators. FRBR considers the 2 different books as 2 different versions.
Here are matching keys of the record proposed as example:
Record 1 (2006):
<frbr><t>1</t><k1>$$Kubzroyoux jean christophe$$AA</k1><k1>$$Kubzdean tacita$$AA</k1><k1>$$Kubzwarner marina$$AA</k1><k1>$$Kubzgreer germaine$$AA</k1><k3>$$Kubztacita dean$$AT</k3></frbr>
Record2 (2004)
<frbr><t>1</t><k1>$$Kubzde cecco emanuela$$AA</k1><k1>$$Kubzdean tacita$$AA</k1><k3>$$Kubztacita dean$$AT</k3></frbr>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…116 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
55 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.
35 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 patrons. There is no way to know how the orignal query was processed, which terms were added and what was actually searched.
It would be a good enhancement to provide a) to the user i the Front End brief additional information about the terms actually searched, to make the process transparent and understandable b) to the systems librarians extended information about about the terms actually searched, to allow a better understanding of the process and a chance to set up properly the related Search Engine Configurations, the user 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.77 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.
77 votes -
• Records without a date at the bottom of results list when sorting on date oldest
At this moment, the sort option “Date oldest” displays the records without a date on top of the results list. This is confusing and not relevant for users; when there are several records without a Creation Date they probably conclude that sorting on date oldest doesn’t work. Our request is to display the records without a date always at the bottom of the results list when a sort option on date is used (thus as well for date oldest as for date newest)
79 votesHi all,
This is to update that this is currently not planned to be developed. We might evaluate it again in the future.
Therefore we are removing the "Under review" status for now.
Best regards,
Yael.
-
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 be able to see, in their institutional view, that an item is checked out without having to "check holdings" and load the RTA for all institutions. RTA should be accurate even for checked out items when the brief results display loads after each search.
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…
97 votes -
comment request
Add comments on the request in the user's account
We would like that the comments which are written by the user are apparent in the user's account.
See attached files for more explanations.
60 votes -
Provide institutions with the ability to systematically boost the ranking of Subscribed PCI collections over Open Access PCI collections
Often, there are multiple versions of an article offered in Primo. The different versions might be the result of having access through paid subscriptions and open access collections. However, there is currently no effective way for an institution to give systematic preference to the type of collection they want their patrons to see first. We request the ability to systematically boost the ranking of Subscribed PCI collections over Open Access PCI collections.
34 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 a good example in some it is 1998-2013 and others is 2015 +, )
The most obvious case is when using the A-Z list or a general Primo search to find a journal title.
In SFX it is possible to add a year or source parameter to the display logic rule so that the collapse display logic only applies when the user specifies a date or when the open url does not come from the A-Z list. This means that a user wanting to use Primo or the A-Z to see ALL date holdings of a given serial title could see all possible links with their coverage statements, not just one statement per provider.
It would be better if the collapsed menu could be preserved and all the unique holding statements were shown, however, the SFX logic of conditionally showing all links is preferable to the current Alma behaviour.
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…
162 votes -
Primo Analytics: extracts the usernames related to failed logins
It would be great -with Primo analytics- building an analysis that extracts the usernames related to failed logins
47 votes -
alerts based on a range of call numbers
We would like our users to be able to define an alert in primo, based on a range of call numbers – for example:
lc = "ds67->ds79.99" .37 votes -
Second sort in facets
Currently, Primo shows the items in the facets (e.g. the subjects facet) either sorted alphabetically or by the number of items.
However, it seems to order the items randomly when the number of items is identical for several different subject heading in the facet.
It would be beneficial to be able to configure a secondary sort option for these items (for example when using a multilingual subject heading system - to present the same subject in both language one after the other).79 votes -
Add a list of suggestions to zero result searches in the A-Z Journals list
It is not possible to display a list of suggestions when a user retrieves zero results for a search in the A-Z Journals list. However, it is possible in Primo simple and advanced search. It would be beneficial to provide users with a distinct list of suggestions if they retrieve zero results in the A-Z journals list.
37 votes -
Please make the MARC bib. 245 subfield p from the bibliographic record available.
The MARC 245 subfield p from the bibliographic record is not exposed to Primo. This means that the data in the b245p is not available to display to users in the My Account section of Primo, as part of the requesting process and on pull slips for items. This becomes important when the items have 245a data that is the same. For example, when a video game has the same name with more info in the 245p like the ones below.
b245a b245p
Angry birds. Star Wars
Angry birds. Trilogy
Assassin's creed. Brotherhood
Assassin's creed. Revelations
Batman. Arkham Asylum
Batman. Arkham city
Batman. Arkham origins
Call of duty. Black Ops
Call of duty. Black ops III would like to see the bib. 245 p added.
examples of issues attached.
The MARC 245 subfield p from the bibliographic record is not exposed to Primo. This means that the data in the b245p is not available to display to users in the My Account section of Primo, as part of the requesting process and on pull slips for items. This becomes important when the items have 245a data that is the same. For example, when a video game has the same name with more info in the 245p like the ones below.
b245a b245p
Angry birds. Star Wars
Angry birds. Trilogy
Assassin's creed. Brotherhood
Assassin's creed. Revelations
Batman. Arkham Asylum
Batman.…112 votes -
Make configurable preference of source in deduplication
Preference of records coming from differente sources in deduplication is hardcoded in Primo and it causes undesired situations, for example poor SFX records have preference over rich ILS records and the information from ILS records is discarded. Order of preference of sources should be configurable through Primo Admin interface instead of being hardcoded
77 votes -
Configuring brief display for different formats
It would be useful to be able to configure different fields to display in the brief results for different formats within Primo.
68 votes
- Don't see your idea?