GithubHelp home page GithubHelp logo

Comments (8)

apozas avatar apozas commented on July 29, 2024 2

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.

apozas avatar apozas commented on July 29, 2024 1

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.

leso-kn avatar leso-kn commented on July 29, 2024 1

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.

leso-kn avatar leso-kn commented on July 29, 2024 1

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.

apozas avatar apozas commented on July 29, 2024 1

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.

apozas avatar apozas commented on July 29, 2024

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.

leso-kn avatar leso-kn commented on July 29, 2024

Sounds good! Looking forward to seeing it in the app

from contactdiary.

matthias-vorwerk avatar matthias-vorwerk commented on July 29, 2024

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)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.