You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: v1.1/schema.md
+81-46
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ The [Implementation Guidance](/implementation-guide/) available as a part of Pro
41
41
42
42
Where optional fields are included in a catalog file but are unpopulated, they may be represented by a `null` value. They should not be represented by an empty string (`""`).
43
43
44
-
When a record has an `accessURL` or `downloadURL`, they should be contained as objects within a `distribution`. Any object may be described by `title`, `description`, `format`, or `mediaType`, though when an object contains `downloadURL`, it must be accompanied by `mediatype`.
44
+
When a record has an **accessURL** or **downloadURL**, they should be contained as objects within a **distribution**. Any object may be described by **title**, **description**, **format**, or **mediaType**, though when an object contains **downloadURL**, it must be accompanied by **mediaType**.
45
45
46
46
The Project Open Data schema is case sensitive. The schema uses a camel case convention where the first letter of some words within a field are capitalized (usually all words but the first one). While it may seem subtle which characters are uppercase and lowercase, it is necessary to follow the exact same casing as defined in the schema documented here. For example:
47
47
@@ -89,7 +89,7 @@ temporal | Temporal | The range of temporal applicability of a dataset (i.
89
89
90
90
"Common Core" Distribution Fields
91
91
-------------------------------------------
92
-
Within a record, `distribution` is used to aggregate the metadata specific to a dataset's resources (`accessURL` and `downloadURL`), which may be described using the following fields. Each distribution should contain one `accessURL` or `downloadURL`. `downloadURL` should always be accompanied by `mediaType`.
92
+
Within a record, **distribution** is used to aggregate the metadata specific to a dataset's resources (**accessURL** and **downloadURL**), which may be described using the following fields. Each distribution should contain one **accessURL** or **downloadURL**. **downloadURL** should always be accompanied by **mediaType**.
93
93
94
94
{: .table .table-striped}
95
95
Field | Label | Definition
@@ -137,15 +137,6 @@ Further Metadata Field Guidance (alphabetical by field)
137
137
**Usage Notes** | This field refers to degree to which this dataset *could be made available* to the public, regardless of whether it is currently available to the public. For example, if a member of the public can walk into your agency and obtain a dataset, that entry is **public** even if there are no files online. A *restricted public* dataset is one only available under certain conditions or to certain audiences (such as researchers who sign a waiver). A *non-public* dataset is one that could never be made available to the public for privacy, security, or other reasons as determined by your agency.
**Required** | Yes, if the file is accessible indirectly, through means other than direct download.
145
-
**Accepted Values** | String (URL)
146
-
**Usage Notes** | This should be the URL for an indirect means of accessing the data, such as API documentation, a 'wizard' or other graphical interface which is used to generate a download, feed, or a request form for the data. This should not be a **direct** download URL. It is usually assumed that accessURL is an HTML webpage.
**Usage Notes** | Distribution is a concatenation, as appropriate, of the following elements: **accessURL** and **format**. If an entry has only one dataset, enter details for that one; if it has multiple datasets (such as a bulk download and an API), separate entries as seen below:
**Required** | Yes, if the dataset has an **accessURL** or **downloadURL**.
199
+
**Accepted Values** | Array of Objects
200
+
**Usage Notes** | Distribution is a concatenation, as appropriate, of the following elements: **accessURL**, **downloadURL**, **description**, **format**, **mediaType**, and **title**. If an entry has only one form, enter details for that one; if it has multiple forms (such as a bulk download and an API), separate entries as seen below:
**Required** | Yes, if the file is accessible indirectly, through means other than direct download.
230
+
**Accepted Values** | String (URL)
231
+
**Usage Notes** | This should be the URL for an indirect means of accessing the data, such as API documentation, a 'wizard' or other graphical interface which is used to generate a download, feed, or a request form for the data. This should not be a **direct** download URL. It is usually assumed that accessURL is an HTML webpage.
**Required** | Yes, if the file is available for public download.
232
239
**Accepted Values** | String (URL)
233
-
**Usage Notes** | This must be the **direct** download URL. Other means of accessing the dataset should be expressed using **accessURL**.
240
+
**Usage Notes** | This must be the **direct** download URL. Other means of accessing the dataset should be expressed using **accessURL**. This should always be accompanied by **mediaType**.
**Usage Notes** | This should be a human-readable description of the file format of the dataset, that provides useful information that might not be apparent from `mediaType`.
243
259
**Example** | `{"format":"A CSV spreadsheet compressed in a ZIP file."}`
**Required** | Yes, if the file is available for public download.
266
+
**Accepted Values** | String
267
+
**Usage Notes** | This must describe the exact files available at **downloadURL** using [MIME Types](http://en.wikipedia.org/wiki/Internet_media_type). _[Also note [Office Open XML MIME types](http://blogs.msdn.com/b/vsofficedeveloper/archive/2008/05/08/office-2007-open-xml-mime-types.aspx)]_
**Required** | Yes, if the file is available for public download.
322
-
**Accepted Values** | String
323
-
**Usage Notes** | This must describe the exact files available at **downloadURL** using [MIME Types](http://en.wikipedia.org/wiki/Internet_media_type). _[Also note [Office Open XML MIME types](http://blogs.msdn.com/b/vsofficedeveloper/archive/2008/05/08/office-2007-open-xml-mime-types.aspx)]_
@@ -406,7 +432,16 @@ If there is a need to reflect that the dataset is continually updated, ISO 8601
406
432
**Required** | Yes, if applicable
407
433
**Accepted Values** | ISO 8601 Date
408
434
**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start datetime/end datetime} in the [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format. ISO 8601 specifies that datetimes can be formatted in a number of ways, including a simple four-digit year (eg. 2013) to a much more specific YYYY-MM-DDTHH:MM:SSZ, where the T specifies a seperator between the date and time and time is expressed in 24 hour notation in the UTC (Zulu) time zone. (e.g., 2011-02-14T12:00:00Z/2013-07-04T19:34:00Z). Use a solidus ("/") to separate start and end times.
409
-
435
+
436
+
{: .table .table-striped #title}
437
+
**Field [#](#title){: .permalink}** | **title**
438
+
----- | -----
439
+
**Cardinality** | (1,1)
440
+
**Required** | Yes, always
441
+
**Accepted Values** | String
442
+
**Usage Notes** | Acronyms should be avoided.
443
+
**Example** | `{"title":"Types of Vegetables"}`
444
+
410
445
If there is a need to reflect that the dataset is continually updated, ISO 8601 formatting can account for this [with repeating intervals](http://en.wikipedia.org/wiki/ISO_8601#Time_intervals). For instance, updated monthly starting in January 2010 and continuing through the present would be represented as: `R/2010-01/P1M`.
411
446
412
447
Updated every 5 minutes beginning on February 15, 2010 would be represented as: `R/2010-02-15/PT5M`.
0 commit comments