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.

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

Decision about visualization of test cases to be applied to fields that provide closed data in case of unlogged usage of the application #9

Open
rcavaliere opened this issue Sep 10, 2024 · 0 comments
Open

Decision about visualization of test cases to be applied to fields that provide closed data in case of unlogged usage of the application #9

rcavaliere opened this issue Sep 10, 2024 · 0 comments
Assignees
@rcavaliere

Comments

@rcavaliere
Copy link
Member

rcavaliere commented Sep 10, 2024 •
edited
Loading

In case of fields related to closed data, we have all records having issues.
In this case, it's not because of technical issues, but data access limitations.

Open question to be solved: should we visualize these errors or find a way to not show them, and just limit the visualization to open data fields?
@rcavaliere rcavaliere converted this from a draft issue Sep 10, 2024
@rcavaliere rcavaliere self-assigned this Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rcavaliere rcavaliere

Labels
None yet
Projects
automated-data-quality-monitoring-tool
Status: Ready
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rcavaliere