Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.

Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.

Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate results and consolidate the FRBR groups?

Examples of duplicate records:
Accuracy of prediction of gene content in large animal populations and its use for candidate gene detection and genetic evaluation
3 results (2 FRBR groups):
- TNproquest195858157 and TNfaoagrisUS201300875183
- TNcrossref10.3168/jds.2007-0231, TNscopus2-s2.0-42449094585, TNsciversesciencedirectelsevierS0022-0302(08)71293-1, TNmedline18349258
- TNorbi2268/23076

Linguistic symbiosis between event loop actors and threads
2 results (1 FRBR group):
- TNsciversesciencedirectelsevierS1477-8424(08)00024-9
- TNscopus2-s2.0-51649125887 and TNcrossref10.1016/j.cl.2008.06.005

Efficient control of transient wave forms to prevent spreading depolarizations
2 results (1 FRBR group):
- TNarxiv0705.3398
- TNscopus2-s2.0-39649117125, TNsciversesciencedirectelsevierS0022-5193(07)00579-6, TNcrossref10.1016/j.jtbi.2007.11.019, TNmedline18177900

Le traitement de la modalité épistémique dans les traductions françaises de On the Origin of Species de Charles Darwin
3 results:
- TNerudit1038687ar
- TNscopus2-s2.0-85017546223
- TN_proquest1870219718

Primo Central Index contains many records for abstracts of conference papers that have been published in journal issues/supplements.

These records are given the Article resource type in Primo. This confuses users, who when they find these items expect a full-length article instead of a short abstract.

It also creates problems with link resolvers, which attempt to generate article-level links and fail (publishers usually do not provide these abstracts as individual articles).

To fix this, Primo Central should be given a new resource type for abstracts.

The sources for these records are usually large indexes such as Scopus or Web of Science, which already mark these items as abstracts. This would make it easy to reclassify items as the Abstract resource type.

Primo supports display of See references (not same as See Also) in browse headings, if those cross-references are in the bibliographic data ingested by Primo. There is no capacity to display See Also and Usage info from authority records, which are important so that users understand how and why certain terms, especially subjects, may be used.

We propose that See Also and Usage info display in the Browse headings.

Example headings and See Also and Usage info that does NOT currently display in Primo:

Blacks:

Search also under: subdivision Blacks under individual wars, e.g. World War, 1939-1945--Blacks; and headings beginning with the word Black

Here are entered works on blacks as an element in the population. Theoretical works discussing the black race from an anthropological point of view are entered under Black race.

It's possible this enhancement could be achieved through application of an API that interacts with Library of Congress systems. Display of narrow/broader terms would also be highly valuable.

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.

In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).

We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to only display fields based on the content of some subfields (for example: only display 7XX where $$e equals 'editor', 'publishing director ', 'translator', 'Director', 'film director'...).

In Primo you can activate autocomplete to get suggestions for search-queries based on what the end-user begins to type in the search-box.

We have tested the functionality and see that it could be useful for the end user to get these suggestions. However we see that the suggestions from the central index in some cases are a little strange and that you get suggestions from the entire index and not only the sources the institution has activated. This means that the end-user could get suggestions that gives 0 results.

The local index suggestions seems to be a lot more accurate and useful.

The source for suggestions are determined based on the scope. For local scopes you get the local suggestions, for a remote scope you get suggestions from the central index and in the blended scope you get suggestions from both local and central index.

We would like an option in the scope-definitions in Primo to decide the source of suggestions for blended scopes. Meaning that we could decide that we would like to get only the suggestions from the local index and not from the central index in blended scopes.