{"id": "facets:facets-metadata", "page": "facets", "ref": "facets-metadata", "title": "Facets in metadata", "content": "You can turn facets on by default for specific tables by adding them to a  \"facets\"  key in a Datasette  Metadata  file. \n             Here's an example that turns on faceting by default for the  qLegalStatus  column in the  Street_Tree_List  table in the  sf-trees  database: \n             [[[cog\nfrom metadata_doc import metadata_example\nmetadata_example(cog, {\n  \"databases\": {\n    \"sf-trees\": {\n      \"tables\": {\n        \"Street_Tree_List\": {\n          \"facets\": [\"qLegalStatus\"]\n        }\n      }\n    }\n  }\n}) \n             ]]] \n             [[[end]]] \n             Facets defined in this way will always be shown in the interface and returned in the API, regardless of the  _facet  arguments passed to the view. \n             You can specify  array  or  date  facets in metadata using JSON objects with a single key of  array  or  date  and a value specifying the column, like this: \n             [[[cog\nmetadata_example(cog, {\n  \"facets\": [\n    {\"array\": \"tags\"},\n    {\"date\": \"created\"}\n  ]\n}) \n             ]]] \n             [[[end]]] \n             You can change the default facet size (the number of results shown for each facet) for a table using  facet_size : \n             [[[cog\nmetadata_example(cog, {\n  \"databases\": {\n    \"sf-trees\": {\n      \"tables\": {\n        \"Street_Tree_List\": {\n          \"facets\": [\"qLegalStatus\"],\n          \"facet_size\": 10\n        }\n      }\n    }\n  }\n}) \n             ]]] \n             [[[end]]]", "breadcrumbs": "[\"Facets\"]", "references": "[]"}