CDI now merges multiple results for the same article together, but when it does it preferences CDI records with 'Link in Record' rather than displaying the Link Resolver choices under Full Text Availability. The Link in Record articles often lead to indexing sites, not to the publisher where the full text is available. We need a config option where we can preference Subscription (Linkresolver) over Link in Record when merging records in Primo

For the Digitization Request, Hold and Booking Request, and Purchase Request forms, the Alma mapping tables (under GetIt Configuration) define the fields that are displayed to users (Yes = viewable to users, No = not viewable to users).

We would like to have the possibility to configure mandatory fields if we want the user to specify a field in the form (as it is already the case with a check box in the Resource Sharing Request form).

Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.

It is not currently possible to select multiple options on an Advanced Search drop down menu is Primo VE (ex: Material Type, Language); this functionality would be very helpful for users who wish to do more precise searching -- especially since Primo VE lacks the functionality of combining search results. This functionality is the HTML select multiple attribute (https://www.w3schools.com/tags/attselectmultiple.asp)

When users log in through Open Athens they still have to click on Primo Log in button

The MARC 260b + 264b field is not included in the out-of-the-box indexing in Primo VE advanced search or facet as PUBLISHER. According to the documentation the publisher name is searchable only by general in the simple search and not in the advanced search, specific search for the publisher name. Readers want to limit the results by the name of the publisher.

We know we can run usage statistics via alma analytics. The usage report is for the internal library staff to decide on different collections. I want to propose to add the functionality to Alma D, where everyone will see the usage report on Primo in a different facet. This is an essential feature, especially for the end-users. If the function is added, the end-users will be able to see the statistical report about the document/resource, i.e., When was the document/resource last used?
Yesterday:
Past 30 days:
Total Views:
Total Downloads:
Total Uses:

The MARC 505$r is indexed in the PNX as Creator and contributor. The MARC 505$t is not similarly indexed in the PNX as an added or alternate title.

Hover texts in Primo VE

In the "Get IT/Location" area in the copy view, all data (for example: section, callnumber, availability, ...) is output again as hovertext (white font with black, semi-transparent background) when hovering over it (see appendices 1-3). The same error also occurs with the Active Filters on the search results page (see appendix 4).

This redundancy disturbs the user experience and already confuses users. In some cases, this phenomenon makes it impossible to see the entire text.
I request that these disturbing hover texts be removed.

It is currently possible to manually add contents of a Set to a Collection that will appear in Primo.

We would like to make it possible to create dynamic Collections that change/update when new items are added that meet the criteria to be added to the logical set.

Right now, as the logical set changes, the Collection contents remain unchanged.

DOI and PMID searching can be augmented for enhancement in keyword searching in Primo VE, so that these identifiers can be searches as keywords. It would be very helpful to our researchers to be able to more efficiently and exactly search within Advanced Search fields for DOI and PMID. These fields can be searched within unique fields in the Citation Linker, so the indexes exist, but they are not available for inclusion in Advanced Search settings. We would like to be able to add DOI and PMID as options in Advanced Search settings in Primo VE.

It would be great to allow search scopes to be combined in PrimoVE so that predefined search scopes and local search scopes can be configured to search as one scope. Currently, PrimoVE is not able to do this and makes searching more complicated to educate end users on how to search.

For Example, Allow 690 and 6XXs to be able to be search all under Subject. Curently Subject does not include 690.

Primo VE shall allow the library to customize the "View full text in collection" label in full record display page under view it section. There are different kinds of "link text" displayed in CDI mode which makes our users very confused.

Users submit a range of pages when they request digitization of a material. Preliminary pages in books often use Roman numerals. Please whitelist these characters along with 0-9 in the form validation scheme.

Fields boosting in Primo VE has not an option for Fields boosting of display field Contributor. The default rule for Contributor is including 700, 710, 711. As an example, that means if you boost the creator field for a book with three authors the second and third author in field 700 will not get boosted, just the first author in 100.