You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
jpmckinney
changed the title
Add an additionnal check to catch the releases with same ocid and same date
Add an additional check to catch the releases with same ocid and same date
Aug 18, 2021
jpmckinney
changed the title
Add an additional check to catch the releases with same ocid and same date
Additional check: Releases with same date for given ocid
Jul 7, 2023
If two releases or more with the same
ocid
anddate
, should the tool return a warning?Follow up of open-contracting/standard#848
cc @duncandewhurst @jpmckinney
The text was updated successfully, but these errors were encountered: