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

    Configuring Static Facets

    Primo supplies out-of-the-box values for the following static facets:
    You can define additional static facets using any of the predefined fields in the Facets section of the PNX (such as format or genre) and any of the 50 locally defined facets.
    Static facets can be configured at the institution level for institutions in multitenant environments. All other environments must configure static facets at the installation level.
    The following tables are used to configure static facets in the Back Office:
    Tables Used to Configure Static Facets
    Table Description
    Static Facets mapping table
    Defines each static facet and automatically assigns the following tables to each one:
    • A static facets values mapping table (see below)
    • A display values code table (see below)
    A change to any static facet mapping table requires you deploy of all code and mapping tables from the Deploy All page.
    Mapping tables for the static facet values
    Each mapping table defines the list of values for a static facet.
    A change to any static facet mapping table requires you deploy of all code and mapping tables from the Deploy All page.
    When a static facet is defined in the Static Facets mapping table, the system automatically creates a values mapping table for the static facet. For example, the facet_genre_values mapping table defines the list of values used for the Genre static facet.
    For the Library facet, the system automatically populates the values table with the library codes that have been defined with the Institution wizard and uses this table for all institutions in your Primo installation.
    Code tables to display values in the Front End UI
    Each code table defines the labels that display in the Front End for each static facet value. This code table allows you to customize the facet labels per view and language.
    When a static facet is defined in the Static Facets mapping table, either a predefined code table is used or a code table is generated when you first synchronize the static facet’s values mapping table. For example, if you define the resource type facet as a static facet, the system uses the predefined Facet Resource Type code table.
    To define a static facet:
    1. On the Back Office's home page, select Advanced Configuration.
      The Advanced Configuration page opens.
    2. Select All Mapping Tables.
      The Mapping Tables page opens (see Static Facets Subsystem).
    3. Select the Static Facets subsystem to display the list of the static facets mapping tables.
      Static Facets Subsystem
    4. Click Edit to select the Static Facets mapping table for editing.
      The Static Facet Mapping Table page opens.
      Static Facets Mapping Table
    5. In the Create a New Static Facet section, select a facet in the Choose a Facet drop-down list.
    6. Click Create to add the new facet to the mapping table.
      For every static facet, the Values Table Name and Code Table Name fields are defined automatically by the system and cannot be modified.
    7. Click Save to save your changes and return to the Static Facets Subsystem page (see Static Facets Subsystem).
    8. Click Edit to modify the facet values of the facet that you defined – for example, the facet_genre_values table.
      The facet_genre_values table opens.
       
      facet_genre_values Mapping Table
    9. Enter values in the fields in the Create a New Mapping Row area to add a new facet value to this table.
    10. Click Create to add the new mapping row to the table.
    11. Click Save to save your changes and return to the Static Facets Subsystem page (see Static Facets Subsystem).
    12. Click Synch to propagate the new values to the associated code table (such as the Basic Media Type code table for prefilter facets).
      This operation only adds new values to the code table. To override existing values, you must update the code table manually.
    13. To view or update the associated code table, edit the code table on the Primo Home > Advanced Configuration > All Code Tables page.
    14. Deploy the code and mapping tables.

    Adding Resource Types

    It is possible for on-premises customers to modify the list of resource types. For example, if you want to add a new resource type that will be used for display, a prefilter, and facets, use the following procedure.
    Because prefilter and resource type facets are defined as static facets by default, there is no need to define them as static facets.
    To add a new resource type:
    1. Add the new resource type to the Display/Type field in the normalization rules.
    2. Save your changes and then use the Primo Home > Deploy All page to deploy the changes made to the normalization rules.
    3. Rerun the pipe to update the PNX.
      It is now possible to run pipes without harvesting from the data source.
    4. Update the following mapping tables:
      1. facet_pfilter_values in the Static Facets subsystem – Add the new resource type to the prefilter values. Save the values.
      2. facet_rtype_values in the Static Facets subsystem – Add the new resource type to the resource type values.
    5. On the Static Facets subsystem page (see Static Facets Subsystem), click the Sync button in the facet_pfilter_values and facet_rtype_values mapping table rows to propagate the changes to the associated code tables.
      Static Facets Subsystem
    6. Update the following mapping tables:
    7. pre-filter normalization rules in the Normalization subsystem – Add the new resource type to the prefilter facet.
    8. format_mean normalization rules in the Normalization subsystem – Add the new resource type to the resource type filter.
    9. Add the correct labels for the new resource type in the following code tables:
      • Basic Media Type
      • Advanced Media Type
      • Icon Code
      • Facet Resource Type
      Include labels for English and any other languages you use in the Front End.
    10. Use the Primo Home > Deploy All page to deploy the changes made to the mapping and code tables.
    11. Add an icon image for the new resource type to the following directory on the server:
      fe_web
      cd images
    12. Enable the new resource type in the Front End via the Views wizard:
      1. In the Basic Search tile, select the new resource type.
      2. In the Advanced Search tile, edit the resource type and add the new resource.
    13. Use the Primo Home > Deploy All page to deploy the changes made to the views.
    • Was this article helpful?