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
In OCDS some fields refer to codelists, to limit and standardize the possible values of the fields, in order to promote data interoperability.
Codelists can 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.
Currently, there are three fields in the OCDS publication for Assam that should use close codelists, but they rely on raw / original values instead. These are
Field
Path to Field
Codelist
Additional Values Used
procurementMethod
releases/tender
method.csv
Auction, Global Tenders, Limited, Open Limited, Open Tender, Single
mainProcurementCategory
releases/tender
procurementCategory.csv
Buy, EOI, Empanelment, Fixed-rate, Item Rate, Item Wise, Lump-sum, Multi-stage, PPP-BoT-Annuity, Percentage, Piece-work, QCBS, Supply, Tender cum Auction, Turn-key, Works
status
releases/bids/details
bidStatus.csv
Accepted-AOC, Accepted-Fee/PreQual/Technical, Accepted-Fee/PreQual/Technical/Finance, Accepted-Finance, Accepted-PreQual/Technical, Accepted-Technical, Admitted-Fee/PreQual/Technical, Admitted-Fee/PreQual/Technical/Finance, Admitted-Finance, Admitted-PreQual/Technical, Admitted-Technical, Not Admitted-Fee/PreQual/Technical, Not Admitted-Fee/PreQual/Technical/Finance, Not Admitted-Finance, Not Admitted-Technical, Rejected-AOC, Rejected-Fee, Rejected-Fee/PreQual/Technical, Rejected-Fee/PreQual/Technical/Finance, Rejected-Finance, Rejected-PreQual/Technical, Rejected-Technical
In order to address this issue, we need to map current codes to OCDS codes. We can use Codelist Mapping Template for that.
Same goes for open codelists. While open codelist allow to add additional values, it is still a good idea to map them to OCDS whenever it is possible.
Field
Path to Field
Codelist
Additional Values Used
type
releases/tender/milestones
milestoneType.csv ( + )
Pre-procurement milestones
measure
releases/statistics
statistic.csv
contractValue
What we should keep in mind that when we switch to OCDS codelists, there's gotta be addtional coordination with frontend development. Because while it generally better to use codelists internally, users still should get human readable and clear values on frontend. So we can use codelist mapping to provide users those.
The text was updated successfully, but these errors were encountered:
In OCDS some fields refer to codelists, to limit and standardize the possible values of the fields, in order to promote data interoperability.
Codelists can 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.
Currently, there are three fields in the OCDS publication for Assam that should use close codelists, but they rely on raw / original values instead. These are
In order to address this issue, we need to map current codes to OCDS codes. We can use Codelist Mapping Template for that.
Same goes for open codelists. While open codelist allow to add additional values, it is still a good idea to map them to OCDS whenever it is possible.
What we should keep in mind that when we switch to OCDS codelists, there's gotta be addtional coordination with frontend development. Because while it generally better to use codelists internally, users still should get human readable and clear values on frontend. So we can use codelist mapping to provide users those.
The text was updated successfully, but these errors were encountered: