From ae5eb0fe4efd2c11c78be75605ddb4efc5c17d58 Mon Sep 17 00:00:00 2001 From: Duncan Dewhurst Date: Tue, 11 Feb 2025 10:18:40 +1300 Subject: [PATCH] output/mapping/eforms/guidance.yaml: Update BT-200-Contract, OPT-155-LotResult --- output/mapping/eforms/guidance.yaml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/output/mapping/eforms/guidance.yaml b/output/mapping/eforms/guidance.yaml index a56422d..6705f5c 100644 --- a/output/mapping/eforms/guidance.yaml +++ b/output/mapping/eforms/guidance.yaml @@ -6547,11 +6547,12 @@ For each `efac:ChangeReason`, add or update the corresponding `Amendment` object in the contract's `.amendments` array: - Ensure its `.id` is set. The `.id` can be any value guaranteed to be unique within the scope of the procedure. For example, it can be set to a [version 4 UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier), or it can be assigned sequentially across all notices for this procedure (the first notice sets it to "1", the second to "2", etc.). - - Map this field to its `.rationaleClassifications.id`. - - Set its `.rationaleClassifications.scheme` to 'eu-change-corrig-justification'. - - Look up the code's label in the [authority table](https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/modification-justification), and map it to its `.rationaleClassifications.description`. + - Add a `Classification` object to its `.rationaleClassifications` and + - Map this field to its `.id`. + - Set its `.scheme` to 'eu-modification-justification'. + - Look up the code's label in the [authority table](https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/modification-justification), and map it to its `.description`. eForms example: CON-0001add-wssRES-0001CON-0001 - OCDS example: '{"contracts":[{"id":"CON-0001","amendments":[{"id":"1","rationaleClassifications":[{"id":"add-wss","description":"Need for additional works, services or supplies by the original contractor.","scheme":"Modification justification"}]}],"awardID":"RES-0001"}]}' + OCDS example: '{"contracts":[{"id":"CON-0001","amendments":[{"id":"1","rationaleClassifications":[{"id":"add-wss","description":"Need for additional works, services or supplies by the original contractor.","scheme":"eu-modification-justification"}]}],"awardID":"RES-0001"}]}' sdk: https://docs.ted.europa.eu/eforms/latest/schema/contract-modification-notice.html - id: BT-201-Contract parentNodeId: ND-ModificationReason @@ -14803,10 +14804,10 @@ - Set the item's `.id` incrementally. - For each `efbc:StatisticsCode`, add a `Classification` object to the item's `additionalClassifications` array: - Map this field to its `.id`. - - Set its `.scheme` to 'eu-vehicle-category'. + - Set its `.scheme` to 'eu-vehicles'. - Look up the code's label in the [eForms codelist](https://docs.ted.europa.eu/eforms/latest/reference/code-lists/vehicles.html), and map it to its `.description`. eForms example: RES-0001vehicles-zero-emissionLOT-0001 - OCDS example: '{"awards":[{"id":"RES-0001","items":[{"id":"1","additionalClassifications":[{"scheme":"vehicles","id":"vehicles-zero-emission","description":"vehicles zero emission"}]}],"relatedLots":["LOT-0001"]}]}' + OCDS example: '{"awards":[{"id":"RES-0001","items":[{"id":"1","additionalClassifications":[{"scheme":"eu-vehicles","id":"vehicles-zero-emission","description":"vehicles zero emission"}]}],"relatedLots":["LOT-0001"]}]}' sdk: https://docs.ted.europa.eu/eforms/latest/schema/competition-results.html#_lot_result - id: OPT-156-LotResult parentNodeId: ND-ProcurementStatistics