search

publiclab / wherewebreathe

wherewebreathe.org
2 stars 7 forks source link

re-asking questions and changing answers #48

Open jywarren opened 10 years ago

jywarren commented 10 years ago

Moving from #38:

Jeff: @shapironick, do we want to be able to say either "you answered this question x days ago" and "has your answer changed?"

Jeff: Can people go back and change their answers or reanswer them, or delete old answers? Those are three separate approaches, to be precise.

@shapironick: It would definitely be great to have a "have your answers changed?" or more specifically "have your symptoms changed?" because with time symptoms will probably get worse, and having that data on the sequence of symptoms onset reported in near real time would be amazing!

@jywarren: To simplify this, we could invite people to run through a whole question block periodically. I'm going to add to the database design issue to ask if we can have a "repeatable" value on each question, so that we don't re-ask things that won't change. @novakn - how often would some questions need to be re-asked? Can we choose a standard interval to avoid having to record periodicity for each question?

Actual implementation of re-asking questions can probably wait, i just want to know so we can plan for it, possibly in phase 2.

novakn commented 10 years ago

Jeff, just so you know I haven't forgotten: I am looking into literature about the interval for re-surveying participants. I think we will need to record the timing for re-asking questions anyhow because even if we try to re-survey them at standard intervals there will inevitably be some variability. Tentatively, 6 months seems like a good interval.

N

On Fri, Aug 1, 2014 at 10:49 AM, Jeffrey Warren notifications@github.com wrote:

Moving from #38 https://github.com/publiclab/wherewebreathe/issues/38:

Jeff: @shapironick https://github.com/shapironick, do we want to be able to say either "you answered this question x days ago" and "has your answer changed?"

Jeff: Can people go back and change their answers or reanswer them, or delete old answers? Those are three separate approaches, to be precise.

@shapironick https://github.com/shapironick: It would definitely be great to have a "have your answers changed?" or more specifically "have your symptoms changed?" because with time symptoms will probably get worse, and having that data on the sequence of symptoms onset reported in near real time would be amazing!

@jywarren https://github.com/jywarren: To simplify this, we could invite people to run through a whole question block periodically. I'm going to add to the database design issue to ask if we can have a "repeatable" value on each question, so that we don't re-ask things that won't change. @novakn https://github.com/novakn - how often would some questions need to be re-asked? Can we choose a standard interval to avoid having to record periodicity for each question?

Actual implementation of re-asking questions can probably wait, i just want to know so we can plan for it, possibly in phase 2.

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/48.