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

"Sharing behaviour" graph on CWA Dashboard page needs update #3337

Closed
Ein-Tim opened this issue Jan 19, 2023 · 10 comments
Closed

"Sharing behaviour" graph on CWA Dashboard page needs update #3337

Ein-Tim opened this issue Jan 19, 2023 · 10 comments
Assignees
Labels

Comments

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 19, 2023

Where to find the issue

Describe the issue

There are only two categories, "QR codes" & "teleTANs" but now with version 3.0 we also have self reported warnings. This should be another category.

Suggested change

Make sure that the corresponding data to self reported warnings exist and extend the page.


Internal Tracking ID: EXPOSUREAPP-14614

@Ein-Tim Ein-Tim added the bug Something isn't working label Jan 19, 2023
@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Jan 19, 2023

Hopefully these statistics are already being collected and it is just a question of displaying them as an enhancement.

In the app there are two buttons:

  1. "Positive self-test?"
  2. "Positive test and no result in the app?"

I guess these would be 2 different counters.

(There hasn't been any change to the Solution Architecture document regarding CWA 3.0).

@dsarkar
Copy link
Member

dsarkar commented Jan 20, 2023

Good morning! thanks for the suggestion. We are in contact with the stakeholders about this issue.

@Ein-Tim
Copy link
Contributor Author

Ein-Tim commented Jan 27, 2023

@dsarkar

I'd like to push this issue and urge the team to get this fixed/implemented ASAP.
As we can see on https://www.coronawarn.app/en/analysis/ in the graph "Warnings received by data donors", since January 12 there is a clear trend upwards. It would be really interesting to see how many of these warnings were caused by self reported infections!

@MikeMcC399
Copy link
Contributor

@Ein-Tim

Good observation! I captured the graph for "Warnings received by data donors" beginning Jan 1, 2023:

image

@dsarkar
Copy link
Member

dsarkar commented Jan 27, 2023

Good morning @MikeMcC399 and @Ein-Tim! We are aware of the interest to publish the SRS data on a separate tab on the third graph. The topic was discussed with stakeholders and it is now up to them to get to a decision. Thanks for sharing your thoughts on the topic!

@MikeMcC399
Copy link
Contributor

@dsarkar

Did the stakeholders make a decision? Was it not clear that there would be a need to publish SRS data when it was introduced?

image

@dsarkar
Copy link
Member

dsarkar commented Feb 9, 2023

@MikeMcC399 We are currently evaluating the possibility and options for displaying SRS warnings. Currently, there is no final decision for this feature or a release date.

@MikeMcC399
Copy link
Contributor

@dsarkar

Since March 1, 2023 there is no longer a warning process for OEGD and 10C QR codes. The only method left is "warn without a TAN" and the statistics on https://www.coronawarn.app/en/analysis/ do not include these numbers.

@brianebeling
Copy link
Member

brianebeling commented Mar 6, 2023

@dsarkar

Since March 1, 2023 there is no longer a warning process for OEGD and 10C QR codes. The only method left is "warn without a TAN" and the statistics on https://www.coronawarn.app/en/analysis/ do not include these numbers.

Hi Mike, thanks for the heads-up. We have made the change to include this (and other minor improvements) and want to publish it as soon as possible.

This topic specifically is always a bit delicate and has to receive several rounds of reviews, but everyone involved wants to get this out as soon as possible.

@brianebeling
Copy link
Member

Fixed with #3421

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants