Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Primo VE 2022 Release Notes

    Search for what you need
     
    Search:   magnifying-glass-gray.png            Release:  
     
              Showing results for:    Features: | Additional Enhancements: | Resolved Issues:
     

    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.


    Download the PDF for the Release Notes.

    What's New in November?

    To download other formats of the presentation, select the following links: WebEx or PDF.

    February Sneak Preview

    • Support new Exact Type of “Equals” in the Advanced Search (NERS)

    • Add "Starts With" Functionality to the Call Number in the Advanced Search (NERS)

    • Allow users search using item barcode from a new "Barcode Search" section in the Advanced Search (NERS)

    • Better UX for changing number of titles per page (NERS)

    • Improved UNIMARC and CNMARC Mapping 

    • User Settings for Persistent Search History – Continued to allow the institution to determine the default status for the new users' toggles

    Download the PDF for the Release Notes.

    What's New in August?

    To download other formats of the presentation, select the following links: WebEx or PDF.

    Upcoming Issues to Note

    Upgrade to Angular 1.8 in Primo/Primo VE – We plan to upgrade from Angular 1.6.10 to Angular 1.8 in the Primo/Primo VE November 2022 release. This upgrade may impact your Angular customizations in Primo and Primo VE and may require you to adjust the customizations accordingly prior to the upgrade to ensure a smooth migration to Angular 1.8. In advance of the November 2022 release, please carefully review the following documentation/training to ensure that your Angular customizations are ready for the update in November:

    November Sneak Preview

    • Added options to set preferences for Link-in-Record linking for CDI (NERS)

    • Support new Exact Type of “Equals” in the Advanced Search

    • New action - Share 

    • Give Us Feedback Improvements 

    • Collection Discovery usage in Primo Analytics (NERS) 

    • Enrich metadata when exporting to citations for local articles and book chapters

    Upcoming Issues to Note

    Upgrade to Angular 1.8 in Primo/Primo VE – We plan to upgrade from Angular 1.6.10 to Angular 1.8 in the Primo/Primo VE November 2022 release. This upgrade may impact your Angular customizations in Primo and Primo VE and may require you to adjust the customizations accordingly prior to the upgrade to ensure a smooth migration to Angular 1.8.

    In advance of the November 2022 release, please carefully review the following document to ensure that your Angular customizations are ready for the update in November:

    Download the PDF for the Release Notes.

    What's New in May?

    To download other formats of the presentation, select the following links: WebEx or PDF.

    Upcoming Issues to Note

    Upgrade to Angular 1.8 in Primo/Primo VE – We plan to upgrade from Angular 1.6.10 to Angular 1.8 in the Primo/Primo VE November 2022 release. This upgrade may impact your Angular customizations in Primo and Primo VE and may require you to adjust the customizations accordingly prior to the upgrade to ensure a smooth migration to Angular 1.8.

    In advance of the November 2022 release, please carefully review the following document to ensure that your Angular customizations are ready for the update in November:

    Download the PDF for the Release Notes.

    What's New in April?

    To download other formats of the presentation, select the following links: WebEx or PDF.

    Upcoming Issues to Note

    Primo Analytics – The following activity is planned for April:

    • In light of community feedback, we plan to align the action dates reported in Primo VE Analytics to more accurately reflect user actions within a full day, for all time zones. This will resolve cases for time zones in which patron usage may be reported on the previous or next day.

    • Impact to note: After the update, Primo Analytics reports will reflect the data updated two days ago (instead of up to a day ago)—for example, a report that is run on Friday will reflect the data that was reported up to Wednesday.

    • Rollout plan: Canada data center on April 10th; All other data centers on April 24th.

    May Sneak Preview

    • New tool for users to provide library feedback or report an issue (NERS).

    • Ability to expand search to include or exclude full text matches in CDI.

    • Add option to sort pickup locations alphabetically.

    Download the PDF for the Release Notes.

    What's New in March?

    To download other formats of the presentation, select the following links: WebEx or PDF.

    Upcoming Issues to Note

    Primo Analytics – The following activity is planned for April:

    • In light of community feedback, we plan to align the action dates reported in Primo VE Analytics to more accurately reflect user actions within a full day, for all time zones. This will resolve cases for time zones in which patron usage may be reported on the previous or next day.

    • Impact to note: After the update, Primo Analytics reports will reflect the data updated two days ago (instead of up to a day ago)—for example, a report that is run on Friday will reflect the data that was reported up to Wednesday.

    • Rollout plan: Canada data center on April 10th; All other data centers on April 24th.

    April Sneak Preview

    • Enhanced Get It to Support Library Level List

    • Allow Restricted Search for Search Webhook

    • Customize RIS Mapping (Idea Exchange)

    Download the PDF for the Release Notes.

    What's New in February?

    To download other formats of the presentation, select the following links: WebEx or PDF.

    Upcoming Issues to Note

    Primo Analytics – The following activity is planned for April:

    • In light of community feedback, we plan to align the action dates reported in Primo VE Analytics to more accurately reflect user actions within a full day, for all time zones. This will resolve cases for time zones in which patron usage may be reported on the previous or next day.

    • Impact to note: After the update, Primo Analytics reports will reflect the data updated two days ago (instead of up to a day ago)—for example, a report that is run on Friday will reflect the data that was reported up to Wednesday.

    • Rollout plan: Canada data center on April 10th; All other data centers on April 24th.

    CDI Rights processing – Advance notice:

    Our development team is finishing work on reducing the time it takes activations in Alma/SFX to be reflected in CDI. The goal is to process the data within 48 hours. We plan to deploy the necessary changes at the beginning of March and then have a gradual rollout to ensure there are no service disruptions. We will provide additional updates once the rollout has started. No work will be required by you.

    March Sneak Preview

    • Specialized Search Scopes for CDI - Allow the creation of views with search scopes that are restricted to certain disciplines or resource types.

    • Advanced Search – Collapsing the search criteria form (NERS).

    • Expand Database Searches to All Data Fields Continued – Support search by categories (NERS #7199).

    • Display the related records (for example, Related Titles, Series, and Is Part of) sorted by relation type and title.

    Download the PDF for the Release Notes.

    What's New in January?

    To download other formats of the presentation, select the following links: WebEx or PDF.

    February Sneak Preview

    • Enhance the database search to include keyword searching (NERS), and in the March release, it will also include search by categories.

    • Linking to related records without specifying a title.

    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.

    PVE_ShareExportAction2.png

    Share Action Selected

    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:

    • fulldisplay.command.pushto.option.share: Share

    • fulldisplay.command.pushto.option.shareTwitter: Twitter

    • fulldisplay.command.pushto.option.shareFacebook: Facebook

    • fulldisplay.command.pushto.option.shareWhatsApp: WhatsApp

    • fulldisplay.command.pushto.option.shareLinkedIn: LinkedIn

    • fulldisplay.command.pushto.option.shareCopied: Copied

    • fulldisplay.command.pushto.option.shareCopy: Copy

    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:

    1. Support the configuration of whether the following fields are mandatory or optional on the Give Us Feedback form: email address and description.

      PVE_ReportProblemRow_Nov22Parms.png

      Mandatory Configuration Parameters
    2. 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.

      PVE_ReportProblemRow_EmailAddressCategory.png

      Add Email Addresses per Category
    3. 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.

    PVE_GuestSaveFavoritesWarning.png

    Guest Saved Record

    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:

    • nui.favorites.guestSaveMessage – To permanently save your items to favorites, <b>make sure to sign in</b>

    • nui.favorites.guestSaveMessageDismiss – Dismiss

    Provide Direct Linking from Full Record

    November 2022 URM-XXXXX
    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.

    PVE_FullText_DirectLinking.png

    Linking Options in Full Record

    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 2022URM-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.

    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.

    PVE_CDI_Setup_ProviderPreferences.png

    Central Index and Proxy Set-Up Page

    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.

    PVE_PersistentBanner.png

    New Persistent Banner

    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.

    PVE_RR_Configuration_Banner_RT.png

    New Banner Type

    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:

    • results.banner.closeBanner – Close Banner

    Aria Labels code table

    The following codes have been added to support this functionality in screen readers:

    • nui.aria.resRecomm.recommendedRsrc.type.label.banner – {Main Title}: {URL text}

    • nui.aria.resRecomm.recommendedRsrc.type.label.closeBanner – Close Banner

    • nui.aria.resRecomm.recommendedRsrc.type.label.bannerAlert – The library has recommended this resource that may interested you: {Main Title}

    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:

    PVE_PersisteentRecommendation_Librarian.png

    Persistent Suggested Librarian Resource Displayed First

    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.

    PVE_DisplayAlwaysColumn.png

    Display Always Column - Resource Recommender Configuration

    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.

    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:

    1. 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.

      PVE_MyPersonalDetailsSettingsOption_UserAreaMenu.png

      My Personal Details and Settings Option - User Area Menu
    2. 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.

      PVE_MLC_PersonalDetails_and_SettingsTab.png

      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:

    • display_user_settings (new) – Set this field to true to allow users to enable/disable persistent functionality from My Library Card > Personal Details. This functionality is disabled by default.

      This setting also enables the new My Personal details and settings option in the User Area menu.

    • save_users_search_history (existing) – Set this field to true to display the Allow saving my search history option in the Personal details section and to allow signed-in users to save search history between sessions.

    • show_recent_search (existing) – Set this field to true to display the Use my search history for the recent search suggestions option in the Personal details section and to allow a user's search history to be used to provide recent search suggestions.

    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:

    • nui.mypref.label.save_history – Allow saving my search history

    • nui.mypref.label.save_history_suggestions – Use my search history for the recent search suggestions

    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:

    • nui.aria.allowSavingHistory – Allow saving my search history

    • nui.aria.useHistoryForRecent – Use my search history for the recent search suggestions

    • nui.aria.myPersonalDetails – My Personal details and settings

    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:

    • nui.detailsAndSettings.header – Personal details and settings

    • nui.userSettings.header – Personal settings

    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.

    PVE_reCaptcha_Example_GiveUsFeedback.png

    reCaptcha Enabled in 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:

    1. Enter the following URL to register your institution and to create your reCaptcha site and secret keys:

      https://www.google.com/recaptcha/admin/create

    2. Open the Captcha Keys mapping table and type the associated key in the following fields: reCaptcha Site key and reCaptcha Secret key.

    3. Save your changes

    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:

    • captcha.notselected – *Please Type CAPTCHA Again

    • captcha.invalidSiteKey – *reCaptcha Site key is invalid - please check the configuration

    • captcha.publickey – *Public Key Configuration Is Misssing

    • captcha.privatekey – *Private Key Configuration Is Misssing

    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.

    PVE_SecondaryResourceType_Example1.png

    List of Configured Secondary Resource Types

    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.

    PVE_EditSecondaryResourceType_Example1.png

    Edit Secondary Resource Type Page

    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).

    PVE_DefineLocalField_DC.png

    Define a Display Field Page

    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
     

    Defaults DC Rules for Creator Field

    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).

    PVE_FilteredStatement.png

    Filtered Availability Statement

    If the Unfilter option is selected in Get It, the previously filtered locations appear in the availability statement.

    PVE_UnfilteredStatement.png

    Unfiltered 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.

    PVE_AdvSearch_SupportCustomLang.png

    Advanced Search Page - Language Filter

    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:

    PVE_SubjectSort_Comparison.png

    Subject Sort Comparison

    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:

    1. To open the feedback tool, select the feedback icon PVE_Feedback_icon1.png, 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.

    2. Select the type of issue (subject) that you are reporting. The institution can configure and display a maximum of four issue types.

      Image1.png

      Select Issue Type - Four Issue Types Displayed
    3. Specify the following information:

      PVE_Feedback_Screen2.png

      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.

    4. Select Send to send the feedback. The following message displays if the feedback is successfully sent to the feedback manager.

      PVE_Feedback_Screen3.png

      Feedback Sent Successfully
    5. 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: Desktop 

       

      Thank 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 User

      The 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.

    PVE_Opt-In_Example.png

    Full Text Match and User Override Enabled

     

    • 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:

    • Search in FT: Yes (Always) – Searches always check full text for matches in CDI records and there is no end user option to disable it. This is the default option.

    • Search in FT: Yes (End-user selection) – Searches always check full text for matches in CDI records, but end users have an option to disable it.

    • Search in FT: No (Always) – Searches never check full text for matches in CDI records and there is no end user option to enable it.

    • Search in FT: No (End-user selection) – Searches never check full text for matches in CDI records, but end users have an option to enable it.

    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:

    • nui.expandresults.tooltip.active – Deactivate Expand My Results

    • nui.expandresults.tooltip.inactive – Activate Expand My Results

    • nui.cdiFTsearch – Search in Full Text

    • nui.cdiFTsearch.tooltip.active – Deactivate Search in Full Text 

    • nui.cdiFTsearch.tooltip.inactive – Activate Search in Full Text 

    aria Labels code table (Configuration Menu > Discovery > Display Configuration > Labels)

    The following codes have been added to provide accessibility for this functionality:

    • nui.aria.expandresults.active – Deactivate expand my results

    • nui.aria.expandresults.inactive – Activate expand my results

    • nui.aria.cdiFTsearch.active – Deactivate search in full text

    • nui.aria.cdiFTsearch.inactive – Activate search in full text 

    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.

    PVE_Sorted_PickUpList.png

    Locations Sorted Alphabetically by Campus

    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).

    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.

    PVE_MultiLinkEnabled1_ShowMore.png

    Multiple Links Collapsed in View Online - No Link to Resource Link from CDI

    Selecting the Show More option displays additional link options that are grouped in the following order if they exist:

    1. Direct links from CDI (excluding open access links) return in the following fields of the PNX:

      1. 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:

      2. 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.

    2. Alma link resolver:

      1. OpenURL links from Alma return in the links/openurladditional field, which is limited to a single field.

      2. OpenURL related services.

    3. 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:

    PVE_MultiLinkEnabled1_Expanded.png

    Multiple Links Expanded in View Online - No Related Services

    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:

    • nui.getit_full.multiple_showmore – Show more
    • nui.getit_full.multiple_showless – Show less

    The following codes allow you to add a section heading for each type of link:

    • nui.getit_full.multiple_linktorscr_subsc – <blank>
    • nui.getit_full.multiple_linkresolver – <blank>
    • nui.getit_full.multiple_linktorscr_oa – <blank>

    Aria labels code table (Configuration Menu > Discovery > Display Configuration > Labels)

    The following code are used for accessibility:

    • nui.aria.fulldisplay.multiple.showmore – Show more links
    • nui.aria.fulldisplay.multiple.showless – Show less links

    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.

    PVE_ExportActions2.png

    RIS Format Export Actions

    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.

    PVE_Export_To_RIS_MT.png

    Export Mapping for the RIS, EasyBib, and EndNote Actions Mapping Table

    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.

    PVE_GetIt_LocationsGroupedByLibrary.png

    List of All Libraries 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.

    PVE_GetIt_ListOfLibraryLocations.png

    List of a Library's Locations in Get It

    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:

    • nui.locations.headerLibraries – Libraries

    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:

    You must be signed-in or on campus to search in this resource.

    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:

    • nui.search.tnsearch.error.authorization – You must be signed-in or on campus to search in this resource.

    .

    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.

    PVE_DB_Cat_Search1.png

    Expanded DB Search - Support DB Categories

    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.

    PVE_SearchCriteria_Collapsed.png

    Collapsed Search Criteria Section on Advanced Search Results Page

    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. 

    PVE_SearchCriteria_Expanded.png

    Search Criteria Section Expanded 

    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

    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 titlesSeries, and Is Part Of. For more information on linking records in Alma, see Using the MARC Linking Fields for Related Records.

    PVE_SortedRelations.png

    Related Titles Grouped by Relation Type and Sorted

    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.

    PVE_CDI_SearchProfiles_SelectiveOptions.png

    Selective Resource Types and Disciplines Configuration

    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 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:

    PVE_CitationRoleExample.png

    Example Citation in 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.

    PVE_ExpandedDB_Search.png

    Expanded Database Search

    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):

    c.uresolver.request.ill.patron_has_duplicate_request – Patron already has a similar borrowing request, please contact the library.

    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). 

    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:

    1. If subfield t exists, its value is used for the display link.

    2. If subfield t does not exist, the values of all other subfields (except for subfields w, x, z) are used for the display link.

    3. 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:

    773 #0 $$w 991546060000541

    PVE_773_Linking_No_Title_Example2.png

    Related Record with No Configured Title

    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"
                      then

      To:

      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.

    Search Holdings Information Index in Advanced Search

    New Holdings Information in Advanced Search

    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:

    • Holdings Field – Specify the holdings field that you want to index.

    • Holdings Subfield – Specify a comma-separated list of subfields that you want to index. You must specify at least one subfield.

    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-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
      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 no change

      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.

      PVE_BrowseSearch_LC_Name_651.png

      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.

      PVE_PrimoStudio_TermsofUseLink.png
    • November 2022 URM-159125
      Allow all publication dates to be indexed – All publication dates are now indexed from MARC fields 264 $c and 264 $c for simple search, but they cannot be searched or sorted as publication dates and do not have facets.

      This change will go into effect when the Primo VE semi-annual indexing is completed in January.

    • November 2022 URM-144433
      Display Volume, Issue, and Pages in Citations – For local records, host enumerations (volume, issue, and pages) that are included in the MARC 773 $g subfield are now included in the respective PNX fields (addata/volume, addata/issue, addata/spage and addata/epage) and displayed in citations via export actions. Note that this functionality is already supported for CDI records.

      This change will go into effect when the semi-annual indexing of the Repository is completed in December.

      To support this functionality, the MARC 773 $g subfield must be formatted as follows for local records:

      • Extract Year, Volume, Issue information to include in the PNX addata/date, addata/volume, and addata/issue fields:

        Format - $773 starts with: Description Example

        DDD(DDDD)DD

        <volume - minimum of 1 and maximum of 3 digits> (<Year in 4 digit format>) <issue - minimum of 1 and maximum of 3 digits>

         

        An article published in 2005, volume 3 issue 1 should be included in the 773 $g as the following: 3(2005)1

        DDD(YYYY)

        <volume - minimum of 1 and maximum of 3 digits> (<Year in 4 digit format>)

        An article published in 2005, volume 3 should be included in the 773 $g as the following: 3(2005)

      • Extract page information (start/end pages and total number of pages) to include in the PNX addata/spage, addata/epage, addata/tpages fields:

        Format – 773 $g includes: Description Example

        p.DDD-DDD or p. DDD-DDD

         

        p. <startpage in minimum of 1 and maximum of 3 digits>-<endpage in minimum of 1 and maximum of 3 digits>

         

        An article published with start page 1 and end page 26 should be included in the 773 $g as the following: p. 1-26 or p.1-26

         

        pp.DDD or pp. DDD

        pp.<total number of pages in in minimum of 1 and maximum of 3 digits>

        A book published with total number of pages of 360 should be included in the 773 $g the following: pp.360 or pp.360

        then DDD becomes addata/tpages

         

      • DD indicates 1 to 2 issues.
      • DDD indicates 1 to 3 pages or volumes.
      • DDDD indicates a 4-digit year.
    • November 2022 PRM-46313
      Upgrade to Angular 1.8 in Primo/Primo VE – This upgrade may impact your Angular customizations in Primo and Primo VE and may require you to adjust the customizations accordingly prior to the upgrade to ensure a smooth migration to Angular 1.8. In advance of this release, please carefully review the following document to ensure that your Angular customizations are ready for the Angular update:
    • September 2022 URM-172205
      Tracking Number of Indexed Titles for Primo VE – The new Primo Discovery subject area allows you to track the number of titles indexed for Primo VE. For more details, see Primo Discovery.
    • September 2022 URM-156092
      Disable Proxy for OA Links Provided by CDI – With this enhancement, Open Access is now handled at the link level instead of the record level for links returned from CDI. This allows Primo VE to disable the proxy for all links returned by CDI based on the Open Access indicator provided per link in the PNX Links section:

      <links>

      # Regular Link in Record Links:

      <linktorsc>$$U<link>$$G<Provider>$$Hfree_for_read</linktorsc>

       

      # All Links:
      <linktorsradditional>$$U<link>$$G<Provider>$$Hfree_for_read</linktorsradditional>

       

      # QuickLinks:
      <linktohtml>$$U<link>$$G<Provider>$$Hfree_for_read</linktohtml>

      <linktopdf>$$U<link>$$G<Provider>$$Hfree_for_read</linktopdf>
      </links>

      If the $$H field contains the free_for_read indication, the collection is considered Open Access, and depending on the Proxy settings in Primo VE, the proxy is added to the URL. For more details, see Configuring Central Index and Proxy Settings for Primo VE.

      Examples:

      <linktorscr>$$Uhttps://www.doaj.org/ABC/123.pdf$$EPDF$$P1$$GDOAJ$$Hfree_for_read</linktorscr>

       

      <linktorscradditional>$$Uhttps://www.doaj.org/ABC/123.pdf$$EPDF$$P1$$GDOAJ$$Hfree_for_read</linktorscradditional>

       

      <linktohtml>$$Uhttps://www.proquest.com/docview/1882579091$$EHTML$$P50$$Gproquest$$Hfree_for_read</linktohtml>

       

      <linktopdf>$$Uhttps://www.sciencedirect.com/science/article/pii/S0735109716008226?via%3Dihub$$GElsevier$$Hfree_for_read</linktopdf>

    • August 2022 PRM-46601 (Added September 14, 2022)
      The following actions have been added to the Action Usage subject area in Primo VE Analytics to support the display of all links from CDI in View It:
      Group Subgroup Action Description

      Document

      Link

      Additional openURL

      Additional Link to source

       

      The user selected an additional link in the View It section of the record's full display.

      When a user selects a link in View It, these actions can occur only if the Display all links from CDI capability is enabled, multiple links are returned from CDI, and the user has first selected Show More.

      For additional information, see Display All Links in Full Display for CDI.

    • August 2022 URM-171605
      Primo VE now supports out-of-the-box translations for Ukrainian.
    • August 2022 URM-128817
      Primo VE now maps the MARC 260 $a and 264 $a fields to the General search field.
    • August 2022 URM-149372
      The Access Model in Primo VE now supports HTML in the record's full display.
    • 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.

      PVE_SearchCriteria_Expanded.png

      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:

        PVE_SearchCriteria_Collapsed.png

        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.
    • May 2022 URM-165387 SF: 06324288, 06279453, 06275719, 06279698, 06277395, 06287546, 06291515, 06323429, 06306372, 06300661, 06279131, 06283928, 06284253
      Remove Links to Related Titles with No Records – Prior to the April release, MARC 776 fields did not create related title entries in a record's details if they did not have the $$t subfield configured. With this enhancement, related title fields are now removed from a record's details if no $$t is specified and there is no matching relation. If there is a $$t and no matching relation, the link returns an advanced search for the value of $$t.
    • May 2022 URM-155041
      Updated Synonym File for German – The following entry has been added to the German synonym file:
        studiomusiker=sessionmusiker(normal)
    • May 2022 URM-98230
      Updated Mapping for Images Resource Type – The mapping for the images resource type has changed from:
           Leader(06) = k AND 008(33) = i|k|l|n|s|t
      To: 
           Leader(06) = k AND 008(33) = a,c,i,k,l,n,o,s,t
    • April 2022 URM-160148
      Improved FRBR Key Combinations – Added the K4 FRBR key to prevent titles in different languages from being merged. For more details, see Understanding the Dedup and FRBR Processes (Primo VE).
      Key Content MARC 21 Field DC Field UNIMARC Field

      K4

      Language

      041 a, d, e

      008 35-37

      dc.language

      dcterms.language

      101 a

    • April 2022 URM-166178
      Enrich Author Facet with Preferred Terms from Authority (Multiple Languages) – Previously, the values for the Author were enriched from the Authority records using all subfields. With this enhancement, the enriched term for author uses only subfield $a, which is the same as is displayed in the Author facets for creator in the bibliographic record. This helps reduce multiple occurrences of the same creator in Author facets after enrichment from Authority records.
    • April 2022 URM-156681
      Add Provider IDs to Primo VE OpenURL for Leganto – Provider IDs that were added to the CDI record and the Alma OpenURLs are now included in the Leganto OpenURL so that they can be used for linking.
    • April 2022 URM-166609
      Switching from Simple Search to Advanced Search – With the addition of the collapsible search box in Advanced Search, the search box is now expanded when switching from Simple Search to Advanced Search when a query exists in Simple Search. This allows users to quickly make changes to their queries after the switch.
    • February 2022 PRM-45815
      Support the Display of Long Facet Names – As was done for long facet values, facets with long display names now wraparound to the next line instead of being truncated on a single line.
    • February 2022 PRM-45819
      Track Sort by Date in Analytics – With this enhancement, the following actions are now supported in Primo VE Analytics:
      Group Subgroup Action Description
      Results List Sort Sort by date-newest User sorted results by newest date.
      Sort by date-oldest Users sorted results by oldest date.

      With the February release, the old actions are no longer available, and the new actions will start to appear in your reports on February 20.

    • January 2022 URM-161845
      Limit Search/Facets of Local Extensions to Local Institution – Previously, local extensions for UNIMARC fields 6X9, 69X, and 9XX and for CNMARC fields 9XX (for 905 only subfields d,e,f,s) were searchable via search and facets from any institution in a consortium. With this enhancement, these local extensions are now limited to the local institution only.
    • January 2022 URM-161859
      Primo VE to Primo VE - Allow Searching in Remote Institutions from Other Instances – When configuring your institution to search other Primo VE institutions, the remote institution is no longer limited to the same instance.
    • January 2022 URM-155594
      Annual upgrade of Melingo – For Israeli customers only, upgraded Melingo, which is the Hebrew search plug-in. This change will go into effect when the semi-annual indexing has completed in January.
    • January 2022 URM-136800
      Remove Publishing Job for Primo Central – With the switch to CDI, the Publish electronic records to Primo Central publishing profile has been removed.
    • January 2022 URM-121616
      Hide Course Information for Unpublished Reading Lists – When a Reading List is unpublished in Leganto, the associated course information is now hidden from the Details and More from the Same sections in the record's full display. In addition, course information that is associated with an unpublished reading list will not be searchable in Primo VE after re-indexing. For more information, see Configuring the Course Information Field in the Details Service.

    Resolved Issues

    • December 2022 PRM-42789 SF: 05331669 (Added November 21, 2022)
      HTML 5 regions did not have meaningful names for accessibility and could not be customized in the Aria Labels code table. This has been fixed by adding the following codes:
      Code Description
      nui.aria.navigationRegionPagination Pagination Region
      nui.aria.navigationRegionMainMenu Main Menu Region
      nui.aria.navigationRegionFullView Full View Region
      nui.aria.navigationRegionTopBar Top Bar Region
      nui.aria.navigationRegionFacets Facets Region
      nui.aria.navigationRegionDBSearch DB Search Region
      nui.aria.navigationRegionSearchBar Search Bar Region
      nui.aria.navigationRegionCitationLinker Citation Linker Region
      nui.aria.navigationRegionAZSearch AZ Search Bar Region
      nui.aria.navigationRegionNewspaperSearch Newspaper Search Bar Region
      nui.aria.navigationRegionBrowseSearch Browse Search Bar Region
      nui.aria.navigationRegionTagsSearch Tags Search Bar Region
      nui.aria.navigationRegionSearchResults Search Results Region
      nui.aria.navigationRegionAccountOverview Account Overview Region
      nui.aria.navigationRegionOrgListCategorize Organization List Region
    • December 2022 URM-124051 SF: 6407362, 5331749, 5326800, 5323330, 5314860, 5310663, 5307518
      The item.serviceNotAvailable code could not not be translated. This has been fixed.
    • December 2022 URM-153356 SF: 5300515, 6028185
      Facet value was indexed unnormalized in Solr (with capital letter). This has been fixed.
    • December 2022 URM-161036 SF: 6401968, 6400934, 6297930, 6056221, 5325771, 5312527, 5303962, 5303255
      PNX addata/oclcid contained non-oclc numbers. This has been fixed.
    • December 2022 URM-169311 SF: 6249954
      Local field labels were displayed as codes in Print action in Primo VE. This has been fixed.
    • December 2022 URM-170971 SF: 5299806
      Breaking dedup between members of Discovery Network was not possible. This has been fixed.
    • December 2022 URM-173475 SF: 5303353, 6485397
      Items in a temporary location were not displayed on Get It on Services page. This has been fixed.
    • December 2022 URM-175082 SF: 6307910, 6409912, 6461572
      Emails for export records from My Account Loans (current or historical) failed. This has been fixed.
    • December 2022 URM-176739 SF: 6286366
      Missing Discovery label for nui.favorites.fetchingItems. This has been fixed.
    • December 2022 URM-177986 SF: 6464509, 6466482, 6482825, 6518489
      The code label nui.eshelf.menu.userSettings was missing from the User Tile Labels code table. This has been fixed.
    • December 2022 URM-178811 SF: 6473484
      After changing tab in the search bar, the following error was returned: Angularjs error - Cannot read properties of undefined. This has been fixed.
    • December 2022 URM-178872 SF: 6452071
      Unable to change the order of the top-level facets through CSS. This has been fixed.
    • December 2022 URM-180150 SF: 6505280
      Unexpected tag AlmaDFullText was visible on the User Tags page. This has been fixed.
    • November 2022 PRM-46989 PRM-46884 SF: 06055632 (Added November 14, 2022)
      Searches including the Arabic Farsi letter Yeh returned inconsistent results if it included diacritics. To resolve this issue, the characters U+0626, U+06CC, and U+0649 are now normalized to character U+064A.
    • November 2022 PRM-46855 SF: 6460181
      For Hebrew the Get It arrow was pointing in the wrong direction to get back to the list of locations. This has been fixed.
    • November 2022 PRM-46854 SF: 6460607
      Public note direction was displayed incorrectly. This has been fixed.
    • November 2022 PRM-46848 SF: 6449210
      When no URL was defined, the Resource Recommender banner was clickable. This has been fixed.
    • November 2022 PRM-46814 SF: 5328398
      For mobile devices, the 'Sent to' menu was covered by the search menu. This has been fixed.
    • November 2022 PRM-46795 SF: 6408813
      The Report a problem widget could not be customized. For more details, see Give Us Feedback Improvements. This has been fixed.
    • November 2022 PRM-46677 SF: 6316942
      The Collection name was truncated in the "More from same collection" section. This has been fixed.
    • November 2022 PRM-46654 SF: 6370233
      For guest users, the Analytics beacon was fired for the "Send to Leganto" action. This has been fixed.
    • November 2022 PRM-46546 SF: 6342301
      For mobile devices, the container for Advanced Search was not fully flexible. This has been fixed.
    • November 2022 PRM-46545 SF: 6333795
      For mobile devices, the Advanced search UI placeholder was broken. This has been fixed.
    • November 2022 PRM-46154 SF: 5329810
      An incorrect aria label displayed for next page arrow (link) in the pagination region. This has been fixed.
    • November 2022 URM-177811 SF: 6460514
      Different behavior between exclude and select > exclude > apply. This has been fixed.
    • November 2022 URM-177779 SF: 6441153
      searchInFulltextUserSelection did not work in the Primo VE Search API. This has been fixed.
    • November 2022 URM-176731 SF: 6436395, 6445352, 6490544
      Thumbnails for external records could be either from Google/Syndetics or customer's own but not both. This has been fixed.
    • November 2022 URM-175592 SF: 6295123
      Bound with label was not displayed in Location items, only in Location. This has been fixed.
    • November 2022 URM-175168 SF: 6321739
      Service page did not return network portfolios, which was affecting IP recognition. This has been fixed.
    • November 2022 URM-174559 SF: 6395426
      Resource Configuration was not importing URL from Excel sheet. This has been fixed.
    • November 2022 URM-170157 SF: 6246649
      Expired users were able to log on to Primo VE via LDAP. This has been fixed.
    • November 2022 URM-165915 SF: 5323802, 6239509
      Item level Public Note not compatible with HTML script. This has been fixed.
    • November 2022 URM-160866 SF: 5324912, 5326481
      In View Online links to CREDO records were broken. This has been fixed.
    • November 2022 URM-155893 SF: 5322384, 6233124
      The display_856_in_the_holdings_as_viewit parameter worked only if the record was part of a collection. This has been fixed.
    • November 2022 URM-146399 SF: 5307382, 6222054, 6408403, 6425708
      The permalinks redirect failed when using MMS ID instead of IE ID. This has been fixed.
    • September 2022 PRM-46622 SF: 05301434, 05301803
      Aural indicators were missing from the Resource Sharing Request form. This has been fixed.
    • September 2022 PRM-46275 SF: 05329876, 06291125
      In the search results, page number and count results were not read separately in JAWS. This has been fixed.
    • September 2022 PRM-46154 SF: 05329810
      The incorrect aria label was read for the next page link at the bottom of the search results. This has been fixed.
    • September 2022 PRM-46036 SF: 05329396
      The aria-labels of Navigation link buttons were not translated correctly via permalinks. This has been fixed.
    • September 2022 PRM-45621 SF: 05319689, 05804787, 06290907, 06398429
      Local display field did not include some content enclosed in angle brackets in the source record. This has been fixed.
    • September 2022 PRM-45505 SF: 05322383, 06281603, 06434614
      Fields surrounded by angle brackets <> were not presented in the full display. This has been fixed.
    • September 2022 PRM-46850 SF: 06457050, 06458996, 06464440, 06467066
      User settings for Persistent Search History were not working as expected. This has been fixed.
    • September 2022 PRM-45669 SF: 05302631
      The Sort items by relevance measure was incorrectly counted for Primo VE Analytics. This has been fixed.
    • September 2022 URM-176954 SF: 6385379
      GES was not displaying in some cases. This has been fixed.
    • September 2022 URM-176265 SF: 6423608
      Getit was overwritten with shared digital objects and items were not displayed. This has been fixed.
    • September 2022 URM-176041 SF: 6410190
      Filter for volumes displayed wrong description coming from other tables. This has been fixed.
    • September 2022 URM-175213 SF: 6054573, 6300999, 6306259
      Proxy was not applied to Quicklinks as expected. This has been fixed.
    • September 2022 URM-175208 SF: 6416530
      Unable to export more than 10 Alma records to EndNote. This has been fixed.
    • September 2022 URM-173282 SF: 6385024
      Display issue when selecting certain entries from the GetIt library-level list. This has been fixed.
    • September 2022 URM-172067 SF: 6260521
      Invalid library logo URL path generated in 'logo_path' field of XML for Saved Search letter prevents logo image from being loaded in Gmail. This has been fixed.
    • September 2022 URM-171515 SF: 5304508
      In the Brief and full display, the contributor name was doubled in the creator field. This has been fixed.
    • September 2022 URM-170110 SF: 6321654
      Collection Title sort was case sensitive. This has been fixed.
    • September 2022 URM-170094 SF: 6320560
      Source Field in Blank Form Pre-Populated by Default. This has been fixed.
    • September 2022 URM-168963 SF: 6286366, 6287576, 6289557
      Empty export email when selecting all records by favorite label. This has been fixed.
    • September 2022 URM-168030 SF: 6270307
      View It for external+network dedup record show services only from external. This has been fixed.
    • September 2022 URM-167105 SF: 6262999
      Collection disappears after setting sort by title. This has been fixed.
    • September 2022 URM-165647 SF: 6036778
      Special characters were not sorted alphabetically as expected. This has been fixed.
    • September 2022 URM-162087 SF: 5306127
      The Customized Languages Codes table had incorrect data. This has been fixed.
    • September 2022 URM-137844 SF: 5299301, 5311941, 5318114, 5326277, 6453132
      The Discovery Import Profile "Template" generated one link instead of multiple links. This has been fixed.
    • August 2022 URM-176954 SF: 06385379 (Added August 2, 2022)
      General electronic services were not displayed for records. This has been fixed.
    • August 2022 PRM-46554 SF: 06282871
      It was not possible to set distinct placeholder text labels for start/end year fields. The use of one label caused confusion for visually impaired users. This has been fixed.
    • August 2022 PRM-45630 SF: 05319118
      No oral announcement provided for dynamically changed content for Item Display in the Get It section. This has been fixed.
    • August 2022 PRM-39766 SF: 06390360, 05587616, 05313267, 05312236, 05300667, 05299529
      Cannot open Virtual Browse item when opening a full view from My Favorites. This has been fixed.
    • August 2022 PRM-46752 SF: 06388918
      In some cases, the following console error appeared: Possibly unhandled rejection: canceled. This has been fixed.
    • August 2022 PRM-42702 SF: 06434586
      Beginning with the May 2020 release, for narrow screen widths (such as with mobile devices), citation trail icons appear only in the record's full display and not in the brief results.
    • August 2022 URM-174704 SF: 6305630, 6404667
      IZ shared digital resources were not displaying in NZ Union View & other IZ views. This has been fixed.
    • August 2022 URM-172578 SF: 6370972
      The digital inventory of suppressed record still appeared in the dedup group with Alma-E and Alma-P. This has been fixed.
    • August 2022 URM-170065 SF: 6287084, 6334886
      Quicklinks were not proxied in results of Newspaper Search. This has been fixed.
    • August 2022 URM-170040 SF: 6315839
      Unable to change order of search profiles for Search Profile slot on second page. This has been fixed.
    • August 2022 URM-169615 SF: 6237572
      In Blank ILL form, the fields Preferred Pickup Location and Preferred Local Pickup Location were not appearing as mandatory. This has been fixed.
    • August 2022 URM-169159 SF: 6292005
      After changing the UI language, two language parameters in calls caused a discrepancy between UI and selected language. This has been fixed.
    • August 2022 URM-168896 SF: 6220188, 6271874
      The language parameter in the URL ("lang") was not changing after sign-in. This has been fixed to use the user's default language.
    • August 2022 URM-167955 SF: 5305017
      Check Availability calendar was different between Alma's Get it and Primo VE. This has been fixed.
    • August 2022 URM-167480 SF: 5324963, 6377420
      Inconsistent formatting in Locations and Location items. This has been fixed.
    • August 2022 URM-167303 SF: 5322973, 6051114, 6344364
      Clarification was provided for the use of HTML in display labels. For details, see Codes that Support HTML Formatting.
    • August 2022 URM-166285 SF: 6051856, 6213501, 6268749, 6346659
      For certain UNIMARC records, addata/aufirst and addata/aulast were not created correctly, causing wrong citation format. This has been fixed by including 7XX a, b subfields in the mapping rules.
    • August 2022 URM-165917 SF: 6046919
      Unrelated subfield was added to thumbnail link. This has been fixed.
    • August 2022 URM-165327 SF: 6226824
      The Print action wasn't able to translate the "unavailable" availability status. This has been fixed and will use the following code: delivery.code.unavailable label.
    • August 2022 URM-162953 SF: 5323073, 6437494, 6443113
      Add configuration for Captcha option to protect from SPAM Mail for both email and report a problem. See reCaptcha Option for Export to Email Action and Give Us Feedback Tool.
    • August 2022 URM-161102 SF: 5301193, 6338608
      Support Custom language in the Advanced Search Language filter. See Support Filtering of Custom Languages in Advanced Search.
    • August 2022 URM-160698 SF: 5323049, 6023865
      (NERS 7402) Display Collection Discovery for specific libraries / institutions. See Display Collection Discovery for Specific Libraries / Institutions.
    • August 2022 URM-149372 SF: 5333078
      Public Access Model didn't support HTML. See Additional Enhancements.
    • August 2022 URM-145572 SF: 5299770, 5324739, 5332762, 6278621, 6349808
      The New records from last month facet did not include new records from last week. This has been fixed by including new records from last month and last week.
    • August 2022 URM-128817 SF: 5328439
      Added two drools to the marc2opr for the General search field. See Additional Enhancements.
    • August 2022 URM-100382 SF: 6043491
      Allow normalizing metadata fields for search and Display - DC. See Support Normalization of Display and Local Fields for Dublin Core.
    • August 2022 URM-171268 SF: 06325877, 06362038, 06368862
      In My Library Card, the language parameter in the URL ("lang") was not changed after selecting new interface language. This has been fixed.
    • July 2022 PRM-45613 SF: 05303477 (Added June 28, 2022)
      Previously, The logo had both an aria-label and alt-text, which was interpreted as two different links. This has been fixed by hiding the aria-label.
    • July 2022 URM-174825 SF: 06413514 (Added June 22, 2022)
      Missing Search Profiles and Scopes on Search Profiles page, and in some cases, they could not be re-installed. This has been fixed.
    • July 2022 PRM-46554 SF: 06282871
      Visually impaired users were unable to determine whether the Year field represented the start or end year in Advanced Search. To resolve this issue, the code advanced.DateRange.label.Year has been replaced with the following codes to help distinguish between start and end dates:
           - search-advanced.DateRange.label.start_Year = ’Start Year’
           - search-advanced.DateRange.label.end_Year = ’End Year’
    • July 2022 PRM-46484 SF: 06391386, 06372375, 06352191, 06314125, 06311529, 06311473, 06302738, 06301378
      The summary line in Advanced Search disappeared after typing the backspace key to remove all characters to perform another search. To resolve this issue:
           - The summary line in Advanced Search is now visible even when there is no query.
           - An underline is presented when there is no query to indicate that this is a placeholder for text.
           - The height of parameters and query text in the summary line has been aligned.
    • July 2022 PRM-45625 SF: 05303569
      The aria label for the Cancel Request button was missing on the My Library Card > Requests page. This has been fixed by adding the following code to the Aria Labels code table:
           - nui.aria.request.cancel = Cancel request
    • July 2022 PRM-43742 SF: 06329306, 05330241, 05330224, 05330119, 05329948, 05319177, 05311515
      The URL loses persistence parameter after locking the facets and performing another search. This has been fixed.
    • July 2022 PRM-46056 SF: 06036176
      Incorrect Hebrew tool tip displayed for Remove search term in Collection Discovery. This has been fixed.
    • July 2022 PRM-45634 SF: 05320616, 05324177, 06263121
      When using a screen reader, the Send To actions bar that is next to each result was not being read. This has been fixed.
    • July 2022 PRM-45473 SF: 05300684
      While using a screen reader, there was no aural announcement that the content had changed when changing institutions in My Account. This has been fixed.
    • July 2022 PRM-38839 SF: 05315276
      Sorting was not correct after changing tabs in My Library Card. This has been fixed.
    • July 2022 URM-170782 SF: 6333736
      License information is not displayed in View It in some cases. This has been fixed.
    • July 2022 URM-170521 SF: 6321079
      An error message was returned when accessing the Resource Sharing Restriction Rules page. This has been fixed.
    • July 2022 URM-169515 SF: 6291614, 6315152, 6344236
      Specialized Search Scopes for CDI was not working correctly - changing between two CDI scopes did not generate a new search call to CDI. This has been fixed.
    • July 2022 URM-168900 SF: 6372184, 6341037, 6339388, 6337577, 6327947, 6307910, 6298112, 6294882
      Export to Excel from My Account did not return any data. This has been fixed.
    • July 2022 URM-163831 SF: 6048836
      Descriptions of suppressed items displayed in the item filter. This has been fixed.
    • July 2022 URM-156825 SF: 5302161, 6272790
      The View the collection link opened the full record instead of the collection when Direct Linking was enabled. This has been fixed.
    • July 2022 URM-156079 SF: 5319054
      The incorrect date displayed for searches saved before 12 PM NZ time in My Favorites. This has been fixed.
    • July 2022 URM-150103 SF: 5300531, 5307689, 5333336
      Records with the same title were missing from the Related titles field in the record's full details. This has been fixed.
    • July 2022 URM-148495 SF: 5307469
      Wrong Dutch translation for pickup location in the Request form. This has been fixed.
    • July 2022 URM-136890 SF: 5314934, 5331180, 6042031, 6331700, 6342822
      After the execution of MD Import profile with the Unlink for CZ and create a local bib option, a CZ record was overwritten and unlinked, but the original CZ record could still be found in Primo VE. This has been fixed.
    • June 2022 PRM-46460 SF: 05302719, 05321247, 05325545, 05325714
      An error occurred when users attempted to access results beyond the 2,000 record limit. When the search results limit is now reached, The Next page button (>) is hidden and the following message appears:

      You have reached the maximum number of results to display. To get more relevant results, please refine your search term.

      The nui.results.maxResults code has been added to the Results Tile Labels code table to allow translation and customization.
    • June 2022 PRM-43157 SF: 05324086
      When mobile devices were held horizontally, the "X" button appeared in the middle of the search box. This has been fixed.
    • June 2022 URM-145383 SF: 05301341, 05305816, 05317040, 05329627
      Direct linking was not working for some CDI records. This has been fixed.
    • June 2022 URM-160440 SF: 6321291, 6288159, 6269281, 6264949, 6260546, 6051166, 5327480, 5320712, 5317188, 5312451
      View It services did not appear for deduped records that consisted of both electronic and physical records. This has been fixed.
    • June 2022 URM-163859 SF: 6376893, 6358158, 6353070, 6337694, 6340358, 6216171, 6047124, 6037162, 6381234, 6255559, 6338921, 6220613, 6268956, 6347322, 6337611, 6338088, 6259171, 6220491, 6334634, 6322823, 6334801, 6310179
      In some cases, the link resolver did not return available services. This has been fixed.
    • June 2022 URM-164572 SF: 6034923, 6321739, 6340109
      Available View It portfolios were not displayed for signed in users. This has been fixed.
    • June 2022 URM-164682 SF: 5327874, 6057732
      On the Discovery Import Profile, Link to Request links based on a template were always created despite having an empty linking parameter. This is fixed by setting the new disable_link_for_empty_linking_parameter discovery customer parameter to true.
    • June 2022 URM-166071 SF: 5333354
      For some Japanese records, the rft.title parameter was missing in the OpenURL of the CDI records  even when the addata title was populated. This has been fixed.
    • June 2022 URM-170452 SF: 6328110
      The LOCATE service option overlaid the text on the mobile view. This has been fixed.
    • June 2022 URM-171662 SF: 6352188
      The Include/Exclude full text matches button did not appear for in the results for CDI search scopes. This has been fixed.
    • June 2022 URM-172539 SF: 6358249
      Patron roles and identifiers were not appearing in My Library card. This has been fixed.
    • May 2022 PRM-45210 SF: 05326867, 05329078
      The main region in the search results page did not contain the search results when using JAWS. This has been fixed.
    • May 2022 PRM-44848 SF: 05328517
      Screen reader was not reading selected values under the prefilter headings in Advanced Search. This has been fixed.
    • May 2022 PRM-44823 SF: 05328629
      In Advanced Search, no auditory message was given to JAWS users when the Search Field drop-down list was automatically changed to Title after selecting Starts with from the Precision drop-down list. This has been fixed.
    • May 2022 PRM-46432 SF: 06301286
      On the Advanced Search page, fields and buttons in the Search Criteria region were not hidden from screen readers when the region was collapsed. This has been fixed.
    • May 2022 PRM-46498
      After specifying an invalid Start Date for a publication in Advanced Search, its error message overlapped the End Date. This has been fixed.
    • May 2022 PRM-46506
      Unable to use the Space or Enter keys to toggle the Expand my Results and Search in Full Text settings. This has been fixed.
    • May 2022 PRM-43590
      When navigating from Library Search to Newspaper Search, persistent facets were not cleared. This has been fixed.
    • May 2022 PRM-45790 SF: 06049652, 05324137, 05305861, 05326288, 06224258, 06036918, 06207657, 06219560, 06230747, 05326278, 05326028, 05318607, 06054869, 06042885
      In some cases, the E-mail export action sent email with missing record details. This has been fixed.
    • May 2022 PRM-46108 SF: 06048782, 06280212
      Unpaywall links and Quicklink used the same code for their labels. The following codes have been added to allow Unpaywall links to have different labels:
           - fulldisplay.unpaywall.PDF has been added to the Links and General Electronic Services Labels code table.
           - fulldisplay.unpaywall.PDF.tooltip has been added to the Full Display Labels code table.
           - nui.aria.unpaywall.PDF has been added to the aria Labels code table.
    • May 2022 PRM-45341 SF: 05301441
      The display label and aria-label were incorrectly using the same code. To resolve this issue, we have added a separate code for aria-label:
           - (Existing) specificChapterPages is still configured in the Resource Sharing Labels code table.
           - (New) nui.aria.almaResourceSharing.specificChapterOrPages has been added to the Aria Labels code table.
    • May 2022 PRM-45038 SF: 06261743, 06225642, 06048685, 05324926, 05324481, 05314298, 05299990, 05299738
      The link to RefWorks in the User Area menu could not be disabled in mobile view by configuration. This has been fixed.
    • May 2022 PRM-42657 SF: 05309629, 05314276, 05325867
      Booking request on mobile devices did not display calendar icon. This has been fixed.
    • May 2022 URM-164297 SF: 06047077, 06210604, 06290067, 06294106, 06300792
      Failure to load Ranking Configuration page. This has been fixed.
    • May 2022 URM-148087 SF: 05299041
      Saved searches emails were not being sent to users. This has been fixed.
    • May 2022 URM-145367 SF: 05314096
      Sort title was incorrectly including 245.c. This has been fixed.
    • May 2022 URM-135987 SF: 05299393, 05300720, 05301323, 05320360, 05411836
      There was a discrepancy between Browse Search results and Alma's Browse Shelf Listing because Primo VE filters deduped records from Browse Search results. If you want to display deduped records in Primo VE's Browse Search results, set the Discovery customer parameter filter_dedups_from_discovery_browse to false.
    • May 2022 URM-169209 SF: 06303045
      Added 槪->概 and 硏->研 to cjk_unicode_trad_to_simp_normalization.txt to provide the correct normalization.
    • April 2022 URM-168895 SF: 6051713, 6293243
      In some cases, the Get It section was replaced with View It in record's full display after clicking the availability of a physical record in brief results. This has been fixed.
    • April 2022 PRM-46135 SF: 5307369
      Selecting a record's citation path incorrectly added it to search history. This has been fixed.
    • April 2022 PRM-43590
      As expected, persistent facets were not cleared after moving to Newspaper Search. This has been fixed.
    • April 2022 URM-132743 SF: 5319578, 5349740
      The Export Context object to BX job processed 0 records. This has been fixed.
    • April 2022 URM-148354 SF: 5303159, 5315464, 5319553, 5323985
      Clicks to Bx recommendations were not being tracked in Analytics. This has been fixed.
    • April 2022 URM-150103 SF: 5300531, 5307689, 5333336
      Records with same title were missing from 'Related title' section in record's details. This has been fixed.
    • April 2022 URM-151882 SF: 5322038
      Changes to the 'vertitle' display field's normalization rule had no effect on the display. This has been fixed.
    • April 2022 URM-152190 SF: 5300477, 5301309, 5301529, 5307366, 5317479, 5317933, 5318030, 5318040, 5322702, 5333021, 6256855
      In some cases, facets occasionally failed to display in searches. This has been fixed.
    • April 2022 URM-153965 SF: 5300602, 6245421
      Exported record to email failed to open for some records. This has been fixed.
    • April 2022 URM-154655 SF: 5318892
      Unable to update suggested database information in Resource Recommender Configuration. This has been fixed.
    • April 2022 URM-154734 SF: 5319465
      Journal Search categories were not displayed when switching from Database Search to Journal Search. This has been fixed.
    • April 2022 URM-160361 SF: 5303933, 5304508
      In some cases, creator and contributor name were duplicated in Brief and Full display. This has been fixed.
    • April 2022 URM-162411 SF: 6051683, 6225245, 6297715, 6299698
      The volume filter in Get It displayed the codes rather than the display values of the item's volumes. This has been fixed.
    • April 2022 URM-162950 SF: 5307015
      The Full view link 'Chapters of this book' displayed the code instead of its display value and required a page refresh to see the display value. This has been fixed.
    • April 2022 URM-165368 SF: 5307536, 5320294
      Some RIS Type mappings were unexpected for export to RIS actions (such as EndNote). For a current list of mappings, see Primo VE Resource Type Mappings. In addition, you can now customize which fields are used to map information to RIS fields with export actions. For more information, see Custom RIS Mapping.
    • April 2022 URM-166044 SF: 6218808
      The icon_other.png image displayed for records that matched multiple local resource types instead of using the image from the first matching type. This has been fixed.
    • April 2022 URM-166324, 5328930 SF: 5328930
      When the Prefer resources with PO line option was enabled on Alma's Online Services Order page, preference was not given to services of collections/portfolios that have a linked PO Line (for example, subscribed services or owned) in Primo VE. This has been fixed.
    • April 2022 URM-166387 SF: 6241688, 6254798
      The Enable QR On Top option in View Configuration was not saved after being cleared. This has been fixed.
    • April 2022 URM-167215 SF: 6052222
      Offensive subject terms were not hidden in facets if the results also included a collection facet. This has been fixed.
    • April 2022 URM-167305 SF: 6225215, 6250469
      Long public note in holdings record created unnatural word wrapping for fields in Get It. This has been fixed.
    • March 2022 URM-167546 SF: 6210654
      Resource Sharing Request form had pickup location pre-filled with a library when it should have been empty. This has been fixed.
    • March 2022 URM-165678 SF: 6234330
      Location facet displayed the code of the location instead of the location name. This has been fixed.
    • March 2022 URM-168372 SF: 6287239
      Could not change and distribute the GetIT! Tab 1 discovery labels code table because it could not be saved. This has been fixed.
    • March 2022 URM-167973 SF: 6273807
      Multiple errors appeared in console after displaying a record's full details. This has been fixed.
    • March 2022 URM-167937 SF: 6272138
      Local search scope was unable to find recently indexed records. This has been fixed.
    • March 2022 PRM-43590
      When moving from Library Search to Newspaper Search, all persistent facets are now cleared.
    • March 2022 URM-165678 SF: 6234330
      Location facet displayed code instead of value when the location code contained a hyphen. This has been fixed.
    • March 2022 URM-157887 SF: 5317610
      Some Chinese words were incorrectly treated as stop words in the ftext fields and were omitted from the search. This has been fixed, but re-indexing is required.
    • March 2022 URM-164541 SF: 5307674
      In the Citations section in a record's full display, the URL to access Scopus citations was incorrectly using the http prefix instead of https. This has been fixed in the template for Scopus.
    • March 2022 URM-166021 SF: 5311859
      When exporting a record with the Print action, codes appeared instead of translated text. This has been fixed.
    • March 2022 URM-154476 SF: 5329520, 6252887
    • For consortia, institutions were repeated in the list of available member institutions for each deduped instance of a record. This has been fixed so that each institution appears only once in the list.
    • March 2022 URM-165876 SF: 6241153, 6242204, 6238611, 6239688, 6241565, 6240078, 6241072, 6241838, 6239955, 6241801, 6240269, 6240462, 6240319, 6238693, 6241889, 6240065, 6239963, 6240520, 6240138, 6239632, 6240535, 6238586, 6240144, 6240406
      Course reserves from IZ were not appearing in course reserves scope. This has been fixed.
    • March 2022 URM-159513 SF: 6245760, 6231304, 6026594, 5321302, 5314784, 5302706, 5299204
      Depending on the language, the icon did not match the resource type of the record. This has been fixed.
    • March 2022 URM-153356 SF: 5300515, 6028185
      In some cases, the facet value for local fields were indexed and not normalized in Solr (with Capital letter). This has been fixed. For local fields that are using normalization + parallel dc, in case of similar values that differ only in case, the values are now gathered and counts are merged. A re-indexing is not required.
    • March 2022 URM-163222 SF: 5305780, 6237572
      Fields configured as mandatory on the Resource Sharing form were not marked as mandatory in the UI. This has been fixed.
    • March 2022 URM-148243 SF: 5302605, 5312708, 5312819, 5314035, 5329428
      For local resource types, the ExportRIS action did not include the type TY. This has been fixed.
    • March 2022 URM-163451 SF: 06035706
      The initials for the days in the calendar application were not changed for Spanish. This has been fixed.
    • March 2022 URM-158293 SF: 5312712
      Permalinks were not working for Search Webhook. This has been fixed.
    • March 2022 URM-149657 SF: 5299717
      For portfolios that were activated in the NZ, off campus users were not seeing the Available for all status in the record's full display. This has been fixed.
    • March 2022 URM-167295 SF: 6259712
      Local extensions of CZ records were not searchable for institutions that were not part of the consortium. This has been fixed.
    • March 2022 URM-167546 SF: 6210654
      The pickup location was prefilled for resource sharing requests when it should have been empty by default. This has been fixed.
    • March 2022 URM-165978 SF: 6225679
      In the English interface, the pickup location appeared twice in the Pickup location drop-down list on the Request form. This has been fixed.
    • March 2022 URM-156332 SF: 5302009, 5314469
      Search API failed for local records when the 'tab' parameter existed. This has been fixed.
    • March 2022 URM-154718 SF: 5319410
      The page number that appears above the results list was not using the description/translation defined with the nui.paging.pagenumber code In the Results Tile Labels code table. This has been fixed.
    • February 2022 PRM-45883 SF: 5324771, 6290243
      For details, see Track Sort by Date in Analytics.
    • February 2022 URM-167483 SF: 6269906, 6269945, 6270541, 6270555, 6270698
      Primo VE Search API failed. This has been fixed.
    • February 2022 URM-167295 SF: 6259712
      Local extensions of CZ records were not searchable for institutions that were not part of the consortium. This has been fixed.
    • February 2022 URM-156478 SF: 5302061
      Customized local search and facet fields were not institution aware for consortia. This has been fixed.
    • February 2022 URM-156183 SF: 5306885, 5320807, 5331968, 6025783, 6216550
      Records imported into Alma with physical inventory not appearing in Primo VE until re-indexed. This has been fixed.
    • February 2022 URM-159455 SF: 5322643
      Thumbnail templates for which the value of Field started with a space loaded empty and later filled with incorrect data. This has been fixed.
    • February 2022 URM-154049 SF: 5323526
      The Warmup collection discovery cache job is always failing or being skipped. This has been fixed.
    • February 2022 URM-158631 SF: 5316629
      Duplicate GES links appearing in Links section on the Services Page. This has been fixed. To support this fix, the fulfillment_general_electronic_services_links_merge parameter has been added to the Customer Parameters mapping table (Configuration Menu > Fulfillment > General > Other Settings). For more details, see Configuring Other Settings (Fulfillment).
    • February 2022 URM-153484 SF: 5302104, 5399309
      Export to RIS, BibText, and Mendeley intermittently failed. This has been fixed.
    • February 2022 URM-156440 SF: 5319006
      The export file is missing many favorites after an export. This has been fixed.
    • February 2022 URM-157633 SF: 5316754, 5322781
      When a Service Availability Rule was based on rfr_id, it did not work as expected for General Electronic Services (GES). This has been fixed.
    • February 2022 URM-164911 SF: 5323529
      Some Chinese characters were not displayed properly on the No Results page. This has been fixed.
    • January 2022 URM-164240 SF: 6022062, 6038209, 6204775, 6210654, 6213479
      On the Resource Sharing Request form, the pickup location always defaulted to the first value in the drop-down list. This has been fixed.
    • January 2022 URM-158748 SF: 5317225
      The append translation action, which is used to translate local display fields in the normalization rules, was not translating values that contained capital letters. This has been fixed.
    • January 2022 URM-161230 SF: 5323358
      Codes displayed instead of Facet labels in the new feature Supporting Austlang languages. Requires a re-index of the relevant records for the change to take effect. This has been fixed.
    • January 2022 URM-159059
      The Real Time Item-Level Descriptions functionality for Resource Sharing is not working. This has been fixed.
    • January 2022 URM-158885 SF: 5319047, 5758162
      RTA and Get It display library name instead of location name when the library code and location name are identical. This has been fixed.
    • January 2022 URM-158613 SF: 5316844, 5323968
      Internal users cannot log on to Primo VE. This has been fixed.
    • January 2022 URM-158277 SF: 5300177, 6052766, 5305041, 5312758, 6057645, 5320699, 5326615, 5324950, 5306715, 5300849, 5325992, 5307820, 6044909, 6054578, 6035371, 5300856, 5316861, 5308462, 5301927, 6037835, 5320520, 5325184
      In some cases, Browse by Subject returned incorrect results. This has been fixed.
    • January 2022 URM-157888 SF: 5306602, 5317526
      Type label for BX recommendations was not translated. This has been fixed.
    • January 2022 URM-157817 SF: 5302339, 5319107, 6028250
      Item filter in Get It filter was not working correctly. This has been fixed.
    • January 2022 URM-154896 SF: 5301663
      Some records were not re-indexed after removal of items using the Alma job Withdraw Items. This has been fixed.
    • January 2022 URM-150514 SF: 5299530
      CSL has an additional space after the title. This has been fixed.
    • January 2022 URM-142894 SF: 5331858
      Unable to place digitization request for dedup records. This has been fixed.
    • January 2022 URM-136890 SF: 5314934, 5331180
      Overwritten CZ records still appeared in Primo VE. This has been fixed.
    • January 2022 URM-136070 SF: 5313747
      Unable to add conditions containing more than one-word phrases for Restricted Search Groups. This has been fixed.
    • January 2022 URM-130684 SF: 5319244, 5329966, 5747863
      Collections resource type facet was not translated. This has been fixed.
    • January 2022 URM-117842 SF: 5309533, 5319855, 5324655
      When filtering the items list or clearing its filtering in Get It, users were returned to the holdings list. This has been fixed.
    • January 2022 URM-105361 SF: 5311859, 5329912
      In some cases, the source of a record as shown in the record's details was different from the source returned when the using the Send to Print action. This has been fixed.

    CDI-Related Updates

    Starting with the November 2021 release of CDI, this section lists the fixes and enhancements associated with CDI by their release date to ensure that Primo/VE customers are aware of the availability of these updates during and between releases of Primo/VE. When available, CDI updates are released on the first Wednesday of the month.


    2022 Updates

    December 7, 2022

    November 2, 2022

    • CDI-24203 SF: 05323983, 05332163, 05332458, 06205711, 06298619
      The PNX mapping for resource types 'text resource' and 'report' was changed from genre 'book' to genre 'unknown' to ensure compatibility with the Alma link resolver.
    • CDI-21705 SF: 05324810
      The Harvard Business Review (ISSN:0017-8012) was classified as a magazine in CDI, resulting in low relevancy rankings. It is now classified as Journal/Journal Article during the static rank score computation to improve its relevancy rankings; the record's display will not change.

    October 5, 2022

    • CDI-24386 SF: 06396689, 06464126
      Because article titles were missing from the Addata field in the PNX, GES services were having linking issues. This has been fixed.
    • CDI-22880 SF: 05305867, 06039704
      In some cases, a related topic was presented instead of an exact match topic from Britannica. This has been fixed.

    September 7, 2022

    • CDI-20976 SF: 05322339, 05322369 (Added November 4, 2022)
      An issue with non-verbatim match penalty for English spelling variations has been fixed. The following document has been updated to clarify CDI's handling of synonyms and spelling variations: Search and Ranking in CDI.
    • For Journal resource types, addata/Jtitle is created from the record PublicationTitle field. If the record lacks a PublicationTitle, addata/Jtitle is created from the record Title field.
    • CDI-24259 SF: 05298841
      CDI search results returned Subject facet values that contained only special characters (such as an asterisk or at sign). This has been fixed.

    July 6, 2022

    • In some cases when CDI assigns Title based rights coverage, a URI based direct link was returned for a Link in Record collections that was not active for the institution. The linking logic was updated to prefer OpenURL in this scenario.
    • CDI-23694 SF: 06326253
      The Is Part Of relationship for Book Chapters displayed an incorrect full date of YYYY-MM-DD instead of only full year of YYYY. This has been fixed.
    • CDI-24054 SF: 06250266
      CDI was not retrieving the correct number of results in Advanced Search when an OR operator was used between search fields or inside a search field. This has been fixed.
    • CDI-23965 SF: 06366996
      Removed the word סקס from the extension list of the Hebrew name זקס.

    June 1, 2022

    • CDI-23711 CDI failed to populate the PNX addata/title section for 'text_resource' and 'report' resource types that lacked a Publication Title. This has been fixed by mapping the Title field to the addata/title section when ‘text_resource’ and ‘report’ type records do not have a Publication Title.
    • CDI-20344 SF: 05332919
      Full Text availability was incorrectly assigned to the first document in each CDI instance due to an error in the document enumeration code. This has been fixed so that the documents are returned in the Full Text filter only for institutions that have activated the content.
    • CDI-23709 SF: 06321534
      The terms Full Paper, Note, and Research were added to CDI's subject terms exclusion list. This change will take place at the completion of the first search update after the June release. A holistic revision of CDI Subject Headings is under consideration, but it is not planned at this time.

    May 4, 2022

    • CDI-23255 SF: 06206239
      Unless the client/user allows full text matching, matches in References and TableOfContents no longer return in search results when simple and advanced searches include any field. This change takes effect when the first search update of the CDI May release completes, which normally occurs two days after a release's deployment.
    • CDI-23464 SF: 05309104
      Some contributor fields were not highlighted correctly in the full display. This has been fixed.

    April 13, 2022

    • CDI-23604 SF: 06301387
      In the top section of the full record, the Book Reviews link indicated an incorrect number of related reviews. This has been fixed so that the number in the link matches the actual number of reviews.
    • CDI-20716 SF: 05310194, 05333381
      The journal title facet previously included publication titles for all resource types. This has been corrected so that the journal title facet values are limited to the following CDI resource types:
      • Article
      • Journal
      • Newspaper
      • Newspaper article
    • CDI-23223 SF: 05324574
      The Alma Link Resolver matched with genre=document instead of with genre=transcript and returned a broken link. The CDI content type transcript was mapped to Text resource journal article instead of Text resource document to conform to the format expected by the Alma and SFX link resolvers.
    • CDI-22758 SF: 05321247, 05325545, 05325610, 05328033, 05333161, 06021204, 06207527, 06210234, 06231544, 06262995, 06276628
      Primo Classic/VE - deep pagination caused CDI timeout. The limit for CDI's search results has been extended to 2,000 items to match the limits imposed by Primo and Primo VE local indexes. Support for deeper pagination is being investigated, but it is not planned at this time.

    March 2, 2022

    • CDI-23175 SF: 05309042
      In the list of synonyms for CDI, the term medical history was added as a synonym for the term health history.
    • CDI-20571 SF: 05301624, 05301659, 05308283, 05317174
      The following terms were added to the compound words list:
      • cross sectional
      • cyber attack
      • cyber attacks
      • nano particles
      • post traumatic
    • CDI-23357 SF: 06026832
      When searching for the title Juridical Review, the results were auto-corrected to Judicial Review. This was fixed.
    • CDI-23347 SF: 06057153
      Empty HTML tags in the record's metadata caused blended searches to return limited results. This was fixed.
    • CDI-22933 SF: 05308685
      The following words were added to the Hebrew synonyms list for CDI:
      • כשלונה=כישלונה
      • הרהורים=הירהורים
      • עפרון=עיפרון
      • ספרייה=ספריה

    February 2, 2022

    • CDI-20977 SF: 05331227
      Subject facet values with double quotes returned no results. This was fixed.
    • CDI-21147 SF: 05306454, 05320735, 05323780
      CDI uses a fuzzy match mechanism (also known as OR QUERY mechanism) that targets long queries, accepting results where many terms show up in title field, although not all terms appear in results. This mechanism was not activated when the search included ISSNs or patterns that look like ISSNs. For example, in a search such as the following, the 1193-1199 looked like an ISSN and did not activate the fuzzy matching mechanism:
      Added value of double inversion recovery magnetic resonance sequence in detection of cortical and white matter brain lesions in multiple sclerosis. The Egyptian Journal of Radiology and Nuclear Medicine, 45(4), pp.1193-1199.
      This has been fixed, and queries with ISSNs now also use the fuzzy matching mechanism.
    • CDI-22863 SF: 05309069
      When performing a title search (via an advanced search), multiple title fields were searched in addition to the primary title (such as subtitle, alternative title, journal title, book title, and so forth). With this fix, a significant boost is given to the primary title over the other title fields.

    2021 Updates

    December 1, 2021

    • SF: 05327188, 05326630, 05320976, 05314635, 05302831, 05299989
      The Spanish language facet failed to filter Spanish language records due to an incorrect language code mapping. This was fixed.
    • When exporting CDI records from Primo/VE to RIS or to a reference management system (such as EndNote), they appeared with type Generic. This has been fixed to map the correct type.

    November 3, 2021

    • CDI support for the Exclude eBooks in CDI Results feature for Primo/VE. 

    October 21, 2021

    • The CDI Activation Analysis Tool can be used to check a specified CDI record in your results list to see which collection activation in Alma or SFX caused the record to appear in the results and to determine why its full text is flagged for availability or not. For additional information regarding the tool and its usage, see CDI Activation Analysis.

    • Was this article helpful?