Data Catalog
There are scenarios where one needs to describe a collection of data packages, such as when building an online registry, or when building a pipeline that ingests multiple datasets.
In these scenarios, the collection can be described using a “Catalog”, where each dataset is represented as a single resource which has:
Specification
The Data Package Catalog builds directly on the Data Package specification. Thus a Data Package Catalog MUST
be a Data Package and conform to the Data Package specification.
The Data Package Catalog has the following requirements over and above those imposed by Data Package:
- There
MUST
be aprofile
property with the valuedata-package-catalog
, or aprofile
that extends it - Each resource
MUST
also be a Data Package
Examples
A generic package catalog:
A minimal tabular data catalog:
Data packages can also be declared inline in the data catalog:
Implementations
None known.