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 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
releasesarray within a record (within a record package), along with a compiled release that is identical except for the value of thetagfield.cc @yolile from Skype discussion on 2019-09-09, in case anything else to add.