Generate MultiRecord Measures for QualityAssurance that return COMPLETE/NOT_COMPLETE for compliant #295
Comments
|
Added label template to allow code that translates markdown tables in issues to csv to exclude this and #296 by filtering on labels: CORE and Test and not Template. |
chicoreus
added a commit
to kurator-org/bdq_issue_to_csv
that referenced
this issue
Aug 13, 2024
…) from translation of markdown tables to csv. Adding lock file pattern to gitignore.
|
CSV list of Core MultiRecord Measure tests generated with kurator-org/bdq_issue_to_csv including assignment of stable guids (list of test labels and guids in https://github.com/kurator-org/bdq_issue_to_csv/blob/master/src/main/resources/multirecord_measure_guids.csv, we can extend this file to mark tests that should accept INTERNAL_PREREQUISIITES_NOT_MET as COMPLIANT. CSV file of tests: https://github.com/tdwg/bdq/blob/master/tg2/core/TG2_multirecord_measure_tests.csv Human readable markdown: https://github.com/tdwg/bdq/blob/master/tg2/core/generation/docs/core_multirecord_measure_tests.md |
|
As suggested by @Tasilee - perhaps a new issue for the exceptions where INTERNAL_PREREQUISITES_NOT_MET other wise the Expected Response is not correct fro those records. |
|
I have corrected FFDQ in the preamble to bdqffdq for consistency with Vocabulary (#152) |
chicoreus
changed the title
|
Per @Tasilee and @ArthurChapman , splitting off a separate issue #297 for measures that allow for empty values and still are complete. |
|
Per @Tasilee a list of these tests:
|
chicoreus
added a commit
that referenced
this issue
Aug 14, 2024
… test specifications as of 2024-08-14. Updating csv spreadsheet and rdf-xml for MultiRecord measures for #295, #297, and #296 generated from the validations after bugfixes in kurator-org/bdq_issue_to_csv and split from two into three issues. Regenerating human readable markdown lists of multirecord measures (no changes to regenerated markdown for other CORE tests).
chicoreus
added a commit
that referenced
this issue
Aug 14, 2024
… test specifications as of 2024-08-14, using the updatd list of issue-usecase mappings. Updating csv spreadsheet and rdf-xml for MultiRecord measures for #295, #297, and #296 generated from the validations using the updated v79 list of issue-usecasse mappings. Regenerating human readable markdown lists of multirecord measures and other CORE tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For a set of Validations, listed below, generate a Measure that operates on a MultiRecord and returns a Response.result of COMPLETE if all records in the MultiRecord have a Response.result of COMPLIANT for a particular Validation.
Template for these would look like this, one for each Validation, specified as {Validation}: Generate from the bdqffdq compliant template instead, to match TG2_tests.csv columns. We don't need to add issues for each, but can track rationale management for this set of tests here.
These Measures expect the Validations to complete to Response.status=RunHasResult and Response.result=COMPLIANT for data to have quality. See #297 for QA measures where some of the prerequisite information elements may be empty and the data still have quality.
The text was updated successfully, but these errors were encountered: