Skip to content
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.

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

QA Check Report - Consider changing the Full Report from a superset to a complementary set. #9

Open
ldbiz opened this issue Aug 26, 2020 · 0 comments
Assignees
Labels
enhancement QA Check Report Issue relates to the QA Check Report identifying potential w3act issues introduced by users question

Comments

@ldbiz
Copy link
Contributor

ldbiz commented Aug 26, 2020

The report as stands works in two settings:

Core Report - Original spec to highlight potential legal scope and resource issues.
Full Report - Additional QA issues.

The Full Report includes the core report.

It may be more useful for curators to have them as separate result sets (rather than one included in the other); this would give the benefit of the existing setup with the added ability to easily distinguish between the two for work prioritising.

This is a design question for future discussions, and may need a non-trivial change. As it hasn't actually been requested, I'll assume low-priority.

Example (using a hypothetical 1000 row result set)::

Current format
Core Report:
300 Result Rows

Full Report
1000 rows: 300 of them comprising the core results, 700 additional quality issues.

Proposed format:
Core Report
As Above

Complementary Report
700 rows for the additional quality issues.

@ldbiz ldbiz self-assigned this Aug 26, 2020
@ldbiz ldbiz added the QA Check Report Issue relates to the QA Check Report identifying potential w3act issues introduced by users label Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement QA Check Report Issue relates to the QA Check Report identifying potential w3act issues introduced by users question
Projects
None yet
Development

No branches or pull requests

1 participant