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
The OCDS model works best when publishers create releases to update a contracting process over its lifetime.
However, when publishing historical data (e.g. information about contracting processes that were completed a decade ago), the publisher might only know the final state; they might not be able to reconstruct the timeline.
In this case, the publisher can publish a single release in the releases array within a record (within a record package), along with a compiled release that is identical except for the value of the tag field.
cc @yolile from Skype discussion on 2019-09-09, in case anything else to add.
The text was updated successfully, but these errors were encountered:
jpmckinney
changed the title
Worked example: Publishing historical data, when history can't be reconstructed
Example: Publishing historical data, when history can't be reconstructed
Jun 7, 2023
The OCDS model works best when publishers create releases to update a contracting process over its lifetime.
However, when publishing historical data (e.g. information about contracting processes that were completed a decade ago), the publisher might only know the final state; they might not be able to reconstruct the timeline.
In this case, the publisher can publish a single release in the
releases
array within a record (within a record package), along with a compiled release that is identical except for the value of thetag
field.cc @yolile from Skype discussion on 2019-09-09, in case anything else to add.
The text was updated successfully, but these errors were encountered: