New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Display the severity of checks #56

Open

jpmckinney opened this issue Dec 3, 2019 · 0 comments

Milestone

Member

jpmckinney commented Dec 3, 2019

From this document:

Jan: The resource-level and dataset-level checks have a “check_name” field, and the field-level checks have a “path” field. So, for example, another table can annotate these with metadata like the check’s severity.

In terms of setting the severity of checks, from this document:

JM: the checks spreadsheet has a “Normative in OCDS?” column. To start with, we can set “Yes (MUST)” as the most severe, then “Yes (SHOULD)”, then “No”. For coverage checks, we can have required fields as the most severe.

jpmckinney transferred this issue from open-contracting-archive/pelican

jpmckinney mentioned this issue

Summary of major errors in dataset on overview page #53

Open

jpmckinney added this to the Features milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment