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
Comments
Related: https://gitlab.com/datlab/ocp/ocp-data-quality/-/issues/13
|
Done |
Let me know whether it works for you or we should change it in some way |
The first part about >0% and <100% works for me! |
Same here, thanks @hrubyjan! |
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. |
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. |
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. |
There were 3 requests:
|
For example, the 'procuring entity organization reference' check reports no failures on the compiled release screen:
But clicking through to the check shows that there are actually 3 failures:
Similarly, on the field checks screen, if the failure rate is <1% the check reports 100% success.
The text was updated successfully, but these errors were encountered: