publiclab / wherewebreathe

wherewebreathe.org
2 stars 7 forks source link

Question Flow #18

Closed mmnoo closed 9 years ago

mmnoo commented 10 years ago

For the specific symptoms questions*, can they be combined to flow something like in the following image? symptomsquestion

jywarren commented 10 years ago

This looks good - @shapironick, does this jive with how you see questions connecting with each other?

Melissa - could you jot down the columns you think the Question table would have -- a schema, sort of? Because i'm thinking this might imply that each question has a "next_question_id" field, or perhaps even something like:

question = {
  id: 35,
  type: "multiple-choice",
  set: "health-issues",
  answers: [
      {
        text: "cats",
        leads_to: 235,
      },
      {
        text: "not cats",
        leads_to: 236,
      },
    ]
}
shapironick commented 10 years ago

Looks good. Just forwarded it to Nicole--who's our study design guru--and she said "ooh yeah, that's great. there is also the onset question, that could go in that too." Maybe onset before abatement?

She's not following all the project as it would flood her with more emails than she would need to see so if you have a question just @ her at novakn

On Tue, Jul 1, 2014 at 9:35 PM, Jeffrey Warren notifications@github.com wrote:

This looks good - @shapironick, does this jive with how you see questions connecting with each other?

Melissa - could you jot down the columns you think the Question table would have -- a schema, sort of? Because i'm thinking this might imply that each question has a "next_question_id" field, or perhaps even something like:

question = { id: 35, type: "multiple-choice", set: "health-issues", answers: [ { text: "cats", leads_to: 235, }, { text: "not cats", leads_to: 236, }, ] }

On Tue, Jul 1, 2014 at 4:26 PM, Melissa notifications@github.com wrote:

For the specific symptoms questions*, can they be combined to flow something like in the following image? [image: symptomsquestion] < https://cloud.githubusercontent.com/assets/1740152/3448790/da48eb52-015d-11e4-8bd9-812bacd12bc5.png>

  • from the Google Survey:

https://docs.google.com/forms/d/1BvjKvH5dUFNjhhDdA4NNtsTHiXgurjJN3-c72mcrvFM/viewform

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

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/18#issuecomment-47706706 .

mmnoo commented 10 years ago

@jywarren, working on what you are suggesting, I would possibly create a question table/collection for specific symptoms something like so: Questions { id: 35, type: "multiple-choice-conditional-followup", set: "health-issues", label: "During the past three months, have you experienced fatigue?", answers: [ { text: "Yes, often (every week)", leads_to: 300, }, { text: "Yes, sometimes", leads_to: 300, }, { text: "No, Never", leads_to: 36, } ] } { id: 300, type: "multiple-choice-conditional-followup", set: "health-issues", label: "Do you think your fatigue is due to your home environment?", answers: [ { text: "Yes", leads_to: 301, }, { text: "No", leads_to: 36, } ] } { id: 301, type: "multiple-choice", set: "health-issues", label: "How much time do you have to spend outside of your home to alleviate your fatigue?", answers: [ "A few minutes", "1 hour", "at least 1 day", "at least 2 hours", "at least one week", "this symptom doesn't go away"] } { id: 36, type: "multiple-choice-conditional-followup", set: "health-issues", label: "During the past three months, have you experienced feeling heavy-headed?", answers: [ { text: "Yes, often (every week)", leads_to: 302, }, { text: "Yes, sometimes", leads_to: 302, }, { text: "No, Never", leads_to: 37, } ] } etc.

This is assuming that there wont be hundreds of questions, otherwise I would definitely do something to deal with the redundancy issue created by the question labels and answers in the above schema.

@novakn @shapironick How many questions would the questionnaire have maximum?

mmnoo commented 10 years ago

@shapironick in terms of your onset before abatement comment, are you suggesting there also be a question like: "How much time do you spend in your home environment before you start to feel fatigued?

shapironick commented 10 years ago

In terms of max questions the phase 2 version of the survey is about 50 questions long. I don't think it could get longer than 75. So i don't think it will get to be hundreds. But down the line some of the questions will be repeated as their symptoms change over time.

I guess nicole was refering to the longer version of the survey in which there is a "How soon after moving into the unit did this person begin to notice any of the following symptoms?" question. I think your current contract is just for the short one, so I've just shared the doc for the long survey as a heads up.

On Tue, Jul 1, 2014 at 10:31 PM, Melissa notifications@github.com wrote:

@shapironick https://github.com/shapironick in terms of your onset before abatement comment, are you suggesting there also be a question like: "How much time do you spend in your home environment before you start to feel fatigued?

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/18#issuecomment-47712393 .

mmnoo commented 10 years ago

Reflecting a bit on the wireframe for question flow above. I think that will be ideal for a desktop experience, but in testing our current dev site on my phone, I am wondering if what we currently have (questions asked one-by-one) is better if we account for a mobile experience...

On a phone, its nice that the whole question fits the screen. If we dynamically expand the page to include other question parts, users might not notice, or become frustrated in that itself. I wonder if for mobile design, keeping things as simple as possible is a good goal....

Thoughts?

(Also discussed in #46)