General guidance on version upgrades

open-contracting / standard

Documentation of the Open Contracting Data Standard (OCDS)

http://standard.open-contracting.org/

Other

139 stars 46 forks source link

General guidance on version upgrades #1217

Open ColinMaudry opened 3 years ago

ColinMaudry commented 3 years ago

With the release of OCDS 1.2, many data publishers will wonder how to upgrade, the available options, the potential side effects etc.

The revision and upgrade process is well documented in Governance from a standardization point of view, but not from a data publication point of view.

jpmckinney commented 3 years ago

From https://github.com/open-contracting/standard/issues/849#issuecomment-792650512, we can mention the possibility to publish several datasets for different OCDS versions.

Also from #849, we should be clear that when upgrading a source (API, bulk downloads, etc.) then all data from that source should be upgraded to the same version. (Publishers can of course have endpoints/files for different OCDS versions. This just means the same endpoint/file shouldn't mix versions.)

jpmckinney commented 3 years ago

I'm not clear on the distinction made by "general guidance", so I'll mention some specific guidance here.

From https://github.com/open-contracting/standard/issues/866#issuecomment-754939713:

While adopting "planning processes" is optional, we can describe what sorts of changes a publisher would have to make. There is, of course, the separation/re-mapping of a 1.1 process into a 1.2 contracting process and a 1.2 planning process. We should also check planning extensions for any unusual implications (e.g. cross-references from later stages or similar).

jpmckinney commented 1 year ago

Related #862

duncandewhurst commented 12 months ago

Noting that this issue is probably best addressed once we have finalised the other changes made in 1.2.