Leverage enrich and clean - Fluid Topics - Latest

Enrich and Clean Metadata
Category
Technical Notes
Audience
public
Version
Latest

To optimize metadata management for the ft:sourceName and jira_issuetype metadata keys, proceed as follows:

  1. Create a vocabulary containing all existing categories for the sources. Include all the synonyms used in the terminology.

  2. Add the appropriate subcategories for the Jira issue types.

  3. Go to the Enrich and Clean tab in the Knowledge Hub section of the Administration menu.

  4. Select the New rule button and use this vocabulary to generate new metadata based on the ft:sourceName metadata.

  5. Name the generated metadata custom_sources_and_jira_types.

  6. Check the Apply hierarchy check box.

  7. Select the Create button.

  8. Repeat the process (except for step one) for the jira_issuetype metadata.

    Maintain consistency by using the same vocabulary, custom metadata name, and hierarchy parameter.

  9. Select Save and trigger the reprocess.

    A metadata configuration table interface. The table has columns for 'Original Metadata', 'Taxonomy', 'Generated Metadata', 'Apply Hierarchy', and 'Remove Unclassified Values'. Two entries are visible. The first row shows "ft:sourceName" under 'Original Metadata', "Issue_types_Jira" under 'Taxonomy', and "custom_sources_and_jira_types" under 'Generated Metadata'. The 'Apply Hierarchy' check box is checked, and the 'Remove Unclassified Values' check box is unchecked. The second row is similar but has "jira_issuetype" under 'Original Metadata'.

  10. Add the new custom metadata as a facet to the Search page.

    A software interface showing a list of sources with check boxes for selection. The list includes: 'Confluence', 'Confluence checks', 'Customer New Request', 'Jira' (expanded to show 'Bug', 'Change Request', 'Compliance Escalation', 'Debrief', 'Design System', 'Distribution Release', 'Documentation'), 'Knowledge Base', 'MS Word', 'Salesforce Cases', and 'Salesforce Escalations'. There are also 'More' and 'Less' options indicated below and above the list.

Both values from ft:sourceName and jira_issuetype appear in a hierarchical form.

It is possible to expand on the principles outlined in this use case by incorporating additional metadata that involve hierarchies and share commonalities with others.