Comments (8)
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).
from contactdiary.
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.
from contactdiary.
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
from contactdiary.
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.
from contactdiary.
Well, I was unexpectedly busy during these last weeks, but b9603bb and 3069e56 replace the query for time by a question about the duration of the contact. Any feedback is appreciated.
from contactdiary.
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?
from contactdiary.
Sounds good! Looking forward to seeing it in the app
from contactdiary.
Hi,
thank you very much for this nice, useful app. It was what I was looking for.
The reason why I ended up in this discussion is the (now) missing start time. We discussed this in our family and feel that it is a missing information in some situations. The duration is important and should be kept. But having the possibility to optionally enter the start time would be quite important for us.
Not sure what others think about it.
from contactdiary.
Related Issues (20)
- Crowdin Hungarian translation HOT 1
- Crowdin finished many languages HOT 1
- a treat for you, too HOT 1
- [Bug] "Make a copy today" doesn't work in 2021 HOT 2
- [Bug] HOT 2
- App doppelt Begegnungen aus 2020 nicht fΓΌr 2021 HOT 1
- [Bug] When copy contact for today the year is set to 2020 instead of 2021 HOT 1
- [Request] FAB should respond when keyboard is showing HOT 7
- [Bug] App version 1.4.0 crashes on start HOT 9
- [Request] Support sharing of UK NHS Venue QR Code scans HOT 9
- F-Droid Build Fails on versions 1.4.1 and 1.4.2 HOT 2
- Cannot store a contact or event accross different dates HOT 8
- F-Droid build failed HOT 5
- [Bug]F-Droid build failed HOT 2
- [Bug] Since version 1.4.7, the "make a copy today"-button is missing HOT 5
- [Bug] The mobile phone number entered in incorrect format HOT 1
- App store - outdated main screenshot HOT 1
- Saving of end date is incorrect if end time is set afterwards
- To add Hindi translation of in-app text[Request] HOT 2
- F-Droid build failed HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from contactdiary.