Publishing Open Contracting data involves making a number of choices about what data and documents to include and how to classify and categorize different items. To allow users to understand the choices that a publisher has made, a publisher ought to provide a public web page or document that details the decisions they have made concerning the issues listed below.
This document ought to also contain information about future plans for changes to the data and who to contact with enquiries about the data.
Publication policy pages ought to include information about:
- Who is responsible for providing this data - including appropriate contact details and locations of where to offer feedback.
- How the data is generated, and how often - for example, a brief summary describing the systems the data is generated from, how often the source data is updated, and any processes that operate between the source data and the published open contracting data and documents.
- Any exclusions from the data - such as information which is not disclosed for reasons of privacy and security. This can describe the fields which are excluded for a selection of records, and/or the policy applied to decide if any information is withheld from a public OCDS release.
- Any custom codelists used - or custom codes added to existing codelists.
- Future development plans - brief notes on the future plans of the publisher to improve their data.
Publishers might also wish to apply for, and include the results of, an Open Data Certificate, on their publication policy pages.
A link to the publication policy ought to be embedded within the release package or record package.