Primo VE 2022 Release Notes
Release: Additional Information:
-
Click here to view the CDI-related updates at the bottom of this page.
-
Click here to view the monthly release and maintenance schedules.
Features
Share Export Action
November 2022 URM-175418
The Share export action has been added to the Brief Display, Full Display, and My Favorites pages to allow users to share records with other users using social media applications.
After selecting the Share action, users can share the permalink using the following social media applications: WhatsApp, Facebook, Twitter, and LinkedIn. In addition, users can save record's permalink to the clipboard by selecting Copy.
Analytics - Share Export
To support this functionality, the following actions have been added to the Action Usage subject area:
| Group | Subgroup | Action | Description |
|---|---|---|---|
|
Document |
Actions |
Share |
The user selected the Share export button. |
|
Copy permalink |
The user selected the Copy button while using the Share export action. |
||
|
Share to WhatsApp |
The user shared the record with users on WhatsApp. |
||
|
Share to Facebook |
The user shared the record with users on Facebook. |
||
|
Share to Twitter |
The user shared the record with users on Twitter. |
||
|
Share to LinkedIn |
The user shared the record with users on LinkedIn. |
Configuration Options
This configuration is disabled by default. The following table lists the configuration settings that are associated with this functionality.
| Back Office Element | Description |
|---|---|
|
View Configuration page (Configuration > Discovery > Display Configuration > Configure Views) |
The Share action has been added to the Brief Record Display tab to allow you to enable the new Share export action, set its position, and set whether it is a top-level action. In addition, you can configure which social media applications are supported. For more details, see View Configuration. |
|
Keeping This Item Tile Labels code table (Configuration > Discovery > Display Configuration > Labels) |
The following codes have been added to support the customization and translation of the associated labels in the UI:
|
Give Us Feedback Improvements
November 2022 PRM-46631 URM-176574 URM-176567 PRM-46795
The following enhancements have been added to the Report a Problem tool:
-
Support the configuration of whether the following fields are mandatory or optional on the Give Us Feedback form: email address and description.
Mandatory Configuration Parameters -
Support the configuration of feedback managers per category. If an email address is not specified at the category level, ensure that a default email address is configured in the Row Details section.
Add Email Addresses per Category -
In your customization package, support the customization of the Feedback icon and Send button, and in addition, support the ability to add links to the Give Us Feedback dialog box via directives.
For more details, see Configuring the Feedback Tool for Primo VE.
Provide Warning Message when Guests Add to Favorites (Idea Exchange)
November 2022 PRM-45846
Guest users will now receive a message when adding records to favorites to let them know that these records are temporary and last during the session only. By signing in, users can save the favorites between sessions.
For mobile devices, the message appears at the bottom of the page.
Configuration Options
This enhancement is disabled by default for existing views, but it is enabled by default for new views. The following table list the configuration options associated with the functionality.
| Configuration Page | Description |
|---|---|
|
View Configuration (Configuration > Discovery > Display Configuration > Configure Views) |
In the General tab, select the new Display Favorites Warning Message for Guests checkbox to enable the display of the warning message. For more details, see Configuring Discovery Views for Primo VE. |
|
aria Labels code table (Configuration > Discovery > Display Configuration > Labels) |
The following code was added for accessibility to indicate that the warning messages was closed: nui.aria.favorites.CloseMessage – Close message |
|
Favorites Labels code table (Configuration > Discovery > Display Configuration > Labels) |
The following codes were added to support the display of the warning and message:
|
Provide Direct Linking from Full Record
November 2022 URM-167764
As with the availability link in the brief results, users can now go directly to full text from the full record instead of being taken to the View Online section to choose from the listed providers. When this functionality is enabled, users are typically taken directly to the full text of the first entry in View Online section.
Configuration Options
This functionality is disabled by default. To enable this functionality, set the new apply_direct_linking_settings_in_full_record parameter to true on the Discovery Customer Settings page (Configuration > Discovery > Other > Customer Settings).
Direct linking must also be enabled on the Direct Linking Configuration page (Configuration > Fulfillment > Discovery Interface Display Logic > Direct Linking) in Alma. Otherwise, direct linking is not enabled in the brief or full displays of the record.
Allow Configuration of CDI Linking Preferences
November 2022 (Updated January 6, 2023)URM-167300
You can now set the preferred order of links to the electronic full text in CDI (Link in Record and Quicklinks) if more than one link is available. Prior to this release, this configuration option was available only for links using the link resolver. Note that this setting is separate from the link resolver settings because preferences are configured at the collection level for the link resolver, while they are configured at the platform level for CDI. For more details, see Provider Preference Order for CDI Linking.
This functionality will be fully supported with the CDI December 7 release.
Configuration Options
The new CDI linking preference options are configured on the Central Index and proxy set-up page (Configuration > Discovery > Other > Central Index and proxy set-up) and apply to single link display (Link in Record links and Quicklinks) as well as multiple links display (see Display All Links setting). If no preference is set, the default provider preference is alphabetical by provider. For more details, see Configuring Central Index and Proxy Settings for Primo VE.
Display Collection Discovery for Specific Libraries / Institutions
August 2022 URM-160698 URM-162491
Previously, there was no way to control the display of collections for institutions in a consortium or for libraries by view in a single institution. With this enhancement, collections are now filtered by library as follows:
-
On the Collection pages, only the collections/sub-collections that are associated with the relevant library are displayed.
-
When searching for items from the Collections Lobby page, only the items that are associated with the relevant library are displayed.
-
The collection path that displays for an item on the Full Display page, includes only the paths to collections that are associated with the relevant library.
-
The More from the same collection area shows only items that are associated with the relevant library.
Configuration Options
This functionality is disabled by default. Refer to the following table for configuration information.
| Configuration Element | Description |
|---|---|
|
Discovery Customer Settings mapping table (Configuration Menu > Discovery > Other > Customer Settings) |
Set the view_to_libraries_for_collection_discovery parameter to true to allow collections to be filtered by library/view. You must also map your views to libraries in your institutions so that they can be filtered accordingly for collection discovery. |
|
Primo view mapped into Alma libraries mapping table (Configuration Menu > Discovery > GetIt Configuration > Primo View to Libraries) |
Use this mapping table to map the views to libraries in your institutions. For more details, see Configuring the Location Filter List for Get It. |
New Resource Recommender Type - Banner
August 2022 URM-161890
The Banner Resource Recommender Type allows libraries to display a persistent banner that spans the entire page and appears above all other recommendations, regardless of priority and persistence. The banner displays the following information: name, title, description, and link.
Users can click the X icon to dismiss the banner for the duration of the session.
If more than one banner is configured and active, only the first banner in the list displays above all other applicable suggestions.
Analytics - Banner Resource Recommender Type
To support this functionality, the following actions have been added to the Action Usage subject area:
| Group | Subgroup | Action | Description |
|---|---|---|---|
|
Exploration |
Resource Recommender |
Click on recommended resource - banner |
The user selected the banner or its link. |
|
Resource Recommender Banner appeared |
The user performed a search for which the banner appeared. |
Configuration Options
To support this functionality, the new Banner type has been added to the Resource Recommender Configuration page (Configuration Menu > Discovery > Other > Resource Recommender Configuration). For more details, see Resource Recommender for Primo VE.
The following table lists additional configuration options for this functionality.
| Element | Description |
|---|---|
|
Results Tile Labels code table |
The following code has been added to support the tooltip for the banner's X icon, which is used to close the banner for the remainder of the session:
|
|
Aria Labels code table |
The following codes have been added to support this functionality in screen readers:
|
Support Persistent Suggestions in Resource Recommender
August 2022 URM-161890
Each resource type now allows you to display its recommendations for every search without having to match a searchable tag. These resources appear first, and if more than three suggestions are configured, you can view all persistent suggestions and the other matching suggestions by selecting the See all suggested resources link.
In the following example, the first suggestion on the left is persistent and appears first in the list of suggestions from Resource Recommender:
Configuration Options
To Support this functionality, the Display Always column has been added to the Resource Recommender Configuration page (Configuration Menu > Discovery > Other > Resource Recommender Configuration) to enable persistence at the recommendation level. When selected, the suggestion displays for every search. The order in which it displays in the suggested results is determined by the priority of the suggestion's resource type.
For more details, see Resource Recommender for Primo VE.
Exclude eBooks from CDI Results - Phase 2 (NERS #6702)
August 2022 URM-153520
In November 2021, we added a configuration option to exclude eBooks from your CDI results. This option is useful if you prefer to use your own eBook catalog records (in your Primo local index) instead of the eBook records from CDI. Turning on this option filters all eBook records from the CDI results, both in the filtered and expanded searches.
With the second phase of this enhancement, we exclude CDI eBook records only for collections that have portfolios in Alma instead of filtering out all eBook records from the CDI results. Books from database collections will continue to appear in the CDI search results. For example, if you have active collections for Wiley or JSTOR books, these books are not returned by CDI, but the books from HathiTrust or other collections without portfolios in Alma are returned.
-
The Exclude CDI eBooks option on the Define a Custom Search Profile page (Configuration Menu > Discovery > Search Configuration > Search Profiles) remains the same.
-
The functionality will change automatically in CDI with the August 2022 release.
-
When this option is turned on, the CDI books are removed from both the 'Filtered' and 'Expanded' searches for all collections that have portfolios in Alma. Only books affiliated with database collections that you have activated (for full text or search) are included in the CDI search results.
-
This option will still display duplicates when a book record is available from both a database collection and a collection with portfolios (and they are part of the same merged record), regardless of your institution's activations.
User Settings for Persistent Search History
August 2022 URM-162744
Primo VE now allows signed-in users to configure whether a user's search history is retained between sessions and whether a user's search history is used for recent search suggestions. To enable this functionality, signed-in users can perform the following steps in the UI:
-
Select the new My Personal Details and Settings option in the User Area menu to open the My Library Card > Personal Details and Settings tab directly.
My Personal Details and Settings Option - User Area Menu -
In the new Personal Settings section, configure the following new options:
-
Allow saving my history – When selected, the user's search history is retained between sessions.
-
Use my search history for the recent search suggestions – When selected, the user's search history is used to provide recent search suggestions.
Personal Settings Options Enabled in My Library Card -
Analytics - Persistent Search History
To support this functionality, the following actions have been added to the Action Usage subject area:
| Group | Subgroup | Action | Description |
|---|---|---|---|
| General | General |
Disable saving search history |
The user disabled the Allow saving my search history option in My Libray > Personal Details and Settings. |
|
Disable using search history for search suggestions |
The user disabled the Use my search history for the recent search suggestions option in My Libray > Personal Details and Settings. |
||
|
Enable saving search history |
The user enabled the Allow saving my search history option in My Libray > Personal Details and Settings. |
||
|
Enable using search history for search suggestions |
The user enabled the Use my search history for the recent search suggestions option in My Libray > Personal Details and Settings. |
Configuration Options
This functionality is not enabled by default and requires configuration at the institution level. The following table lists the required and optional configuration associated with this functionality.
| Configuration Element | Description |
|---|---|
|
Discovery Customer Settings mapping table (Configuration Menu > Discovery > Other > Customer Settings) |
Configuration the following settings to enable persistent functionality in the UI:
|
|
User Tile code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following code defines the label for the new option in the User Area menu: nui.eshelf.menu.userSettings – My Personal details and settings |
|
My preferences Tile code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following codes define the labels for the new options in the Personal Settings section on the Personal Details tab:
|
|
Error messages code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following code defines the label for the error message that displays if the user settings cannot be saved for any reason: nui.mypref.label.errorSavingSettings – Settings were not saved due to an internal server error; Please try again later |
|
Aria Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following codes support the use of screen readers for this functionality:
|
|
Library card Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following codes define the labels for the new sections in My Library Card:
|
reCaptcha Option for Export to Email Action and Give Us Feedback Tool
August 2022 URM-162953
Primo now allows you to add reCaptcha security when using the Export to Email action and providing feedback with the Give Us Feedback Tool.
Configuration Options
reCaptcha is not configured out of the box. Please refer to the following table for configuration details. For more details, see Configuring reCaptcha for Primo VE.
| Configuration Element | Description |
|---|---|
|
Captcha Keys mapping table (Configuration Menu > Discovery > Other > Captcha configuration) |
This new mapping table enables the reCaptcha functionality for the Export to Email action and the Give Us Feedback Tool. To enable reCaptcha in Primo VE:
|
|
Send Email and Sms Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following codes have been added to this code table to customize/translate the labels associated with reCaptcha:
|
Option to Set Secondary Resource Type in Facets and Pre-filters
August 2022 URM-156878
Previously, you could assign only one resource type to a record, which limited the search and facets of resources that fell under multiple categories (such as conference proceedings on ebook, dissertations on audio CD, or collections of archival materials that consist of images, and so forth). With this enhancement, you now have the ability to assign secondary resource types to records to allow these records to be found using facets and search pre-filters. Note that these records will continue to display their main resource type only.
Additional resource types cannot be added to Database and Collection resource types because of the manner in which they are calculated.
Configuration Options
To support this functionality, the new Secondary Resource Type page (Configuration Menu > Discovery > Search Configuration > Secondary Resource Type) enables you to assign an additional resource type to records to allow them to be found with a secondary resource type.
For example, if the following secondary resource type is configured, all records matching its criteria are indexed with the Microform resource type so that they are included for search and facets only. For more details, see Configuring Secondary Resource Types for Primo VE.
For consortia:
-
If secondary resource type rules are set at the IZ level, they are applied to IZ records.
-
If the rules are set in the NZ, they are applied to all NZ records
Support Normalization of Display and Local Fields for Dublin Core
August 2022 URM-100382
With this enhancement, customers can now create DC normalization rules to modify the display and search of Display and Local fields on the Manage Display and Local Fields page (Configuration Menu > Discovery > Display Configuration > Manage display and local fields).
As with MARC normalizations rules, you can configure only the display rules for Display fields, but with Local fields, you can configure both the display and search/facet rules. For more details, see Managing Display and Local Fields for Primo VE.
The syntax that is used for the DC normalization rules is similar to that used for other Display and Local fields. It is recommended that you use the templates provided for the fields as a guide. The following example shows the default rules used to display the Creator field:
rule "prima_display creator- dcterms:creator"
when
DCMI is "dcterms"."creator"
then
create operational."prima_display"."creator" with DCMI."dcterms"."creator"
end
rule "prima_display creator - dc:creator"
when
DCMI is "dc"."creator"
then
create operational."prima_display"."creator" with DCMI."dc"."creator"
end
For more details, see Configuring Normalization Rules for Display and Local Fields.
Support Location Filter in Availability Statement
August 2022 URM-XXXXX
Previously, if locations were filtered in Get It using the Primo View Mapped into Alma Libraries page (Configuration Menu > Discovery > GetIt Configuration > Primo View to Libraries), the filtered locations appeared in the availability statement that displays in the brief display lines on both the Brief Results and Full Display pages. With this enhancement, the availability statement displays the same locations that are visible in Get It (depending on whether the locations are filtered or unfiltered).
If the Unfilter option is selected in Get It, the previously filtered locations appear in the availability statement.
Configuration Options
No additional configuration is necessary. For more details, see Configuring the Location Filter List for Get It.
Support Filtering of Custom Languages in Advanced Search
August 2022 URM-161102
Previously, custom languages were supported only under the Language field of the record's full details and under the Language facet in the results. With this enhancement, you can now configure and filter Advanced Searches by a custom language.
Configuration Options
This functionality requires you to add the language's code to the Advanced Search Languages Labels code table () and to add the language to the Language filter in Advanced Search. For more details, see Configuring Austlang and Custom Languages for Primo VE.
Support Alphabetic Sort of Subjects in Record's Full Details
August 2022 URM-166292
The subjects that display in the record's full details can now be sorted alphabetically by subject. For example:
Configuration Options
This functionality is disabled by default. To enable it, set the new subjects_alphabetical_sort_fullDisplay customer parameter to true on the page (Configuration Menu > Discovery > Other > Customer Settings).
Ability to Include or Exclude Full Text Matches in CDI
August 2022 URM-169490
Previously, the ability to exclude full text matches in CDI defaulted to the following option for new and existing views: Search in FT: Yes (Always). With this enhancement, new and existing views now default to the following option, which does not search full text in CDI: Search in FT: No (Always). For more details regarding these options, see Configuring Search Profiles for Primo VE.
Give Us Feedback Tool (NERS)
May 2022 URM-160206
Primo VE now allows end users to report an issue or provide feedback to the library. Once enabled, end users can perform the following steps to send a letter to the feedback manager at the library:
-
To open the feedback tool, select the feedback icon
, which displays at the bottom right corner of the UI. For mobile devices, select Give Us Feedback after selecting the ellipsis at the top right corner. -
Select the type of issue (subject) that you are reporting. The institution can configure and display a maximum of four issue types.
Select Issue Type - Four Issue Types Displayed -
Specify the following information:
Specify Feedback Details-
Subject – Update the issue type if different from what was entered in the previous step.
-
Problem description – Enter the description of the issue or feedback.
-
Email – Specify your email address to allow the feedback team to get back to you in case more information is needed to resolve the issue or to just let you know that the issue has been received or resolved.
-
-
Select Send to send the feedback. The following message displays if the feedback is successfully sent to the feedback manager.
Feedback Sent Successfully -
To close the tool, select either Close or the X icon. If you want to send another feedback, select Send another feedback.
The feedback email includes the following information if provided: sender's email, description, UI page's URL, browser, and device. For example:
Subject: New feedback received from a Primo user - Report a Broken Link
Hello,
You got a new feedback from Jimmy.Johns@gmail.com.Problem Description: Link is broken in the first record of the search results.
Relevant URL: https://na01.alma.myinst.com/discovery/search?query=any,contains,covid%20therapeutics&tab=Everything&search_scope=MyInst_and_CI&vid=PRIMO_OAP_INST:Alma&lang=en&offset=0
Browser: Google Chrome
Device: DesktopThank you
* Please note we make the best effort to ensure that this message is error and virus free.
If you don't trust the sender of this message do not click on any of the above links, respond to the email, or provide any sensitive information.Sample Feedback from UserThe browser and device information is not included if the user does not provide a return email address in the feedback form.
Analytics - Feedback Tool
To support this functionality, the following actions have been added to the Action Usage subject area:
| Group | Subgroup | Action | Description |
|---|---|---|---|
|
General |
Report a Problem |
Click on Give Us Feedback |
The user opened the feedback tool. |
|
Choose category 1 |
The user selected category 1 (code = default.report.option1). |
||
|
Choose category 2 |
The user selected category 2 (code = default.report.option2). |
||
|
Choose category 3 |
The user selected category 3 (code = default.report.option3). |
||
|
Choose category 4 |
The user selected category 4 (code = default.report.option4). |
||
|
Send feedback |
The user sent a feedback. |
||
|
Send another feedback |
The user selected the Send another feedback option. |
||
|
Close the Give Us Feedback window |
The user closed the feedback tool by either selecting Close or the X icon. |
||
|
Send message was failed due to server error |
The user sent a feedback and received an error message. |
Configuration Options
This feature is not enabled by default. The following table lists the configuration options associated with this functionality. For more details, see Configuring the Feedback Tool for Primo VE.
| Element | Description |
|---|---|
|
Report a problem widget configuration page (Configuration Menu > Discovery > Other > Report a problem widget configuration) |
This new page allows you to activate and configure this functionality at either the institution or view level. |
|
Report a Problem Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
This new code table allows you to customize and translate the labels and error messages associated with the Feedback Tool. |
|
aria Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
This code table includes new codes that allow you to customize and translate the labels and tips that provide accessibility for this functionality. |
|
Alma Letters Configuration (Configuration Menu > General > Letters > Letters Configuration) |
The new Report a Problem Letter letter allows you to customize the format and content of the letter. For more details, see Configuring Alma Letters. |
Ability to Include or Exclude Full Text Matches in CDI
May 2022 URM-163144
Users now have the ability enable/disable searches within full text to increase performance and to provide a more focused results set. When end user selection is enabled for this feature, the Search in Full Text option displays for searches that include the Central Index scope.
-
The user's setting of the Search in Full Text slider is persistent for the entire session and applies for all searches in CDI scopes even if the user signs in after changing this setting. If Primo VE's UI page is refreshed, this slider returns to its default setting.
-
In addition, the Expand My Results option has been changed from a checkbox to a slider.
Analytics - Include/Exclude Full Text Matches
To support this functionality, the following action been added to the Action Usage subject area:
| Group | Subgroup | Action | Description |
|---|---|---|---|
|
Results List |
General |
Search CDI FullText - Activate |
The user enabled searches in full text. |
|
Search CDI FullText - Deactivate |
The user disabled searches in full text. |
||
|
The name of the Expand CDI Results (Checked) action has been changed to Expand My Results - Activate because this action is now initiated with a slider. |
The user has elected to expand results to also include CDI records that do not have full text. |
||
|
The name of the Expand CDI Results (Unchecked) action has been changed to Expand My Results - Deactivate because this action is now initiated with a slider. |
The user has elected to limit results only to CDI records that have full text. |
Configuration Options
By default, this capability is disabled and full text is always checked for matches. The following table describes the configuration options to enable this functionality.
| Element | Description |
|---|---|
|
Define a Custom Search Profile page (Configuration Menu > Discovery > Search Configuration > Search Profiles) |
For search scopes that include the CDI (Central Index), a new option has been added to enable the following options for including/excluding full text matches in CDI records:
For more details, see Configuring Search Profiles for Primo VE. |
|
Results Tile Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following codes have been added to support the customization and translation of labels associated with this feature:
|
|
aria Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following codes have been added to provide accessibility for this functionality:
|
Pickup Locations Sorted for Requests
May 2022 URM-113426
When placing requests, the pickup locations are now sorted alphabetically. If campuses are configured, the list of pickup locations is sorted alphabetically by campus, and under each campus, its associated locations are also sorted alphabetically. If the person requesting the item is associated with a specific campus, that campus appears first in the list, followed by the other campuses in alphabetical order.
Configuration Options
This functionality is disabled by default. To enable this functionality, set the alphabetical_sort_pickup_inst_lib parameter to true in the Discovery Customer Settings mapping table (Configuration Menu > Discovery > Other > Customer Settings).
Display Multiple Links for CDI in Full Display (NERS)
April 2022 URM-155872 URM-165187
Instead of Primo VE displaying a single preferred link from CDI, this enhancement allows users to choose from other options to view full text in the View Online section of the record's full display. When this functionality is enabled and CDI returns multiple linking options to view full text, the Show More link appears under the preferred linking option.
Selecting the Show More option displays additional link options that are grouped in the following order if they exist:
-
Direct links from CDI (excluding open access links) return in the following fields of the PNX:
-
links/linktorsrc field – Only one of these fields is permitted, and if provided, it includes either an IEDL link or a special template.
and/or: -
links/linktorsrcadditional – Multiple occurrences of this field are permitted, and each includes an additional direct link from CDI.These links are sorted by provider, which is returned in the $$G subfield.
-
-
Alma link resolver:
-
OpenURL links from Alma return in the links/openurladditional field, which is limited to a single field.
-
OpenURL related services.
-
-
Open Access links from CDI return in one or more links/linktorsrcadditional fields. Open access records have the $$H subfield set to free_for_read. These links are sorted alphabetically by provider name, which is returned in the $$G subfield.
If the Do not proxy Open Access records option is enabled on the Central Index and Proxy Set-Up page (Configuration Menu > Discovery > Other > Central Index and proxy set-up) and CDI returns multiple links, Primo VE determines whether a link is open access only if the $$H subfield is set to free_for_read.
The following example shows the expanded options with the group headings defined:
Configuration Options
This functionality is disabled by default. For information on how to enable this functionality and configure related settings, see the following table.
| Configuration Page | Description |
|---|---|
|
View Configuration (Configuration Menu > Discovery > Display Configuration > Configure Views) |
When selected, the new Display all links in View Online section option instructs CDI to return all available full text links so that they are selectable in a record's full display. If disabled, CDI returns only the preferred link. |
|
GetIT! Tab1 Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following codes define the labels for showing more or less links at a time:
The following codes allow you to add a section heading for each type of link:
|
|
Aria labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following code are used for accessibility:
|
|
Calculated Availability Text Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
delivery.code.fulltext_multiple – Available Online |
Custom RIS Mapping
April 2022 URM-142134
You can now configure how RIS fields are mapped when users perform any of the following export actions: Export to RIS, BibTeX. and EndNote.
Configuration Options
The new Export Mapping for the RIS, EasyBib, and EndNote Actions mapping table allows you to customize the default mapping used to export records to RIS format. For more details, see Export Mappings for the RIS, EasyBib, and EndNote Actions.
Group Locations by Library in Get It
April 2022 URM-164715
If your institution has many libraries that hold the same item at different locations, you can now group these locations by library in Get It.
Users can then select a library to display all available locations for that library. If a library has only one location, users are directed to that location's items.
Configuration Options
This functionality is disabled by default. Refer to the following table for information on how to enable this functionality and to make other related configurations.
| Configuration Page | Description |
|---|---|
|
Discovery Customer Settings mapping table (Configuration Menu > Discovery > Other > Customer Settings) |
When the new getit_group_by_library parameter is set to true, the available libraries are listed in alphabetical order in Get It if there is more than one available library with holdings. Otherwise, Get It displays all available locations in alphabetical order as it did previously. The default setting is false, which does not group locations by library. This functionality is not supported in the How to Get It and GetIt Other sections. |
|
GetIT! Tab1 Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following new code defines the group label for the list of libraries in Get It:
|
Restricted Search Groups for Other Indexes
April 2022 URM-153282
With this enhancement, you can limit searches of Deep Search and Search Webhook scopes to users that are within the following restrictions: IP address, on campus, restricted, or user group. Users who do not meet these restrictions receive the following message:
Configuration Options
Out of the box, this functionality is disabled. Refer to the following table for configuration information.
| Configuration Page | Description |
|---|---|
|
Define Primo VE Webhook Search Scope page (Configuration Menu > Discovery > Search Configuration > Search Profiles > Other Indexes) |
Edit your Search Webhook index and select the Define allowed users link to open the new Allowed Users page, which allows you to add user restriction rules to the scope. For more details, see Defining Allowed Users for Other Indexes. |
|
Define Primo VE Deep Search Scope page (Configuration Menu > Discovery > Search Configuration > Search Profiles > Other Indexes) |
Edit your Deep Search index and select the Define allowed users link to open the new Allowed Users page, which allows you to add user restriction rules to the scope. For more details, see Defining Allowed Users for Other Indexes. |
|
Error Messages Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following code defines the error message that displays when users do not have access to the index:
|
.
Expand Database Searches to DB Categories (NERS #7199)
March 2022 URM-164387
In the previous release, database searches were expanded to all fields (such as subject and author). With this release, the expanded DB search functionality also allows users to search by DB category name.
Configuration Options
The Expanded DB Search feature was enabled by default for all customers in the previous release, but further configurations are necessary to allow searching by DB category name. The following table lists the configuration settings associated with this functionality. For more details, see Configuring Database Search for Primo VE.
| Element | Description |
|---|---|
|
Discovery Customer Settings mapping table (Configuration Menu > Discovery > Other > Customer Settings) |
The expanded_db_search parameter allows you to enable/disable this feature, which was enabled by default in the previous release. If you prefer searching by title only, set this parameter to false. |
|
Define a Local Field page (Configuration Menu > Discovery > Display Configuration > Manage display and local fields) |
The db_categories field has been added as a new local field, which defines the normalization rule used to index the DB categories for searching. For more information, see Configuration Options for Expanded DB Searches. Re-indexing is required after enabling this local field. Otherwise, only new or modified records will be searchable by DB category. |
Advanced Search - Improved Visibility of Search Results (NERS #7265)
March 2022 URM-164114
After performing an advanced search, the Search Criteria section is collapsed so that search results display more prominently on the page, especially for mobile devices, tablets, and smaller laptops. Users can quickly make changes to their current search by editing fields in the Summary line and then selecting the SEARCH button.
If users would like to make more significant changes to their search query, they can select the Expand icon to display the Search Criteria section as it was displayed previously.
Currently, when switching from simple search to advanced search, the Search Criteria section is collapsed. With the April 2022 release, the Search Criteria section will be expanded after switching to advanced search to allow users to modify their queries more conveniently.
Configuration Options
This functionality is enabled for you. The following table lists configuration associated with this functionality.
| Element | Description |
|---|---|
|
Search Tile Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following code was added for the display label of the Search Criteria section on the Advanced Search page: nui.search-advanced.searchCriteria – Search Criteria |
|
aria Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
To support accessibility, the following code was added for the display label of the Search Criteria section on the Advanced Search page: nui.aria.search.searchCriteria – Search Criteria |
Related Titles - Group by Relation Type and Sort by Title
March 2022 URM-151383
Previously, the containing record displayed the related titles of records that were cataloged with the MARC 76X-78X and 8XX fields. With this enhancement, the related titles are now grouped by relation type (such as Contains) and sorted alphabetically by title under the following fields in the record's details: Related titles, Series, and Is Part Of. For more information on linking records in Alma, see Using the MARC Linking Fields for Related Records.
Specialized Search Scopes for CDI
March 2022 URM-164189
Previously, you could define search scopes that returned all matching collections from CDI. With this enhancement, you have the ability to limit CDI search profiles to specific resource types (such as videos) and/or disciplines (such as visual arts) on the Define a Custom Search Profile page (Configuration Menu > Discovery > Search Configuration > Search Profiles). For more details, see Defining Specialized Search Scopes for CDI.
You can assign a maximum of five resource types and five disciplines for each specialized scope.
Improved CSL Mapping - Differentiate Authors and Creators
March 2022 URM-145989
Previously, there was no distinction made between Author and Contributor names when creating a record's citation. With this enhancement, the Citation export action now includes the role (such as editor or illustrator) if defined in MARC 100 or 700 subfield e so that the contributions of each author/contributor is indicated in the citation.
For example, if the source record has the following authors and contributors:
100 1# $$a Cole, K. C. $$e Translator
700 1# $$a Martin, Debra L., $$e Editor.
700 1# $$a Anderson, Cheryl P., $$e Editor.
Its citation appears as follows in the MLA (8th edition) format:
The following table shows the mapping of the supported role in the source record to its display in the citation.
| Field | MARC21 Field | Citation Role |
|---|---|---|
| Creator |
100 e = Editor or Editor of compilation 100 e = Illustrator 100 e = Interviewer 100 e = Translator 100 e = Director 100 e = Composer |
Editor Illustrator Interviewer Translator Director Composer If none of the above are sent, author/contributor roles do not appear in the citation. |
| Contributor |
700 e = Editor or Editor of compilation 700 e = Illustrator 700 e = Interviewer 700 e = Translator 700 e = Director 700 e = Composer |
Editor Illustrator Interviewer Translator Director Composer If none of the above are sent, author/contributor roles do not appear in the citation. |
Configuration Options
Existing records require re-indexing for this feature to take effect. All new and updated records are re-indexed automatically.
Expand Database Searches to All Data Fields (NERS #7199)
February 2022 URM-159687
Previously, searches performed in Database Search matched only on the title. Searches are now expanded to all fields (such as subject and author). With the next release, the expanded DB search functionality will also allow users to search by category name.
Configuration Options
This functionality is enabled by default for all customers. The following table lists the configuration settings associated with this functionality. For more details, see Configuring Database Search for Primo VE.
| Element | Description |
|---|---|
|
Discovery Customer Settings mapping table (Configuration Menu > Discovery > Other > Customer Settings) |
The expanded_db_search parameter has been added to enable/disable this feature, which is enabled by default. If you prefer searching by title name only, set this parameter to false. |
|
Database Search Labels code table (Configuration Menu > Discovery > Display Configuration > Labels) |
The following code has been added to support the display label that appear in the search box on the Database Search page when the expanded DB Search functionality is enabled: nui.databasesearch.searchbox.expanded – Enter a search term
|
Configure the Message for Duplicate Resource Sharing Requests
February 2022 URM-133648
You can now configure the message that returns when users make a duplicate resource sharing request. To support the customization and translation of the message, the following code has been added to the ViewIt Labels code table (Configuration Menu > Discovery > Display Configuration > Labels):
To enable this functionality, you must set the check_patron_duplicate_borrowing_requests parameter to true in the Customer Parameters mapping table (Configuration Menu > Fulfillment > General > Other Settings).
Linking to Related Records without Specifying a Title
February 2022 URM-150415
When adding linking information for a related record (MARC 76X-78X and 8XX fields), the $$t subfield is no longer required to create related record fields (Related Titles, Is Part Of and Series) in the record's details. Previously for the Related Titles and Is Part Of fields, only the value from the subfield t was used to construct the display link for the related record field. With this enhancement, subfield t is no longer required, and the following conditions now determine the display link for the Related Titles and Is Part Of fields:
-
If subfield t exists, its value is used for the display link.
-
If subfield t does not exist, the values of all other subfields (except for subfields w, x, z) are used for the display link.
-
If a title cannot be constructed from the subfields, the new Link to related record label is used for the display link.
The functionality of linking between records has not changed. Primo VE tries to link users directly to the related record based on the Alma related record relationships, and in case records are not connected in Alma, Primo VE generates a search query for the value in the catalog.
In the following example, the MARC 773 field links a record to its parent record using only the MMS ID of the parent record, and the new label for the link displays:
Configuration Options
To support this functionality:
-
The Series and Relations fields' normalization rules have been updated to handle relations that do not include the $$t subfield.
-
The fulldisplay.constants.linkToRelatedRecord code in the Display Constants Labels code table has been added to customize and translate the label used for records that do not have a configured title. For more information, see Configuring Related Record Services for Primo VE.
-
If you prefer to require the existence of subfield t, change the when condition in your normalization rules to check only for the existence of subfield t instead of the existence of any of the subfields t, x, w, z. For example, in the following rule for series 800 fields, change the highlighted line:
rule "Primo VE - Series 800"
when
MARC."800" has any "t,w,x"
thenTo:
rule "Primo VE - Series 800"
when
MARC."800" has any "t"
then
Support the Indexing of Enhanced Holdings Information
January 2022 URM-70119
In addition to metadata provided in the bibliographic record, Primo VE now supports the indexing of holdings information so that users can search for information that is included in the holdings record. After this feature is configured and your records have been re-indexed, users can perform basic and advanced searches to find records based on holdings information.
Configuration Options
Out of the box, this functionality is not enabled and requires configuration. The following table lists the available configuration options.
| Element | Description |
|---|---|
|
Fulfillment Customer Parameters mapping table (Configuration Menu > Fulfillment > General > Other Settings) |
Set the uresolver_enable_getit_holding_configuration parameter to true to enable the new Holdings Search Configuration mapping table. |
|
(new) Holdings Search Configuration mapping table (Configuration Menu > Discovery > GetIt Configuration > Holdings Search Configuration) |
Add a mapping row for each holdings field that you want to index for searching. Select Add Row and specify the following fields:
Changes to this table require your affected records to be re-indexed. For more details, see Configuring Holdings Search for Primo VE. |
|
Advanced Search Configuration tab on on View Configuration page (Configuration Menu > Discovery > Display Configuration > Configure Views) |
Enable the new holdings_information index under the List of Indexes section if you want to perform advanced searches specifically on holdings information. Regardless of this setting, both advanced and simple searches include this index when all fields (Any or anywhere in the record) are searched. |
Ongoing Accessibility Improvements (January)
January 2022 URM-154312
As part of our continuous effort to comply with Web Content Accessibility Guidelines 2.1 Level AA, we have made the following improvement for this release:
-
The screen reader was not picking up the error message after submitting hold requests that were missing required fields. This has been fixed. To support this functionality, the following code was added to the Request Tab Messages Labels code table:
Code Description nui.mandatory.header Please fill in the following mandatory fields to proceed:
Additional Enhancements
- December 2022 URM-178701 (Added January 11, 2023)
Default Settings for Additional Personal Settings – Institutions can now collectively configure the default settings of the following additional personal settings in My Library Card:-
Allow saving my search history – When enabled, this option enables signed-in users to save their search history between sessions.
-
Allow saving my search history – When enabled, this option enables signed-in users to save their search history between sessions.
Additional Personal Settings Enabled in Primo VEIf this enhancement is not configured and the display of additional personal settings is enabled, the additional settings are enabled by default for all users. All user settings override this new default setting. For example, if a user had previously disabled an additional setting (such as Allow saving my search history), its setting is retained and all other additional personal settings use the default setting (whether it has been changed or not).
To support this functionality, the default_user_search_history_off parameter has been added to the Discovery Customer Settings page (Configuration > Discovery > Other > Customer Settings) to configure the collective default for all additional personal settings. If not configured, the default is false, which enables all additional personal settings unless overridden by a user's setting.
The user's settings are also retained if the display of additional personal settings is disabled with the display_user_settings customer parameter.
-
- December 2022 URM-181651
Link Template for Discovery Import Profiles – When configuring linking templates for Discovery Import Profiles, the number of links returned in the Links section of the record's full details now depends on the number of linking parameters used in the linking template:-
Single linking parameter – This option returns static links that are stored in the specified source field. If the field indicated by the linking parameter is repeated in the source record, Primo VE displays a link for each field. This configuration may look something like the following:
Template Parameter Definitions DC Source Links Section $$LinkingParam1
$$LinkingParam1 = dc:source
<dc:source>https://google.com</dc:source>
<dc:source>https://en.wikipedia.org</dc:source>
Multiple links are created:
- https://google.com
- https://en.wikipedia.org
-
Multiple linking parameters – This option returns a single link that dynamically returns the record based on the specified linking parameters. If the field indicated by a linking parameter is repeated in the source record, only the first occurrence of each is used to create the link in Primo VE. This configuration may look something like the following:
Template Parameter Definitions DC Source Links Section https://test.com/request?creator=$$LinkingParameter2&type=$$LinkingParameter3
$$LinkingParam2 = dc:creator
$$LinkingParam3 = dc:type
<dc:creator>Brown</dc:creator>
<dc:creator>Black</dc:creator
<dc:type>Thesis</dc:type>
A single link is created:
https://test.com/request?creator=Brown&type=Thesis
For more information regarding import profiles, see Configuring Import Profiles for Primo VE.
-
- December 2022 URM-135419 (Updated January 20, 2023)
Improvements to Genre Terms Mapping – The following changes have been made to improve the mapping of the MARC 655 field for display and facets:PNX Field Old Mapping New Mapping display.genre 655 v 655 a display.subjects 655 (all except v) 655 (all except a) facet.genre 655 a no change facet.topic 655 a-z 655 (all except a) search.genre 655 a no change search.subject 655 a-z deleted For more information regarding mapping, see Mapping to the Display, Facets, and Search Sections in the Primo VE Record.
- December 2022 URM-112593
Support LC Name Authority Records for 651 – This enhancement allow users to browse by geographical names to support missing 651 terms from the Browse Search Vocabulary LCSH results.
For more details regarding Browse Search, see Configuring Browse Search. - December 2022 URM-180204
Alphabetical Sort for 'Get it from other institutions' – With this enhancement, the institutions are now sorted alphabetically in the Get it from other institutions section of Get It based on the UI's language. - December 2022 URM-177377
Add Link to Terms of Use in Primo Studio – To ensure that users who develop add-ons for Primo Studio are aware of our Terms of Use policy, a link has been added to the Addons tab in Primo Studio. For more details, see Ex Libris Developer Network and API Terms of Use.
- July 2022 URM-170754 (Added June 28, 2022)
Persistent Expand/Collapse Setting for Search Criteria Section – Previously, after first opening the Advanced Search page or switching from Simple to Advanced Search, the Search Criteria section was always expanded.
Search Criteria Section Expanded on the Advanced Search Page (Search Terms Included)With this enhancement, whether the section is collapsed or expanded is determined as follows:-
Selecting Advanced Search from the Simple Search page (with or without search terms) opens the Advanced Search page with the Search Criteria section expanded.
-
Selecting the Previous browser button to return to the Advanced Search page from any Primo VE page (without search terms) opens the Advanced Search page with the Search Criteria section expanded.
-
Selecting the Previous browser button to return to the Advanced Search page from any Primo VE page (with search terms) opens the Advanced Search page with the Search Criteria section expanded/collapsed based on the user's last setting. The default setting is to expand the section unless the user last collapsed the section. For signed-in users, this setting is saved between sessions.
For example, if the user last collapsed the Search Criteria section in the UI, it appears collapsed if the query includes search terms:
Search Criteria Section Collapsed on the Advanced Search Page (Search Terms Included)Changing the search terms in the Summary line retains the expand/collapse setting of the Search Criteria section after selecting Search.
In addition, the following Usage Actions have been added to support this functionality in Primo VE Analytics:
Group Subgroup Action Description Search Search Advanced search collapsed The user collapsed the search criteria section in Advanced Search. Advanced search expanded The user expanded the search criteria section in Advanced Search. -