Codelist reference¶
Some schema fields refer to codelists, to limit and standardize the possible values of the fields, in order to promote data interoperability.
Codelists are either be open or closed. Closed codelists are intended to be comprehensive; for example, the currency codelist covers all currencies in the world. Open codelists are intended to be representative, but not comprehensive.
Publishers must use the codes in the codelists, unless no code is appropriate. If no code is appropriate and the codelist is open, then a publisher may use a new code outside those in the codelist. If no code is appropriate and the codelist is closed, then a publisher should instead create an issue in the OC4IDS GitHub repository.
Extending open codelists
If you use new codes outside those in an open codelist, please create an issue in the OC4IDS GitHub repository, so that the codes can be considered for inclusion in the codelist.
For more information on open and closed codelists, refer to the Open Contracting Data Standard codelists documentation.
OCDS codelists¶
OC4IDS reuses some codelists from the Open Contracting Data Standard and its extensions:
Closed codelists¶
ContractingProcessStatus¶
ContractNature¶
ProjectStatus¶
Projects with a status of 'completed' may be displayed in a list of archived projects.