Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planning final status codelist #1583

Closed
jpmckinney opened this issue Dec 20, 2022 · 2 comments · Fixed by #1642
Closed

Planning final status codelist #1583

jpmckinney opened this issue Dec 20, 2022 · 2 comments · Fixed by #1642
Assignees
Labels
Schema: Fields Relating to adding or deprecating fields in the JSON Schema
Milestone

Comments

@jpmckinney
Copy link
Member

jpmckinney commented Dec 20, 2022

Related: #1160 CRM-8486

A buyer can publish a notice about a future procurement, and then later decide to not follow through on that future procurement.

The model needs to be able to disambiguate whether it's the planning process itself that is cancelled, or the future (non-existent) process. The tricky part is that it's hard to make a statement about something that doesn't exist; we can't mint an OCID for the contracting process and then set its tender/status to 'cancelled', because that implies that the contracting process had at least a minimal existence.

After #1160 and #1582, we can add planning/finalStatus and planning/finalStatusDate, with one code being 'cancelled' (as in the buyer didn't go ahead with the planning process, e.g. to hold consultations for a new recreational facility, which it then decided not to go ahead with) and 'unsuccessful' (as in the planning process didn't yield a contracting process).

@jpmckinney jpmckinney added the Schema: Fields Relating to adding or deprecating fields in the JSON Schema label Dec 20, 2022
@jpmckinney jpmckinney added this to the 1.2.0 milestone Dec 20, 2022
@duncandewhurst duncandewhurst self-assigned this Oct 9, 2023
@duncandewhurst duncandewhurst added the blocked We can't merge this yet label Oct 12, 2023
@duncandewhurst
Copy link
Contributor

Blocked until #1160 is done. Can be done at the same time as #1582

@jpmckinney
Copy link
Member Author

Unblocked

@jpmckinney jpmckinney removed the blocked We can't merge this yet label Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Schema: Fields Relating to adding or deprecating fields in the JSON Schema
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants