
Guideline 13 asks open data policies to require a common, fully described metadata scheme so each data set explains what it contains, how it was created, how current it is and how it can be used.
What metadata does
Metadata is data about data: the title, description, owner, update frequency, field definitions, geographic coverage and date range of a data set. Without it, users cannot judge whether data fits their purpose or how to interpret it.
The guideline recommends a common scheme across all agencies, ideally aligned with international vocabularies such as DCAT. Consistent fields help the public search catalogs, help governments share data internally, and let software discover data sets automatically.
How policies typically phrase it
- A requirement that each published data set include minimum metadata.
- Specific required fields, such as publication date, last update and whether the data is primary or aggregated.
- Field-level descriptions, sometimes called a data dictionary.
- Delegation of the metadata schema to technical standards.
Places whose policies adopted it
Cook County's 2011 ordinance is an early example, requiring its catalog to show whether information is public, when it was published and last updated, and whether it is primary or modified. Minneapolis's 2014 ordinance asks departments to describe data fields and meet minimum metadata requirements explaining how and when data was collected. Boston's 2014 executive order calls for minimum documentation standards.
Other tagged examples include Chicago, Montgomery County, Nashville and Washington, DC (2014).
Common pitfalls
- Title-only metadata, which tells users almost nothing.
- No field definitions, so column names remain cryptic.
- Stale update dates, which erode trust in the whole catalog.
A minimum metadata set
Most technical standards for municipal portals settle on a short list of required fields, with more detail encouraged. A reasonable minimum is:
- Title and plain-language description.
- Publishing department and a contact point.
- Date first published and date last updated.
- Update frequency and temporal coverage.
- Geographic coverage and spatial unit.
- Field-level definitions (a data dictionary).
- License or public domain statement.
- Notes on known limitations or methodology.
Aligning these fields with a common vocabulary such as DCAT or the Project Open Data schema lets catalogs be harvested by regional, state and national aggregators. Equally important is keeping metadata current; an update date that is months out of step with the data undermines confidence in the whole portal, so many policies assign metadata upkeep to the same steward who maintains the data.
Why this matters for your business data
Documentation is one of the cheapest ways to raise the value of operational data. A buyer evaluating a data set needs to know what each field means, how far back it goes and how often it refreshes. Well-documented data sells faster and for more.
Use the valuation calculator to see how completeness affects value, and read how to value my data. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
What metadata should every open data set have?
Typically a title, description, owning agency, contact, publication and update dates, update frequency, coverage period, geographic scope and definitions for each field.
What is DCAT?
DCAT (Data Catalog Vocabulary) is a W3C standard for describing data sets in catalogs. Aligning with it helps catalogs interoperate and lets search tools discover data automatically.
Is a data dictionary part of metadata?
Yes. A data dictionary describes each field in a data set and is one of the most useful forms of metadata for people analyzing the data.
Policies in the index that reflect guideline 13
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Washington, DC | Jun 12, 2006 | Executive memorandum | 1131822 |
| Cook County, IL | May 4, 2011 | Ordinance | 12378131825 |
| Madison, WI | Aug 15, 2012 | Ordinance | 457810111318 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| Montgomery County, MD | Dec 17, 2012 | County legislation (Bill 23-12, Open Data Act) | 457811131822 |
| Oakland, CA | Oct 15, 2013 | Council resolution (No. 84659) | 2345781011 |
| Boston, MA | Apr 7, 2014 | Executive order | 3891318202425 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Kansas City, MO | Jun 19, 2014 | Ordinance (No. 140443) | 81018242713 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| Minneapolis, MN | Aug 1, 2014 | Council-adopted policy | 34568131819 |
| Boston, MA | Jul 30, 2015 | Administrative policy | 478132425 |
| Suffolk County, NY | Jul 31, 2015 | Administrative policy | 78131820222426 |
| Cambridge, MA | Sep 21, 2015 | Ordinance | 12345678 |
| Seattle, WA | Feb 1, 2016 | Administrative policy (CTO policy) | 14678101112 |
| Baltimore, MD | Mar 7, 2016 | Ordinance | 1781113182426 |
| San Jose, CA | Apr 5, 2016 | Council policy | 1681113182230 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
| Fort Collins, CO | Feb 7, 2017 | Council resolution | 12345678 |
| Knoxville, TN | May 2, 2017 | Executive order | 14578111319 |
| Syracuse, NY | Jul 26, 2017 | Executive order | 1456781113 |
Sources
Updated December 31, 2024.