-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add duration of events and contacts #4
Comments
Hi David, Thank you. I am very happy knowing that you find the app useful :) I have had some thoughts about this. Asking for more information about the contacts is a bit tricky. The premise I use is that it must be a professional contact tracer who assesses whether a contact is risky enough, instead of the individual using the app. Adding too much information about a contact may incline to self-evaluation of contacts, and to thoughts of "well, this contact doesn't seem of enough risk, so I won't tell the contact tracer". That is part of the reason why, right now, there is no question about mask use, for example. That being said, it is true that it feels a bit weird to ask for a beginning time and not for an end time. Also, it is possible that knowing whether a meeting lasted 30 minutes or 2 hours is useful for the contact tracers to assess the risk in certain situations (although this is typically easy to remember once you remember the meeting happened, if you had forgotten). Finally, I have been asked for this a few times already. So I think I will add the contact end time. |
I agree, an end time field will be useful for sure! If you have doubts that this will make people not log shorter events, maybe consider adding a check box or an alternative end value for 'short contact'. I believe this option may even motivate to log short contacts |
Don't think I have forgotten about this. I am still thinking about it ;) I agree that just setting a beginning time is useless. In fact, now it is just used for ordering the table. But also, it is irrelevant to know at which period of the day the contact occurred. What actually seems to matter is the duration of the contact. I am thus now considering removing the Time field, and substituting it by a Duration field. Would you mind sharing your thoughts (if any) about this? |
Yeah, I think that makes sense. I guess knowing the exact time of a contact is only relevant in case you meet two or more people on the same day at different times and one of them is infected. Then you may want to know whom of the other people you met before and whom after. But in that case I believe it's very likely that you'll A: still remember who you met first without writing it down and/or B: just inform all people you met on that day. |
Sounds good! Looking forward to seeing it in the app |
Hi, |
Hi, After playing a bit with the Duration feature, I admit that I myself also liked the way of entering times better. Therefore, in the next version I will come back to inserting times, with the ability to insert a beginning and an ending time. Also, no fields will be compulsory except for the name (the bare minimum). I have arrived to the realization that I/the app should not assume responsibilities on what the users input (see also the discussion in #14). |
Hi!
First, I really like the app and I really appreciate the time and effort that has been put into its development so far!
Regarding the tracking of time, I think it would be good to add an end time and separate it from the default start time of an event or contact. I think the duration is useful information for contact tracing in public spaces and it can be used as a factor in classifying the intensity of a contact.
The text was updated successfully, but these errors were encountered: