From aaa066d332bfc6f2607715670fbc898c46e798e0 Mon Sep 17 00:00:00 2001 From: odscjen Date: Mon, 20 Nov 2023 16:42:32 +0000 Subject: [PATCH] build/merging.md: correct typos --- docs/guidance/build/merging.md | 2 +- docs/schema/merging.md | 18 +++++++++--------- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/guidance/build/merging.md b/docs/guidance/build/merging.md index 55c276a6e..270ebff3e 100644 --- a/docs/guidance/build/merging.md +++ b/docs/guidance/build/merging.md @@ -21,7 +21,7 @@ Through these individual releases, the agency provides real-time data about the In each release, the agency also updates the record, which combines all the releases to date. In the final record: * The compiled release contains all the information about the opportunity and the tenderers, using the same schema as a release. -* The versioned release makes it easy to see how the provided changed over time. +* The versioned release makes it easy to see how the amount of information provided changed over time. ```{jsoninclude} ../../examples/merging/updates/ghana_tender1.json :jsonpointer: diff --git a/docs/schema/merging.md b/docs/schema/merging.md index fa252ef84..d2754dcbf 100644 --- a/docs/schema/merging.md +++ b/docs/schema/merging.md @@ -43,30 +43,30 @@ To convert a field's value in a release to a **versioned value**, you must: A **versioned value** thus describes a field's value in a specific release. -For example, in the above worked example, the estimated value of the procurement was $1,000 in a release (`tender/value/amount` was `1000`). Following the steps above, the versioned value is: +For example, in the above worked example, the estimated value of the procurement was 13,000 GHS in a release (`tender/value/amount` was `13000`). Following the steps above, the versioned value is: ```json { - "releaseID": "ocds-213czf-000-00002-01-tender", - "releaseDate": "2016-01-01T09:30:00Z", + "releaseID": "ocds-uhveoc-144560-1601380494627-tender", + "releaseDate": "2020-10-21T13:02:26Z", "releaseTag": [ "tender" ], - "value": 1000 + "value": 13000 } ``` In a **versioned release**, with a few exceptions, a field's value is replaced with an array of versioned values, which should be in chronological order by `releaseDate`. -For example, in the above worked example, the estimated value was $1,000 in a release published January 1, 2016 and then $2,000 in a release published February 5, 2016. In a versioned release, this is serialized as below: +For example, in the above worked example, the number of tenderers was 0 in a release published October 21, 2020 and then 2 in a release published November 5, 2020. In a versioned release, this is serialized as below: -```{jsoninclude} ../examples/merging/updates/versioned.json -:jsonpointer: /records/0/versionedRelease/tender/value -:expand: value, amount +```{jsoninclude} ../examples/merging/updates/ghana_versioned.json +:jsonpointer: /records/0/versionedRelease/tender +:expand: numberOfTenderers,releaseTag :title: Versioned_values ``` -```{jsoninclude} ../examples/merging/updates/versioned.json +```{jsoninclude} ../examples/merging/updates/ghana_versioned.json :jsonpointer: :expand: records, versionedRelease :title: Versioned_release