compile-releases: Add support for versioned releases

open-contracting / kingfisher-process

Stores and pre-processes OCDS data in a SQL database

https://kingfisher-process.readthedocs.io

BSD 3-Clause "New" or "Revised" License

2 stars 8 forks source link

compile-releases: Add support for versioned releases #168

Closed jpmckinney closed 2 years ago

jpmckinney commented 5 years ago

Versioned releases make it very easy to perform quality checks on:

whether time-invariant fields are changed (e.g. tender.mainProcurementCategory)
whether time-variant fields are never changed (e.g. contracts.transactions)
whether field values follow a logical progression (e.g. tender.status)

jpmckinney commented 4 years ago

There's a potential optimization for creating both types of merged releases: https://github.com/open-contracting/ocds-merge/issues/27

As such, I think it makes sense for creating versioned releases be an option on the compile-releases step.

We can think through allowing a user to re-run a step with different options (e.g. if compile-releases was already run, the user can run it again with new options, and only new work will be completed).

jpmckinney commented 2 years ago

There has been no demand for versioned releases. The list of Pelican checks includes some checks as in the issue description that are easiest to calculate on versioned releases. If we decide to implement those, then we can return to this issue.