Skip to content

Commit

Permalink
schema: Reword planningFinalStatus descriptions. Add planning.finalSt…
Browse files Browse the repository at this point in the history
…atusDetails. Remove object name from field names. Order array fields last.
  • Loading branch information
jpmckinney committed May 4, 2024
1 parent 68c763a commit f9b3138
Show file tree
Hide file tree
Showing 3 changed files with 29 additions and 21 deletions.
2 changes: 1 addition & 1 deletion docs/history/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ Per the [normative and non-normative content and changes policy](../governance/n

* Add new fields:
* [#1335](https://github.com/open-contracting/standard/pull/1335) `planning.id`
* [#1642](https://github.com/open-contracting/standard/pull/1642) `planning.finalStatus` and `planning.finalStatusDate`
* [#1642](https://github.com/open-contracting/standard/pull/1642) `planning.finalStatus`, `planning.finalStatusDetails` and `planning.finalStatusDate`
* [#1324](https://github.com/open-contracting/standard/pull/1324) `tender.datePublished`
* [#1296](https://github.com/open-contracting/standard/pull/1296) [#1674](https://github.com/open-contracting/standard/pull/1674) `tender.exclusionGrounds`
* [#1669](https://github.com/open-contracting/standard/pull/1669) `tender.expressionOfInterestDeadline`
Expand Down
4 changes: 2 additions & 2 deletions schema/codelists/planningFinalStatus.csv
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
Code,Title,Description
cancelled,Cancelled,"The planning process was cancelled and did not yield a contracting process. For example, a buyer did not go ahead with planned consultations about the construction of a new recreational facility and decided not to build the facility."
unsuccessful,Unsuccessful,"The planning process is complete, but did not yield a contracting process. For example, a buyer completed consultations about the construction of a new recreational facility, but decided not to build the facility."
cancelled,Cancelled,"The planning process was cancelled by the buyer or the procuring entity (for example, because of a change in needs, insufficient funds, or technical or procedural errors) before any contracting process was planned successfully."
unsuccessful,Unsuccessful,"The planning process failed (for example, because stakeholders rejected the proposed purchase) before any contracting process was planned successfully."
44 changes: 26 additions & 18 deletions schema/release-schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -163,24 +163,8 @@
"description": "Details of the budget that will fund the future contract(s)",
"$ref": "#/definitions/Budget"
},
"documents": {
"title": "Documents",
"description": "Documents related to the planning process (for example, notices, needs assessments and market studies).",
"type": "array",
"items": {
"$ref": "#/definitions/Document"
}
},
"milestones": {
"title": "Planning milestones",
"description": "Milestones associated with the planning process.",
"type": "array",
"items": {
"$ref": "#/definitions/Milestone"
}
},
"finalStatus": {
"title": "Planning final status",
"title": "Final status",
"description": "The final status of the planning process, using the closed [planningFinalStatus](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#planning-final-status) codelist.",
"type": [
"string",
Expand All @@ -194,14 +178,38 @@
null
]
},
"finalStatusDetails": {
"title": "Final status details",
"description": "Additional details on the final status of the planning process. This field can be used to provide the local name of the final status.",
"type": [
"string",
"null"
]
},
"finalStatusDate": {
"title": "Planning final status date",
"title": "Final status date",
"description": "The date on which the planning process reached its final status.",
"format": "date-time",
"type": [
"string",
"null"
]
},
"documents": {
"title": "Documents",
"description": "Documents related to the planning process (for example, notices, needs assessments and market studies).",
"type": "array",
"items": {
"$ref": "#/definitions/Document"
}
},
"milestones": {
"title": "Planning milestones",
"description": "Milestones associated with the planning process.",
"type": "array",
"items": {
"$ref": "#/definitions/Milestone"
}
}
}
},
Expand Down

0 comments on commit f9b3138

Please sign in to comment.