Asset - Term Link

The asset - term link package automatically detects terms with the same (or similar) name of assets and links them together.

To avoid to blindly let the package to link terms with assets, an option to preview the ouput is provided. The typical path to use this package would be:

1. Ask the package to generate the asset-term link preview.
2. If happy with the output, ask the package to link terms with assets.

The package also provides a method to remove terms from assets (only the relationships created by the package itself).

Configuration

Configurations

• Case sensitive: whether to match asset names using a case sensitive logic, default: No.
• Match type: whether to do an exact match or a partial (wildcard) match with the asset names, default: Exact.
• Output type, default: Preview:
  • Preview: to generate a csv with the term-asset link preview.
  • Generate: to create the term-asset link.
  • Delete: to delete the term-asset link.
• Regex to match characters to replace (optional): if there is a re-naming happening between the term and the asset that can be identified by a regex pattern, use this field to identify the characters to be replaced.
• Regex with replacements characters (optional): if there is a re-naming happening between the term and the asset that can be identified by a regex pattern, use this field to specify the replacements characters.
• Name prefix (optional): prefix to add to terms to match with assets.
• Name suffix (optional): suffix to add to terms to match with assets.

Warning

The suffix and prefix are applied after the regex replacement.

Filters

• In scope assets: comma separated asset types (in scope for the term assignment). Please refer to the following link for the list of asset types: https://developer.atlan.com/models/
• Qualified name prefix (Asset filter) (Optional): starting value for a qualifiedName that will determine which assets to match with glossary terms. If blank all assets with type defined in In scope assets are considered.
• Tags (Asset filter) (Optional): tags (comma separated) filter to apply to assets that will determine which assets to match with glossary terms. If blank all assets with type defined in In scope assets are considered. For source synced tags with values, each tag has to follow the format Tag Name@@@Tag Value
• Owner users (Asset filter) (Optional): owner users - usernames (comma separated) filter to apply to assets that will determine which assets to match with glossary terms. If blank all assets with type defined in In scope assets are considered.
• Owner groups (Asset filter) (Optional): owner groups (comma separated) filter to apply to assets that will determine which assets to match with glossary terms. If blank all assets with type defined in In scope assets are considered.
• Glossary list (Term filter) (Optional): list of comma separated glossary names. Only terms belonging to these glossaries are used. If blank all glossaries are considered.
• Glossary certificate filter (Term filter) (Optional): glossary term certificate. Only terms with the specified certificate status are used. If blank the filter is ignored.
• Glossary categories filter (Term filter) (Optional): list of categories path (comma separated). Each path should use @ as a path-delimiter. For example, if the category is called Lowest, which itself is a subcategory of Middle, itself a subcategory of Top: Top@Middle@Lowest. If blank the filter is ignored.

What it does

1. Retrieve the list of terms.
2. Update each term name accoring to regex, suffix and prefix defined in the workflow config.
3. Compare the created term name with the list of asset types defined in the Asset types config parameter (filters, if defined, are applied here).

4. Based on the output type defined in the configuration different logics are executed:

   PreviewGenerateDelete Lineage

   A csv file with the list of matching term-asset combinations is generated with the following columns:

   • asset_guid
   • asset_type_name
   • asset_qualified_name
   • asset_name
   • term_guid
   • term_qualified_name
   • term_name
   • term_glossary

   How to download the file

   The file with the preview can be downloaded from the Argo workflow log screen.

   Warning

   The preview file is always generated even if Preview is not selected as ouput type.

   Link terms with assets.

   Remove terms from assets.

---