Skip to main content

Asset-term link
App

The Asset-term link app automatically links glossary terms to assets when they share the same or a similar name. It uses flexible matching rules, optional renaming based on regular expressions, and filters for both assets and terms to control which relationships are created or removed.

You can use this app to preview potential relationships, generate new links between terms and assets, or delete links that were previously created by the app.

Workflow name​

Specifies a unique and descriptive name to identify the workflow configuration in the Atlan interface. This name appears in the workflow list and helps distinguish this workflow from other glossary or governance workflows.

Example:

finance-asset-term-link

Case-sensitive match​

Determines whether the app compares names using case-sensitive or case-insensitive matching.

  • Yes: Matching is case-sensitive. For example, Customer matches only Customer and not customer.
  • No: Matching is case-insensitive. For example, Customer matches Customer, customer, or CUSTOMER.

Use case-sensitive matching when naming conventions treat different cases as different assets or terms.

Match type​

Controls whether names must match exactly or can match partially.

  • Exact: Only exact matches between the adjusted term name and the asset name are considered. Use this when naming is strictly standardized.
  • Partial: The adjusted term name can match part of the asset name (wildcard-style behavior). Use this when asset names embed glossary terms within longer identifiers.

Output type​

Defines what the workflow does with the matches it finds after names have been adjusted and matched.

When Output type is set to Preview, the app generates a CSV file containing all potential term–asset matches. No changes are made in Atlan.

The CSV includes the following columns:

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

Use this CSV to validate that the regex, prefix/suffix, and filters produce the expected matches before switching to Generate or Delete.

Regex to match characters to replace​

Specifies the regular expression pattern used to identify characters or substrings in the original term name that must be replaced before matching. The pattern is applied to each term name before any prefix or suffix is added.

Examples:

[_\s]+

Matches underscores and whitespace so they can be removed or normalized with another character such as _.

^dim_

Matches the dim_ prefix at the start of a term name so it can be stripped before matching.

Regex with replacement characters​

Defines the replacement string for the pattern in Regex to match characters to replace. The replacement is applied wherever the pattern matches in the term name.

Examples:

-

Replaces any sequence that matches [_\s]+ with a single hyphen, for example converting customer orders and customer_orders into customer-orders.

fct_

Works with ^dim_ to replace the dim_ prefix with fct_, for example converting dim_customer into fct_customer.

Name prefix​

Specifies a prefix to add to the transformed term name (after regex replacement) before matching with asset names. Use this when asset names always start with a fixed token that's not part of the glossary term.

Example:

tbl_

If the adjusted term name is customer_orders and the prefix is tbl_, the final name used for matching is tbl_customer_orders.

Name suffix​

Specifies a suffix to add to the transformed term name (after regex replacement and prefix handling) before matching with asset names. Use this when asset names consistently end with a fixed token, such as _view or _table.

Example:

_view

If the adjusted term name is customer_orders and the suffix is _view, the final name used for matching is customer_orders_view.

Prefix and suffix order

The app applies regex-based replacements first, and then applies the Name prefix and Name suffix settings. Plan your patterns and affixes with this order in mind.

Filters​

Filters limit which assets and terms are considered when generating, previewing, or deleting links. Asset filters apply to the candidate assets, and term filters apply to the candidate glossary terms.

In scope assets​

Specifies a comma-separated list of asset types that are considered for term assignment.

Example:

Table, View, MaterialisedView

Qualified name prefix (Asset filter)​

Specifies a prefix for the asset qualified name. Only assets whose qualified name starts with this value are in scope. If this field is blank, all assets with types defined in In scope assets are considered.

Example:

default/snowflake/production/SALES_DB/

Tags (Asset filter)​

Defines a comma-separated list of tags to use as a filter for assets.

  • Only assets that have at least one of the specified tags are considered.
  • If this field is blank, no tag-based filter is applied.
  • For source-synced tags with values, each tag must use the format Tag Name@@@Tag Value.

Example:

PII, Sensitive@@@High

Owner users (Asset filter)​

Specifies a comma-separated list of usernames. Only assets owned by at least one of these users are considered. If this field is blank, no user-based ownership filter is applied.

Example:

data.steward, analytics.owner

Owner groups (Asset filter)​

Specifies a comma-separated list of group names. Only assets owned by at least one of these groups are considered. If this field is blank, no group-based ownership filter is applied.

Example:

finance-team, risk-office

Glossary list (Term filter)​

Specifies a comma-separated list of glossary names. Only terms that belong to these glossaries are considered. If this field is blank, all glossaries are considered.

Example:

Business glossary, Technical glossary

Glossary certificate filter (Term filter)​

Defines a certificate status filter for terms. Only terms with the selected certificate status are considered. In the UI this appears as a dropdown with the placeholder Select a certificate; leaving it blank ignores certificate status.

Example:

VERIFIED

Glossary categories filter (Term filter)​

Specifies a comma-separated list of category paths to restrict which terms are used. Each path uses @ as a level delimiter and @@@ to separate the category path from the glossary name.

Example:

Top@Middle@Lowest@@@Concepts

This value targets the Lowest category under Middle under Top in the Concepts glossary.

See also​