Skip to content

Enrichment Purposes

Every container in an enrichment datastore carries a purpose: the operation that wrote it, or the fact that Qualytics did not write it. The purpose appears as a badge on the container, drives the filter and sort on the container listing, and is what the destination's Overview charts. This page lists the six purposes, where they appear, and what you see when you open a written container.

For the physical names and columns behind each purpose, see Enrichment Outputs and Export Outputs. For the settings that decide what gets written, see How Enrichment Works.

The six purposes

Purpose Written by The container holds
Scan A Scan of a linked source Failed checks, check metrics, source records, or scan operations. Up to four outputs per source, depending on the results the Scan produced.
Remediation A Scan whose source uses the Append or Overwrite strategy The anomalous records of one source container, one output per container.
Materialize A Materialize operation A copy of one source container, as of the last run.
Export An Export operation, or Export Check Templates from the Library Exported anomalies, checks, field profiles, or check templates.
Computed You, on the enrichment datastore itself A computed table, file, or join defined over the written containers.
Other Not written by Qualytics A container Qualytics did not write, or one it can no longer attribute to a purpose.

Where purposes appear

  • On the container: a badge on each row of the container listing and on the container's overview.
  • On the container listing: the ordinary listing for the connector, with a Purpose filter and sort added, so you can select remediation outputs, materialized copies, or another purpose, and a Last Write sort that orders containers by when Qualytics last wrote to them.
  • On the datastore's Overview: Purpose Distribution charts the written containers by purpose, so you can see at a glance how much of the destination is scan output, remediation, materialized copies, or exports. Above it, Totals shows the count of linked datastores alongside the destination's container and record metrics. The Linked Datastores panel on the same tab is described under Last write.

What a written container shows

Open a written container and its overview explains itself:

  • The display name is built from the purpose and the source, for example Failed Checks (TPCH) or ORDERS / Remediation (TPCH), with the physical name shown beside it. See Output names and display names for how Qualytics maintains them.
  • Origin names the source datastore that wrote the output, the operation that writes it, and the time of the last write with a link to that operation. A container Qualytics cannot confirm having written shows no last write rather than a borrowed one.
  • About describes what the container holds and what one row represents, down to the columns Qualytics adds.
  • For remediation and materialized outputs, the Lineage tab links back to the source container at container and field level. See Lineage.
  • A computed table, file, or join shows a Definition section instead, with the query or the join it is built from.

See Also

  • Enrichment Outputs

    Physical names and columns of Scan, remediation, and materialized outputs.

    Enrichment Outputs

  • How It Works

    Settings, what each operation writes, automatic sync and profile, display names, lineage, and last write.

    How It Works

  • Introduction

    What enrichment is, why to link a destination, and what the destination can and cannot do.

    Introduction