You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that docs/examples/unsuccessful_tender/tender.json has lots.status = 'unsuccessful' - should the lot extension also be updated following the same logic as the changes to tender?
Yes, please create an issue.
Update docs/examples/unsuccessful_tender/tender.json in the standard. Edit (James): I had added this in March, but looking at it now, I don't think an update is needed (or we did it already). On that page, tenderUpdate.json sets "finalStatus": "unsuccessful".
The text was updated successfully, but these errors were encountered:
@jpmckinney the README of the lots extension contains a section entitled "How to set tender.status if lots' statuses differ?" In 1.2 this field (tender.status) is being deprecated. As we don't have a 1.2 branch for the lot extension I don't think we should update this section to refer to a field that currently only exists in the unpublished 1.2 core schema. Should I instead add a section on "How to set tender.finalStatus if lots' statuses differ?" and note that this is only relevant to publishers using OCDS 1.2?
From open-contracting/standard#1648 (comment):
UpdateEdit (James): I had added this in March, but looking at it now, I don't think an update is needed (or we did it already). On that page,docs/examples/unsuccessful_tender/tender.json
in the standard.tenderUpdate.json
sets"finalStatus": "unsuccessful"
.The text was updated successfully, but these errors were encountered: