How to Create Custom Catalog Filters

Table of Contents

  1. Overview
  2. Access Metadata Settings
  3. Create a Custom Field Set
  4. Add a Field (Filter Group)
  5. Add Filter Options
  6. Submit a Support Request
  7. Additional Resource
  8. Troubleshooting

Overview

Catalog filters can be used to efficiently search and filter assets in the Data Catalog. Using custom metadata field sets allows to define predefined options that can be configured into custom catalog filters.

**NOTE** After completing the steps in this article, you must submit a support request to finalize the custom catalog filter setup. Submit a support request through Data & Insight Support page.

When submitting your request, please include the following:

  • Domain link
  • The Custom Field Set and Fields to be used

Access Metadata Settings

Open the Administration Panel from the side navigation by clicking the three horizontal lines in the upper-left corner of the screen. Select Administration, then locate Metadata under Site Settings.

Administration screen with Metadata section highlighted

The Metadata page is where predefined and custom metadata fields are created and managed across the platform. You will see the following tabs:

  • Categories - Manages category related metadata and the Category filter.
  • Fields - Used for creating and managing predefined and custom metadata field sets.
    • Default - Predefined field sets which include: Asset name, Asset Description, Row Label and Tags.
    • Custom - Custom Field Sets
  • Audit - Displays summary view of asset compliance with the configured metadata requirements in aforementioned tabs.

Metadata screen

Create a Custom Field Set

From the Fields tab, select Custom to view existing custom field sets. If none exit, the list will be empty. Click the blue Create Field Set located in the right portion of the screen, enter a descriptive name and save.

Add a Field (Filter Group)

Select the newly created field set in the left panel and choose Add field. Enter a short name for the field that will appear as the filter heading in the Data Catalog. This field name will be visible to the end user.

Add Filter Options

Configure the Field Type as Select and add the drop-down options that should appear in the catalog filter. Each option must be added individually using the Add option button.

Note: The Select field type is required only for creating catalog filters and is not required for metadata fields in other use cases.

Note: Some users may see the Label 1 field while others may not depending on the setup. If this field is visible, you can safely ignore it as it is not needed for this process.

Save your changes when complete.

**NOTE** Once support has enabled the filters, do not rename or remove any existing options. New options may still be added if necessary by selecting Add option and contacting Support after doing so.

At this point, the custom metadata is ready for support to configure as a catalog filter.

Submit a Support Request

**NOTE** After completing the steps in this article, you must submit a support request to finalize the custom catalog filter setup. Submit a support request through Data & Insight Support page.

When submitting your request, please include the following:

  • Domain link
  • The Custom Field Set and Fields to be used

Support will enable the catalog filter, integrate it into the catalog view side panel and validate functionality.


Additional Resources

Below are resources exploring additional topics related to Catalog Filters

FAQs

  • Metadata is not visible in Administration:

    • Confirm you have administrator permissions. If needed, request access from a platform administrator.

  • The filter does not appear in the catalog:

    • Verify that Support has completed and closed the request.

  • Additional filter options are needed:

    • You may add new options to the existing field, but do not rename or delete options already in use. Submit a new support request after making changes.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.