Tag Examples¶
Real scenarios showing how tags focus quality scores, route alerts, and keep a tag library clean. Pick a tab to see scenarios grouped by what the tag is used for.
Making a datastore score reflect the tables you own¶
Context. An analytics team monitors 5 tables in a warehouse datastore that holds 60. The datastore score sits low because tables nobody maintains, such as old staging copies, fail their checks. The team creates a Monitored tag with a weight of 10 and applies it to its 5 tables.
What happens. The checks on those tables inherit the tag and move two levels up in importance right away, so their anomalies rank higher. When the team reports to stakeholders, it opens the tag's page and shows the Quality Score card, which covers only the tagged tables. Each tagged table will also count 11 times as much as an untagged one in the warehouse score once the table weights are recalculated, for example by the next tag change on the datastore. See When Weights Are Recalculated.
Why it works. The tag gives the team a score for its own tables without hiding the others, which still count and can still be reviewed. One tag answers both questions: how healthy is the data we own, and which of its anomalies come first.
Paging the privacy team on anomalies in personal data¶
Context. A retailer's privacy team must review any quality issue in fields that hold personal data. The data stewards tag those fields, and the tables that hold them, with PII. The team then creates a Flow with an Anomaly Detected trigger filtered to the PII tag and a Slack notification to #privacy-review.
What happens. A scan finds null emails in a customers table tagged PII. The check on that table carries the tag through inheritance, so the new anomaly starts with it, the Flow matches, and the channel gets a message naming the table and the check. Anomalies on untagged tables never reach the channel.
Why it works. The tag carries the business rule ("personal data gets reviewed") into every check and anomaly below the tagged tables, so the Flow doesn't need to list them. A new table tagged PII next month is covered without editing the Flow.
Letting a team label its own work¶
Context. The finance data team wants a Q3 Close label for the tables it reconciles each quarter, but a global tag would show up in every other team's tag pickers. An Admin gives the team the Editor team permission, and a team member creates Q3 Close with the Finance scope.
What happens. Only Finance members and Admins see the tag in pickers and filters, and it can only go on the datastores assigned to Finance. Other teams still see it on the tables that carry it, with a lock icon, and cannot remove it. After the close, the team deletes the tag on its own, without waiting for an Admin.
Why it works. The team owns its vocabulary end to end, and the workspace-wide tag list stays short for everyone else.
Merging duplicate tags after a migration¶
Context. After two catalogs were combined, the library holds both Personal-Data and PII, applied to overlapping sets of fields, checks, and anomalies. One Flow filters on Personal-Data, and several saved filters use it. An Admin opens the Personal-Data tag page to see where it is used.
What happens. The Footprint section shows the tag on 340 assets across three datastores and one Flow. The Admin clicks Merge, picks PII, reviews the assets that switch, and confirms. Every asset, the Flow, and the saved filters now use PII, Personal-Data is deleted, and the PII timeline records the merge.
Why it works. Merge moves every reference in one step, so nothing is left filtering on a tag that no longer exists. Deleting Personal-Data instead would have stripped the label from 340 assets, and the Flow would have lost the tag it filters on.
See Also¶
-
Best Practices
Guidelines for a small, consistent tag library.
-
Permissions
Who can create, apply, and manage tags.
-
Introduction
What tags are and why to use them.
-
How It Works
How tags influence Qualytics, the three types, and how a tag spreads through a datastore.
-
Weight Modifier
How a tag's weight changes quality scores and check importance.
-
Global Tags
Tags open to the whole workspace, managed by Admins.
-
Team Tags
Tags scoped to one team, and what happens when the scope changes.
-
External Tags
Tags imported from a connected data catalog.
-
Tag Page
The summary, timeline, assets, and map of a single tag.