Closed yolile closed 3 years ago
Also relevant for analyzing related planning processes (currently used by at least Indonesia Corruption Watch, and likely to become more prevalent under OCDS 1.2)
I have a PR for this now https://github.com/open-contracting/kingfisher-summarize/pull/214
So far I've done the relatedProcesses
within the release object. There's also some within the contract object. Do we want a separate table for those, or is it not useful? (I couldn't find any collections in live kingfisher that had them).
I think the use cases above would not require the one in the contracts array. Once we have a use case, we can consider either adding it to a new table or the same table.
This is now deployed to the kingfisher-process server.
Especially relevant when analyzing FAs related processes, this information is currently only in the JSON column in the
release_summary
table.