Cwa-documentation: Multiple Check-Ins for the same Event (QR-Code) are possible

[jkrwdf]

Avoid duplicates

• [X] Bug is not mentioned in the FAQ
• [ ] Bug is specific for Android only (cannot identify, have only Android)
• [X] Bug is not already reported in another issue

Describe the bug

I can check-in multiple times to the same event, represented by its QR code.
This is obviously not sensible and could be avoided.
See attached screenshot.

Steps to reproduce the issue

Create QR code on one device.
Check in multiple times using another device.

Expected behaviour

I think, re-scanning the same QR code while a check-in for the same QR code is still active should update the existing check-in and prolong its check-in time by the "default check-in time" of the event.

Example: Default check-in time is 2 hours.
I checked in 1 hour ago. I now check in again.
Result: I still have only one active checkin, and it will automatically check out two hours from now.

Less good would be an error message "You are already checked in here".

[Ein-Tim]

Confirm same behavior under iOS.

[jkrwdf]

Thanks.

In addition to the observed behavior, I suggest that when I check-in to another event while I am still checked in to the former event, then this shall automatically check out the former event also, and not keep both check-ins active at the same time.

Assume a venue which has segmented its space into multiple zones (e.g. rooms), and when I change the room, I register in the new room. Obviously, the registration to the former room is then obsolete and can be closed.

[Ein-Tim]

@jkrwdf I suggest that you open a separate feature request for this in the corona-warn-app/cwa-wishlist repository.

[thomasaugsten]

There also some person which visit multiple rooms on an event at the same time. For example waiters or visitor on conferences. We don't want to restrict here to much.

[vaubaehn]

How about if scanning same QR code again, the automatic check out time is added to the remaining time of that event/location?

[jkrwdf]

@vaubaehn I think this suggestion is not as realistic as the approach to set the checkout time of the event in that case to the current time plus 1 times the automatic checkout time. In my initial example, I would have 6 hours otherwise.

[vaubaehn]

@jkrwdf

@vaubaehn I think this suggestion is not as realistic as the approach to set the checkout time of the event in that case to the current time plus 1 times the automatic checkout time. In my initial example, I would have 6 hours otherwise.

True, but I can imagine different use cases, where I would find it comfortable for myself.
What about, if CWA asked you what to do, if you scanned the same QR code again while still being checked in?
Possible options:
-> cancel (dismiss scan/don't check in again)
-> add (automatic checkout) time to remainng time OR fill up remaining time to automatic checkout time
-> modify check in time/remaining time manually (while still being checked in)

If someone found this useful, I'm not sure if this is a bug fix or an enhancement request...

Edit: I missed your suggestion from OP, which is also a nice option.

[dsarkar]

@jkrwdf @vaubaehn @Ein-Tim
I suggest, if you liked to, to you create wishlist items on this topic. Thanks.