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

    Primo 2022 Release Notes

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

    For information regarding Primo VE, see the Primo VE Release Notes.

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

    August Sneak Preview

    • Resource Recommender – Introduce new Banner resource type

    • Collection Discovery – Add option to define Collection Discovery per library/view (NERS)

    • Collection Discovery – Add Next and Previous to navigate the collection items from full display

    • Personal Details and Settings – Allow users to set their preference (for example, use my search history)

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

    May Sneak Preview

    • View it enhancement to show all available links for CDI Records (NERS).

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

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

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

    • Resource Recommender Enhancement – Introduce new banner type.
      .

    Features

    Give Us Feedback Tool (NERS)

    May 2022 PRM-45818
    Primo 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:

      • Subject – Update the issue type if different from what was entered in the previous step.

      • Problem description – (Optional) Enter the description of the issue or feedback. 

      • Email – (Optional) 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.

      PVE_Feedback_Screen2.png

      Specify Feedback Details
    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://sqa-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 action 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 the New Primo UI.

    Element Description

    Report a Problem mapping table (Primo Home > General > Mapping Tables)

    This new mapping table allows you to activate and configure this functionality at the view level only.

    Report a Problem Labels code table (Primo Home > General > Code Tables)

    This new code table allows you to customize and translate the labels and error messages associated with the Feedback Tool.

    In addition, it allows you to customize the content of the feedback letter.

    aria Labels code table (Primo Home > General > Code Tables)

    This code includes the codes that provide accessibility support for this functionality.

    May 2022 PRM-45574
    Instead of Primo 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.

    The following example shows the preferred linking option with the group headings defined:

    Primo_ShowPreferredLinking_CDI.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 a Link in Record link or a special template.

        and/or:

      2. links/linktorsrcadditional – Multiple occurrences of this field is permitted, and each includes an additional direct link from CDI.These links are sorted by provider, which is returned in the $$G subfield.

    2. Link resolver:

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

      2. OpenURL related services from Alma.

    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 in the Institution Wizard (Primo Home > General > Institutions List) and CDI returns multiple links, Primo determines whether a link is open access only if the $$H subfield is set to free_for_read.

    The following example shows all linking options with the group headings defined:

    Primo_ShowAllLinks_CDI.png

    All Links Expanded in View Online

    Regardless of whether the feature is enabled, note that the format of the links in View Online/View it has changed slightly:

    Old format:

    OldFormat.png

    New format:

    NewFormat.png

    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 Properties mapping table (Primo Home > General > Mapping Tables)

    When set to true, the new display_all_links parameter instructs CDI to return all available full text links so that they are selectable in a record's full display.

    If set to false, CDI returns only the preferred link.

    GetIT! Link 1 Configuration mapping table (Primo Home > General > Mapping Tables)

    The following mapping was added to provide linking for the new functionality:

    Delivery Category  Status Source Direct Link Availability/Service Link Link Field
    Remote Search Resource fulltext_multiple All Y Out@@display linktorsrcadditional; openurladditional

    GetIT! Tab 1 Text Configuration mapping table (Primo Home > General > Mapping Tables)

    The following mapping was added to provide the label for the link to access all full text links:

    Delivery Category  Status Source Tab 1 Label
    Remote Search Resource fulltext_multiple All tab1_full

    GetIT! Tab1 Labels code table (Primo Home > General > Code Tables)

    The following codes define the labels for showing more or less links at a time:

    • default.nui.getit_full.multiple_showmore – Show more

    • default.nui.getit_full.multiple_showless – Show less

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

    • default.nui.getit_full.multiple_linktorscr_subsc – <blank>

    • default.nui.getit_full.multiple_linkresolver – <blank>

    • default.nui.getit_full.multiple_linktorscr_oa – <blank>

    Aria labels code table (Primo Home > General > Code Tables)

    The following code are used for accessibility:

    • default.nui.aria.fulldisplay.multiple.showmore – Show more links

    • default.nui.aria.fulldisplay.multiple.showless – Show less links

    • default.nui.aria.fulldisplay.viewOnline – {{link}}

    Calculated Availability Text Labels code table (Primo Home > General > Code Tables)

     

    The following codes define the text labels for calculated availability:

    • default.delivery.code.fulltext_multiple – Full text available

    • default.delivery.class.fulltext_multiple – GetItGreen

    Advanced Search - Improved Visibility of Search Results (NERS)

    May 2022 PRM-45820
    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

    Configuration Options

    This functionality is enabled for you. The following table lists configuration associated with this functionality.

    Element Description

    Search Tile code table (Primo Home > General > Code Tables)

    The following code was added for the display label of the Search Criteria section on the Advanced Search page:

    default.nui.search-advanced.searchCriteria – Search Criteria

    aria Labels code table (Primo Home > General > Code Tables)

    To support accessibility, the following code was added for the display label of the Search Criteria section on the Advanced Search page:

    default.nui.aria.search.searchCriteria – Search Criteria

    Improved CSL Mapping - Differentiate Authors and Creators

    May 2022 PRM-36608
    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.

    This functionality is applicable to all CSL styles.

    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

    Configuration Options

    This feature relies on the following configurations:

    1. Update your Normalization Rules to include the creatorfull and contributorfull fields, which have been added to addata section of the PNX and are used to ensure that citation data is mapped correctly for creators/contributors and their respective roles. These fields include the following subfields and suggested mappings:

      • $$N - (Required) The full name of the creator/contributor.

        Primo_Creator_Rule1.png

        Add $$N Subfield to Creatorfull Field

        Primo_ContributorR1.png

        Add $$N Subfield to Contributorfull Field
      • $$L - The last name of the creator/contributor.

        Primo_Creator_Rule2.png

        Add $$L Subfield to Creatorfull Field

        Primo_ContributorR2.png

        Add $$L Subfield to Contributorfull Field
      • $$F - The first name of the creator/contributor.

        Primo_Creator_Rule3.png

        Add $$F Subfield to Creatorfull Field

        Primo_ContributorR3.png

        Add $$F Subfield to Contributorfull Field
      • $$R - (Required) The role of the creator/contributor, which is mapped using the MARC 100/700 subfield e in the source and the new CreatorContrib_full mapping table.

        Primo_Creator_Rule4.png

        Add $$R Subfield to Creatorfull Field

        Primo_ContributorR4.png

        Add $$R Subfield to Contributorfull Field

      PNX example:

      <Creator_full>$$NCole, K. C$$LCole$$FK. C$$Rtranslator

      <Contributor_full>$$NMartin, Debra L$$LMartin$$FDebra L$$Reditor

      <Contributor_full>$$NAnderson, Cheryl P$$LAnderson$$FCheryl P$$Reditor

    2. Configure the CreatorContrib_role mapping table, which maps the role found in 100/700 subfield e to the $$R subfield in the creatorfull and contributorfull fields. The following table lists the out-of-the-box values:

      Source Code (700/100 subfield e) Target Code ($$R)
      Writer of accompanying material secondary contributor
      Writer of added commentary secondary contributor
      Interviewer interviewer
      Illustrator illustrator
      Writer of preface secondary contributor
      Writer of added text secondary contributor
      Author author
      Writer of added lyrics secondary contributor
      Composer composer
      Editor editor
      Author of introduction, etc. secondary contributor
      Author of afterword, colophon, etc. secondary contributor
      Author of dialog secondary contributor
      Writer of supplementary textual content secondary contributor
      Translator translator
      Director director
      Author in quotations or text abstracts secondary contributor
      Writer of introduction secondary contributor
      Editor of compilation editor
      • The case of the letters in the source (subfield e) must match the case specified in the Source Code column to return a Target Code in subfield $$R.

      • The supported target codes are author, composer, director, editor, illustrator, interviewer, secondary contributor, and translator.

      • Secondary contributors are not sent to CSL.

      • Contributors that do not have a role are treated as authors.

      • If no roles are specified, all contributors are considered authors and are sent to CSL with the aulast, aufirst, auinit, au fields instead of the creatorfull and contributorfull fields.

    Ability to Include or Exclude Full Text Matches in CDI

    May 2022 PRM-46058
    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'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 Matching

    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

    View Properties mapping table (Primo Home > General > Mapping Tables)

    The following options are supported for the new CDI_FullText_search parameter:

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

    • yes-enduser-selection – Searches always check full text for matches in CDI records, but end users have an option to disable it.

    • no-always – Searches never check full text for matches in CDI records and there is no end user option to enable it.

    • no-enduser-selection – Searches never check full text for matches in CDI records, but end users have an option to enable it.

     

    • For the May 2022 release, if there is no entry for this parameter in the table, the default setting is yes-always for new and existing views.

    • For the August 2022 release, if there is no entry for this parameter in the table, the default setting is no-always for new and existing views.

    Results Tile code table (Primo Home > General > Code Tables)

    The following codes have been added to support the customization and translation of labels associated with this feature:

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

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

    • default.nui.cdiFTsearch – Search in Full Text

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

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

    aria Labels code table (Primo Home > General > Code Tables)

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

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

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

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

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

    Support Persistent Suggestions in Resource Recommender

    May 2022 PRM-46033
    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:

    Primo_PersistentDatabaseExample.png

    Persistent Database Resource Displayed First

    Configuration Options

    To Support this functionality, the Display Always column was added to the Resource Recommender page (Primo Home > FE & Delivery > Resource Recommender). When set to true, 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.

    Primo_ResourceRecommender_DsiplayAlways2.png

    Display Always Column - Resource Recommender Configuration

    For more details, see Resource Recommender for Primo

    February 2022 PRM-44683
    When enabled, this functionality embeds links to PDF/HTML full text for CDI records directly into the brief display to provide a convenient and quick way for users to access full text with a single click. Quicklinks provides links to both free to read content and paywalled content. For more details, see Quicklinks in Primo and Primo VE.

    quicklinks_primo_2.png

    Embedded PDF and HTML Quicklinks for CDI Record in Brief Display

    Configuration Options

    This functionality is disabled by default. The following table lists the configuration options associated with this functionality.

    Element Description

    View Properties mapping table (Primo Home > General > Mapping Tables)

    To enable this functionality, create and set the enable_quicklink_icons parameter to true for your view.

    Aria Labels code table (Primo Home > General > Code Tables)

    The following code is used for screen readers:

    • default.nui.aria.quicklink.PDFQuick Link to PDF, opens in a new window
    • default.nui.aria.quicklink.HTMLQuick Link to HTML, opens in a new window

    Full Display Labels code table (Primo Home > General > Code Tables)

    The following codes are used to customize and translate the display labels and tooltips for this functionality:

    • default.fulldisplay.PDFGet PDF
    • default.fulldisplay.HTMLRead Online
    • default.fulldisplay.PDF.tooltipGet PDF
    • default.fulldisplay.HTML.tooltip: Read Online

    To support this functionality, the following actions have been added to the Action Usage subject area:

    Group Subgroup Action Description

    Document

    Link

    Link to PDF fulltext using CDI Quicklink

    The user selected a PDF Quicklink.

    Document

    Link

    Link to HTML fulltext using CDI Quicklink

    The user selected an HTML Quicklink.

    Show Journal Coverage Dates in Brief Results and Journal Search (NERS #6718)

    February 2022 PRM-44022
    For electronic journals managed in Alma, you now have the option to display a coverage summary by year in its availability statement in the results on the Library Search, Journal Search, and My Favorites pages, reducing the need to view the journal's full display to get coverage information. The coverage summary will include a maximum of three date ranges. If there are more than three, the summary will include the more label.

    PVE_SummaryCoverage_MoreLabel.png

    Coverage Information Displayed in Brief Results
    • Because the coverage information is calculated in real time, it will not appear instantly in the results.

    • If a journal is available with no limitations and its portfolios do not contain any date ranges, coverage information will not display in the availability statement.

    • Coverage information may include a single embargo, and if multiple embargoes exist, only one of them will appear in the coverage. If there a more than three date ranges in the coverage, the embargo will be excluded from the coverage if it exists.

    Configuration Options

    This functionality is disabled by default. The following table lists the configuration options associated with this feature.

    Component Description

    Institution Properties mapping table (Primo Home > Advanced Configuration > All Mapping Tables)

    To display the coverage information for electronic journals on the Brief Results and Journal Search pages, set the brief_results_journal_coverage parameter to true.

    Following the calculation of journal coverage in brief results, institutions using direct linking may see incorrect Link Resolver usage data in Alma Analytics reports. Until this issue is resolved, it is recommended that you disable journal coverage if you are using direct linking. This issue is expected to be resolved in the May 2022 release.

    Calculated Availability Text code table (Primo Home > Advanced Configuration > All Code Tables)

    The following codes were added to support the customization and translation of the labels used for this functionality:

    • default.delivery.code.coverage – Coverage: {0}
    • default.delivery.code.coverage.from – From {0}
    • default.delivery.code.coverage.until – Until {0}
    • default.delivery.code.coverage.and_more – and more
    • default.delivery.code.coverage.year_not_available – Most recent {0} year(s) not available
    • default.delivery.code.coverage.year_available – Most recent {0} year(s) available
    • default.delivery.code.coverage.month_not_available – Most recent {0} month(s) not available
    • default.delivery.code.coverage.month_available – Most recent {0} month(s)  available
    • default.delivery.code.coverage.year_month_not_available – Most recent {0} year(s) {1} month(s) not available
    • default.delivery.code.coverage.year_month_available – Most recent {0} year(s) {1} month(s) available

    Option to Hide Offensive Subject Terms to Support Diversity, Equity, and Inclusion (DEI)

    February 2022 PRM-45303
    This functionality allows you to create a list of inappropriate or offensive words and phrases (in any language) that should be hidden in Subject fields that appear in the full display, brief results, and facets. When configured, the excluded words/phrases are not case-sensitive and must match the contents of the Subject field exactly.

    For example, if the word nutrition is excluded, Subjects containing only the word nutrition are not displayed, while Subjects that contain the word nutrition as part of a phrase (such as nutrition periodicals) will continue to be displayed.

    PVE_DEI_Example2.png

    Facets Example

    Configuration Options

    The DEI - List of Terms to Exclude from Subject Heading section has been added to the Edit Institution page (Primo Home > Ongoing Configuration Wizards > Institution Wizard) has been added to support this functionality. Per line, add the offensive word or phrase (in any language) that you want to exclude from display in the Subject headings. The exact words/phrases are not case-sensitive. For more details, see Loading the DEI File.

    Primo_Input_DEI_File_Inst_Wizard.png

    Exclusion List for DEI - Edit Institution

    Expand Database Search (NERS #7199)

    February 2022 PRM-45650
    Previously, searches performed in Database Search matched only on the title. Searches are now expanded to all fields (such as subject and author) and DB categories.

    Primo_DB_Search_AnyField_Example.png

    Expanded Database Search

    Configuration Options

    This functionality is enabled by default, but searching by DB categories requires additional configuration and re-indexing. The following table lists the configuration options associated with this functionality. For complete configuration, see Configuring the Database Search Interface.

    Configuration Page Description

    Institution Properties mapping table (Primo Home > Advanced Configuration > All Mapping Tables)

    The expanded Database Search functionality is enabled by default. If you prefer to search by title only, set the new expanded_db_search parameter to false.

    Normalization Set Editor (Primo Home > Local Data > Normalization Sets)

    The search/dbsearch field has been added to the following templates to map DB categories from your source records: Alma MARC - Template and Alma UNIMARC - Template.

    To enable searching by DB category, you must create a normalization rule for search/dbsearch that includes the following mapping information:

    • The MARC field (6XX and 9XX) that holds the DB category information in the source.

    • The new Use code table transformation, which maps translation information that you have defined in the DB Search code table.

    For example:

    Primo_NormRule_Search_DBSearch.png

    DB Search code table (Primo Home > Advanced Configuration > All Code Tables)

    If you provide translations for DB categories, add codes and translations for each DB category that includes the following characters:

    • dot (.) – For each DB category that includes a dot (such as M.B.A.), you must replace the dots with an underscore in your source records. In addition, you must add a code for each updated category in the DB Search code table. For example:

      default.dbcategories.M_B_A – M.B.A.

    • ampersand (&) – For each DB category that includes an ampersand (such as Guns & Roses), add a new code in which the ampersand has been replaced with its HTML character code in the DB Search code table. For example:

      default.dbcategories.Guns_&amp;_Roses – Guns & Roses

    • apostrophe (') – For each DB category that includes an apostrophe (such as Women's and Gender Studies), add a new code in which the apostrophe has been replaced with its HTML character code in the DB Search code table. For example:

      default.dbcategories.Women&pos;s_and_Gender_Studies – Women's and Gender Studies

    Search Tile code table (Primo Home > Advanced Configuration > All Code Tables)

    The following code has been added to support the display label that appears in the search box on the Database Search page when the expanded DB Search functionality is enabled:

    default.nui.databasesearch.searchbox.expanded – Enter a search term

    Ongoing Accessibility Improvements (February)

    February 2022 PRM-46173
    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 Labels code table:

      Code Description
      default.nui.mandatory.header Please fill in the following mandatory fields to proceed:

    Additional Enhancements

    • May 2022 PRM-46292
      Apache 2.4 Upgrade for On-Premises Customers – For more details, see Upgrade to Apache 2.4 for Primo PDS.
    • May 2022 PRM-38368
      Display Time Zone for Loan Alerts – You can now display the time zone next to the loan alert date in My Library Card by setting the new display_loan_timezone parameter to true in the View Properties mapping table (Primo Home > General > Mapping Tables).

      Primo_MyLibrary_DisplayTZ_LoanTab.png

      Time Zone Displayed in Loans Tab
    • February 2022 PRM-45819
      Track Sort by Date in Analytics – With this enhancement, the sort by date usage actions are now tracked with new actions in Primo Analytics:
      Group Subgroup Action Description

      Results List

      Sort

      Old: Sort by date

      New: Sort by date-newest

      User sorted results by newest date.

      Old: Sort by local

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

    • February 2022 PRM-44659
      SAML Certificate Update – To accommodate the updated expiration policy of the certificate vendors, we have created the first of our bi-annual signed certificates. The next update is planned for the August release.
    • February 2022
      Alert Email Processing – For the following ANZ (Australia and New Zealand) environments only, alert processing will now run daily at 6 AM (Singapore TZ) instead of 12 AM:
      • Primo MT APAC 01
      • Primo MT APAC 03
      • Primo MT APAC Sandbox

    Resolved Issues

    • May 2022 PRM-46092
      Times Cited links in the Full View could not be customized at the institution level. This has been fixed, but you should ensure that your wos_citation & scopus_citation links are configured properly at the institution level.
    • May 2022 PRM-38368 SF: 05315482, 05316406, 05817426
      The Days before loan due-date parameter in the Library Card Alerts mapping table (Primo Home > General > Mapping Tables) was not working as expected. This has been fixed.
    • May 2022 PRM-30667 SF: 5299081
      Search for truncated ISBN did not retrieve records. This has been fixed.
    • May 2022 PRM-36608 SF: 5315571, 5315644, 5315646, 5316291
      CSL citations needs to differentiate between creators and contributors. See Improved CSL Mapping - Differentiate Authors and Creators.
    • May 2022 PRM-38373 SF: 5332800, 5582421, 5655181
      SAML - Support sending SHA-256 logout requests. This has been fixed.
    • May 2022 PRM-40915 SF: 5312816, 5328616
      Records with two authors with same first/last name showed only one name in PNX, which affected citations. This has been fixed, but you will need to update your normalization rules and re-index your records to include the new addata/creatorfull and addata/contributorfull fields. For more details, see Improved CSL Mapping - Differentiate Authors and Creators.
    • May 2022 PRM-42657 SF: 5309629, 5314276, 5325867
      Booking requests on mobile devices did not display calendar icon. 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-43942 SF: 5310424
      After clicking the Remember all filters button, the sticky facets tooltip was not working. This has been fixed.
    • May 2022 PRM-44368 SF: 5332055
      Improved citation format for single vs. multiple page citations.
    • 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-44848 SF: 05328517
      Screen reader was not reading selected values under the prefilter headings in Advanced Search. This has been fixed.
    • May 2022 PRM-45038 SF: 6261743, 6225642, 6048685, 5324926, 5324481, 5314298, 5299990, 5299738
      The Link to RefWorks in the User Area menu could not be disabled in mobile view. This has been fixed.
    • May 2022 PRM-45092 SF: 05317749
      The new UI may be vulnerable to clickjacking. To reduce vulnerability, add and set the xframeoptionsset parameter to true in the Institution Properties mapping table (Primo Home > General > Mapping Tables) so that X-Frame-Options SAMEORIGIN directive is added to requests.
    • May 2022 PRM-45128 SF: 5307429
      While performing an export to BibTex, the Keywords field included an unwanted comma. 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-45744 SF: 5317457
      Full Display was partially opened from My Library Card. This has been fixed.
    • May 2022 PRM-45770 SF: 5302406
      Changed the time recorded in beacon to be the user's request time.
    • 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-45796 SF: 5317285
      When using the Full text splitter, pipe failed to process records. This has been fixed.
    • May 2022 PRM-46108 SF: 6048782, 6280212
      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:
           - default.fulldisplay.unpaywall.PDF has been added to the Full Display Labels code table.
           - default.fulldisplay.unpaywall.PDF.tooltip has been added to the Full Display Labels code table.
           - default.nui.aria.unpaywall.PDF has been added to the aria Labels code table.
    • May 2022 PRM-46135 SF: 5307369
      Citation path was added to the search history. This has been fixed.
    • May 2022 PRM-46317 SF: 6283240, 6298533
      In the new UI, Get It or View It was occasionally replaced with Get It or View It of another title when the record was opened in full display. 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-46447
      After clicking a lateral link in the record's details and then performing subsequent searches in Advanced Search, the subsequent searches were recorded as lateral linking actions instead of advanced search actions for Analytics. 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-46532 SF: 06349500
      Long labels for the Expand my results option cut off and partially hidden behind the search results panel. This has been fixed.
    • May 2022 PRM-45393 SF: 05332113
      Beginning with 2022-05-22, Primo Analytics no longer tracks the Display Primo Central versions action and now uses the Display FRBR versions action to track the following scopes: Primo Local, local, Primo Central, deep_search, and blended.
    • February 2022 PRM-45883 SF: 5324771, 6290243
      For details, see Track Sort by Date in Analytics.
    • February 2022 PRM-46202 SF: 6245724
      Log files were growing too rapidly since November 2021 release. This has been fixed.
    • February 2022 PRM-45590 SF: 5301342
      The structural markup of the My Account page made the content inaccessible to some users. This has been fixed.
    • February 2022 PRM-45134 SF: 5299326
      Facets that contained a comma failed when using the PrimoWebServices/xservice API. This has been fixed.
    • February 2022 PRM-44244 SF: 5536997, 5311463, 5310441, 5308397, 5301767, 5300344, 5299293
      In some cases, an incorrect number of citation trail results were returned. This has been fixed.
    • February 2022 PRM-43974 SF: 5808661, 5460387, 6048543, 5306531, 5303207, 5308499, 5437248, 5583746, 5324541, 5413157, 5308438, 5429608, 5464478, 5460912, 5322403, 5318093, 5312454, 5317837, 5357488, 5308832
      The citation trail was displayed inconsistently for full and brief results. This has been fixed.
    • February 2022 PRM-42719 SF: 5312253
      NVDA screen reader users were unable to navigate the results using the up/down arrow keys. This has been fixed, but users must enable the "Automatic focus mode for caret movement" option in NVDA -> Preferences -> Settings... -> Browse mode.
    • February 2022 PRM-40192 SF: 5311387, 5311731, 5920878
      Users could not add tags when the record ID contained a forward slash (/). This has been fixed.
    • February 2022 PRM-45476 SF: 5309028, 5317732, 5330766
      For CDI records, snippets display only when the search term is found in the snippet. This is not new functionality, but the label of the field that enables the display of snippets when a search term is found in any field has been changed to the following in the Views Wizard > Brief Results Tile:

      Primo_SnippetDisplayOptions.png

      Brief Results Tile in Views Wizard
    • February 2022 PRM-43226 SF: 5309028, 5317732, 5330766
      Facet check boxes on IOS devices required a double-tap to include them. This has been fixed, and the exclude button is always visible for facets on mobile/tablet devices (screen widths less than 1280 px).
    • February 2022 PRM-45998 SF: 6048841, 6211410, 6213132, 6254864
      The exclude button was always visible for facets regardless of the page width. This has been fixed. For page widths above 1280 px (desktop), users must now hover the cursor over a facet to display its exclude button, and for screen sizes (mobile/tablet) and page widths (desktop) less than 1280 px, the exclude button is always visible for facets.
    • February 2022 PRM-45751 SF: 5298815, 5299070, 5327866
      In some cases, the number of new items presented in alert emails did not accurately reflect the results provided in the consolidated link. This can happen when alerts are processed while indexing is running for CDI. The following display labels in the Send Email and Sms code table will no longer display the number of new items in alert emails to avoid confusion:
      Code (en_US only) Description

      default.alert.headingNewName

      New: New items found for: {1}

      Old: {0} new items found for: {1}

      default.alert.headingNew

      New: New items found for the search query: {1}

      Old: {0} new items found for the search query: {1}

      If you have customized these parameters, the above changes are not applied for you. In addition, these changes are not applied to any translations.

    • February 2022 PRM-45165
      The page was not titled according to the area's name after the record's full view was opened and closed. This has been fixed. Note that the default.main.title code is now used instead of the default.nui.brief.title code in the Header/Footer Tiles code table. For more details, see Configuring the Page Title in the New UI.
    • February 2022 PRM-45590 SF: 5301342
      Library user account page, semantic tagging. This has been fixed.
    • February 2022 PRM-45286 SF: 5307393, 5317399, 5318855
      Provider name is displayed with HTML entities in the Links section. This has been fixed.
    • February 2022 PRM-45058 SF: 5299116
      In the new Primo UI, logged-in user change of Interface language also changes user's Default language. This has been fixed.
    • February 2022 PRM-44891 SF: 5299504, 5333195
      Buttons via JAWS' form list isn't working. This has been fixed.
    • February 2022 PRM-44676 SF: 5298885, 5310697, 5850375
      Advanced Title "starts with" search in all caps returns zero results. This has been fixed.
    • February 2022 PRM-43716 SF: 5332460
      Primo Request type filter in my library card gets empty REQUESTS page when all requests of a specific type are cancelled. This has been fixed.
    • February 2022 PRM-43613 SF: 5330029
      EBSCO plugin - FacetConversion parameter does not work for multiple custom facets. This has been fixed.
    • February 2022 PRM-41598 SF: 5299638, 5930049
      In the new Primo UI, the Collection Discovery page in mobile miss-location. This has been fixed.
    • February 2022 PRM-30486 SF: 5299615
      The Get author first name and Get author last name transformation routines did not work for Hebrew. This is fixed by using the following new transformation routines for Hebrew: Get author first name non latin languages and Get author last name non latin languages.

    CDI-Related Updates

    Starting with the November 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

    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?