Running convert-to-oc4ids on the sample OCDS for PPPs flagged an issue with the automatic mapping from OCDS planning.project.sector (a Classification object) to OC4IDS project.sector (an array of strings).
Although the projectSector codelist is open, the above concatenation of scheme and id loses information because planning.project.sector is a Classification block (although oc4ids /definitions/Classification/properties is currently missing uri).
Where an OCDS project.sector classification object exists, it would be better to map to project.additionalClassifications (as well as anything in planning.project.additionalClassifications), and update documentation to instruct users to additionally manually map to the projectSector codelist and/or link to mapping documentation as updated in OC4IDS standard issue #210.
Running convert-to-oc4ids on the sample OCDS for PPPs flagged an issue with the automatic mapping from OCDS
planning.project.sector
(aClassification
object) to OC4IDSproject.sector
(an array of strings).The code currently concatenates scheme and id:
So transforming OCDS for PPPs data:
Generates:
Although the
projectSector
codelist is open, the above concatenation of scheme and id loses information becauseplanning.project.sector
is aClassification
block (although oc4ids/definitions/Classification/properties
is currently missinguri
).Where an OCDS
project.sector classification
object exists, it would be better to map toproject.additionalClassifications
(as well as anything inplanning.project.additionalClassifications
), and update documentation to instruct users to additionally manually map to theprojectSector
codelist and/or link to mapping documentation as updated in OC4IDS standard issue #210.