Open ColinMaudry opened 3 years ago
We could do this check here. We have similar uniqueness checks, so it should not be difficult to add. However, implementers only upload one package at a time, and this issue is maybe more likely to occur within a full dataset, rather than in a sample.
Publishers sometimes mistakenly set date
in each release to the date the whole package was generated, so it would be useful to include this check, even at the package level.
Makes sense!
If two releases or more with the same
ocid
anddate
, should the tool return a warning?Follow up of https://github.com/open-contracting/standard/issues/848
cc @duncandewhurst @jpmckinney