catalog
Catalog

Data catalog

The catalog is the searchable inventory of every table DataRunner has seen across your connections — schema, columns, last scan time — annotated with the descriptions and tags your team adds.

Read
3 min
Sections
3
Plans
All plans

What the catalog tracks

Every time DataRunner introspects a connection, it records each table as a catalog asset: the table name, its schema, the originating connection, and the timestamp of the last scan. The catalog view lets you search across all connections and filter by connection.

  • Table — the introspected table name
  • Schema — owning schema (e.g. public)
  • Description — human-written context (you add this)
  • Connection — which connection it came from
  • Last scan — when the schema was last refreshed

Populating the catalog

Assets appear automatically as connections are introspected — testing a connection or running a schema refresh fills the catalog. If a catalog is empty, run a schema refresh on the connection to populate it.

Describe and tag

Add a description and tags to any asset so teammates know what a table means and who owns it.

http
PATCH /api/v1/catalog/assets/{id}
Authorization: Bearer <token>
Content-Type: application/json

{
  "description": "One row per fulfilled order. Source of truth for revenue.",
  "tags": ["finance", "core"]
}
Pair the catalog with Metrics — once a table is documented, promote the canonical numbers it feeds into named, reusable metric definitions.