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

Report failures <1% #38

Closed
duncandewhurst opened this issue Mar 9, 2020 · 11 comments
Closed

Report failures <1% #38

duncandewhurst opened this issue Mar 9, 2020 · 11 comments
Labels
compiled release checks Relating to compiled release-level check pages
Projects
Milestone

Comments

@duncandewhurst
Copy link

For example, the 'procuring entity organization reference' check reports no failures on the compiled release screen:

image

But clicking through to the check shows that there are actually 3 failures:

image

Similarly, on the field checks screen, if the failure rate is <1% the check reports 100% success.

@jpmckinney
Copy link
Member

Related: https://gitlab.com/datlab/ocp/ocp-data-quality/-/issues/13

UI: Make clear when 0% and 100% are the result of rounding

If 2 out of 10,000 pass, a check will have "0%" pass rate. Similarly, if 9,999 out of 10,000 pass, it will have "100%" pass rate.

However, it's important for an analyst to know whether there are exceptional passes/failures.

One solution might be to use "0%" and "100%" when it is exactly 0 and 100, and to use "~0%" and "~100%" or ">0%" or "<100%" if the number is a result of rounding.

@hrubyjan
Copy link

Done

@hrubyjan
Copy link

Let me know whether it works for you or we should change it in some way

@hrubyjan
Copy link

Sorry there is one more thing I discussed with James. Too many red zeros here. The problem can't be recognized at the first glance. I'm taking the issue back :).
image

@jpmckinney
Copy link
Member

The first part about >0% and <100% works for me!

@duncandewhurst
Copy link
Author

The first part about >0% and <100% works for me!

Same here, thanks @hrubyjan!

@hrubyjan
Copy link

hrubyjan commented Sep 29, 2020

percantage of failures is only displayed when at least some failures exist
image

@jpmckinney
Copy link
Member

Hmm, I remember sometimes getting confused when reading a table for a publisher with very few errors. It is clearer if each cell has a number. I thought we were just going to make values that were exactly zero be a very light grey.

@jpmckinney jpmckinney transferred this issue from open-contracting-archive/pelican Sep 14, 2021
@jpmckinney jpmckinney added the compiled release checks Relating to compiled release-level check pages label Sep 14, 2021
@jpmckinney jpmckinney added this to To do in Pelican via automation Sep 14, 2021
@jpmckinney jpmckinney moved this from To do to In progress in Pelican Sep 14, 2021
@LucyAnne98 LucyAnne98 mentioned this issue Sep 22, 2021
Pelican automation moved this from In progress to Done Oct 2, 2021
@jpmckinney
Copy link
Member

https://dqt.datlab.eu/resource/352

I'd expect that, when it's exactly 0%, that it's the same grey in any column, not just the middle column.

Screen Shot 2021-10-01 at 8 07 32 PM

@jpmckinney jpmckinney reopened this Oct 2, 2021
Pelican automation moved this from Done to In progress Oct 2, 2021
@jakubkrafka
Copy link
Contributor

Well, you originally asked for "... that were exactly zero be a very light grey.":) I'm not trying to "catch you", just double-checking here, as the original idea seems to work nicely here. The zero here is just a "placeholder", to ease the UX, not to transfer any info.

@jpmckinney
Copy link
Member

There were 3 requests:

  1. Use ">0%" and "<100%" if not exactly 0 or exactly 100, because it is relevant to users to know when there are exceptional passes/failures. This was done.
  2. Put a "0%" instead of an empty cell, to make the table easier to read (i.e. it is clearer that there are no passes/failures if they read "0%"). This was done.
  3. Make all "0%" grey, so that it is easier to ignore them and see the more relevant non-zero values. This was only done for the failure column, for some reason?

@jpmckinney jpmckinney added this to the Cleanup milestone Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiled release checks Relating to compiled release-level check pages
Projects
No open projects
Pelican
In progress
Development

No branches or pull requests

5 participants