Single Table Metadata JSON
Last updated
Last updated
This guide describes the single table metadata JSON spec.
Create your metadata programmatically. Use the Python API to automatically detect the metadata based on your data.
The metadata for a single table contains the following elements:
(required) "METADATA_SPEC_VERSION"
: The version of the metadata. If you are using this, the metadata version will be "SINGLE_TABLE_V1"
, indicating that it is a single table that is compatible with SDV version 1.
(required) "columns"
: A dictionary that maps the column names to the data types they represent and any other attributes.
"primary_key"
: The column name that is the primary key in the table
"alternate_keys"
: A list of column names that can act as alternate keys in the table
If your table includes sequential data, other keys are available to describe the sequences. See Sequential Metadata for more details.
When describing a column, you will provide the column name and the data type, known as the sdtype.
The 5 common sdtypes are: "numerical"
, "datetime"
, "categorical"
, "boolean"
and "text"
. Click on the type below to learn more about the type and how to specify it in the metadata.
Boolean columns represent True or False values.
Properties (None)
Annotate groups of columns that represents higher level concepts. Denote the concept using the "type"
keyword, followed by "column_names"
with the list of columns involved. The column names can be present in any order.
Each relationship type supports different types of columns. Browse the table below to explore different options.
An address is defined by 2 or more columns that have the following sdtypes: country_code
, administrative_unit
, state
, state_abbr
, city
, postcode
, street_address
and secondary_address
.
* While anyone can add column relationships to their data, SDV Enterprise users will see the highest quality data for the relationships. To learn more about the SDV Enterprise and its extra features, visit our website.