Entropy Data
Entropy Data

Tags

A governed vocabulary for your data mesh: hierarchical labels you attach to data products, data contracts, assets, and more.

Tags add meaning that no field of the Open Data Product Standard or the Open Data Contract Standard covers. A tag such as governance/pii can be attached to many resources at once, and every list view can be filtered by it.

You'll find them under Governance → Tags (/{organization}/governance/tags).

Managed and unmanaged tags

Any resource can carry a tag simply by naming it in its specification. Such a tag is unmanaged, meaning it exists only as a string on the resources that use it.

A managed tag is defined explicitly, with an ID (for example governance/pii), an owning team, a description, optional links, and optional properties. Both kinds work everywhere tags are used. A managed tag adds a definition to point at, an owner to ask, and an audit trail.

The Unmanaged Tags view lists tags that are in use but not yet defined, grouped by resource type, with a Create managed tag action to adopt them. It shows up to the first 50 per resource type.

Where tags can be used

Data products, data contracts, assets (including tags imported during ingestion), business definitions, source systems, and domains and teams (hidden by default, see Customizations).

A managed tag's details page lists every resource that carries it under Usages. A tag that is still in use cannot be deleted.

Hierarchy

Tag IDs are hierarchical, using / as the separator (governance/pii/email). Parent levels need not exist. Filtering is prefix-based, so filtering by governance also matches governance/pii, and tag filters render the hierarchy as an expandable tree instead of a flat list.

Defining a managed tag

Tags can be created in the web UI, as YAML, or through the API.

FieldDescription
IDUnique technical identifier, for example governance/pii. Unique case-insensitively.
OwnerThe team that owns the tag. Editing and deleting require permissions in that team.
DescriptionWhat the tag means and when it should be applied.
LinksNamed links to relevant resources, for example the policy behind the tag.
PropertiesAdditional custom properties. Tags with nested properties can only be edited as YAML or via the API.
id: "governance/pii"
info:
  owner: "governance-team"
  description: "Marks resources that contain personally identifiable information."
links:
  policy: "https://wiki.example.com/data-protection/pii-policy"
properties:
  retentionDays: 90

info.owner is the team's external id, not its internal UUID.

Governance

  • Permissions: creating, editing, and deleting a tag requires the corresponding resource permission in the owning team. See Roles & Permissions.
  • Change requests: under the four-eyes principle, the actions become Request Add, Request Update, and Request Delete. See Change Management.
  • Audit trail: every change is recorded, with a side-by-side version comparison.
  • Compliance checks: governance policies can be evaluated against tags, shown in the Compliance card on the tag's details page.

Certifications

A certification is bound to a tag, for example certification/gold. Attaching that tag to a data product makes the certification badge and filter pick it up. Tags used by a certification are not shown as ordinary tag chips, because the badge already carries the message.