How is OCDS data published?¶
Open Contracting Data Standard (OCDS) data is published and updated over time using two JSON document types: “releases” and “records”. This page will:
Outline the purpose of releases and records
Describe how to publish a change history using releases and records
Show the components of an OCDS record
The only thing that can be truly called “OCDS data” is a JSON document that validates against the OCDS schema. The JSON documents that OCDS uses are called “releases” and “records.”
OCDS publishers are encouraged to use releases and records to publish data in near real-time and to provide a change history. Tracking change over time is important to users of contracting data because there can be many changes in the life of a contracting process. Knowing how and when certain attributes have changed can help users to understand the process, identify inefficiencies, and spot red flags for corruption.
Releases are JSON documents that are published each time there is a change to a contracting process. Releases follow the OCDS release schema and contain an OCID to identify the contracting process they relate to.
Releases are immutable, which means they cannot be changed once published. There can be many releases per contracting process and the collection of releases for a contracting process constitutes its change history.
Records are JSON documents that act as an index of all releases for a single contracting process. While releases are never updated, records are updated each time there is a change to a contracting process by adding a new release to this index. Records follow the OCDS record schema and, in addition to the release index, can also contain:
A compiled release, which follows the same structure as a release and provides the latest value of each field. The compiled release makes it easy for users to get the latest version of the data about a contracting process.
A versioned release, which contains a history of changes for each field and allows users to see how a particular field has changed over time.
Each time a new release is published it is added to the index, the compiled release is updated with the latest values, and the versioned release is updated with any new changes.
Records and releases each contain several fields which can be used in different sections. The OCDS schema sets out the fields that ought to be included in each section (where applicable), aiming to reuse simple structures to represent information. For example, a release may contain information about items being procured. OCDS’ schema sets out standard building blocks for items across releases, including the name of the item, a description, each item’s value, and the currency used.
When you publish OCDS releases and records, you are encouraged to:
Ensure all documents referenced in OCDS releases are available online
Publish each release and record at its own persistent URL
Produce bulk packages of releases and records for users to download
Publish versions of the data for users to access in CSV for Excel formats
To learn more, go to the next page in the primer: How can I implement the OCDS? You can also review the further resources below to go deeper into the subjects introduced on this page.