sections

5 rows where breadcrumbs = "["Metadata"]" and page = "metadata"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: references, breadcrumbs (array)

id ▼ page ref title content breadcrumbs references
metadata:id2 metadata id2 Metadata reference A full reference of every supported option in a metadata.json or metadata.yaml file. ["Metadata"] []
metadata:metadata-column-descriptions metadata metadata-column-descriptions Column descriptions You can include descriptions for your columns by adding a "columns": {"name-of-column": "description-of-column"} block to your table metadata: [[[cog metadata_example(cog, { "databases": { "database1": { "tables": { "example_table": { "columns": { "column1": "Description of column 1", "column2": "Description of column 2" } } } } } }) ]]] [[[end]]] These will be displayed at the top of the table page, and will also show in the cog menu for each column. You can see an example of how these look at latest.datasette.io/fixtures/roadside_attractions . ["Metadata"] [{"href": "https://latest.datasette.io/fixtures/roadside_attractions", "label": "latest.datasette.io/fixtures/roadside_attractions"}]
metadata:metadata-source-license-about metadata metadata-source-license-about Source, license and about The three visible metadata fields you can apply to everything, specific databases or specific tables are source, license and about. All three are optional. source and source_url should be used to indicate where the underlying data came from. license and license_url should be used to indicate the license under which the data can be used. about and about_url can be used to link to further information about the project - an accompanying blog entry for example. For each of these you can provide just the *_url field and Datasette will treat that as the default link label text and display the URL directly on the page. ["Metadata"] []
metadata:metadata-table-config metadata metadata-table-config Table configuration Datasette supports a range of table-level configuration options including sort order, page size, facets, full-text search, column types, and more. These are now documented in the table configuration section of the configuration reference. For backwards compatibility these options can be specified in either metadata.yaml or datasette.yaml . ["Metadata"] []
metadata:per-database-and-per-table-metadata metadata per-database-and-per-table-metadata Per-database and per-table metadata Metadata at the top level of the file will be shown on the index page and in the footer on every page of the site. The license and source is expected to apply to all of your data. You can also provide metadata at the per-database or per-table level, like this: [[[cog metadata_example(cog, { "databases": { "database1": { "source": "Alternative source", "source_url": "http://example.com/", "tables": { "example_table": { "description_html": "Custom <em>table</em> description", "license": "CC BY 3.0 US", "license_url": "https://creativecommons.org/licenses/by/3.0/us/" } } } } }) ]]] [[[end]]] Each of the top-level metadata fields can be used at the database and table level. ["Metadata"] []

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [sections] (
   [id] TEXT PRIMARY KEY,
   [page] TEXT,
   [ref] TEXT,
   [title] TEXT,
   [content] TEXT,
   [breadcrumbs] TEXT,
   [references] TEXT
);