search

publiclab / wherewebreathe

wherewebreathe.org
2 stars 7 forks source link

Sneak Peek 2 #31

Closed mmnoo closed 10 years ago

mmnoo commented 10 years ago

Hi guys,

I've updated http://dev.wherewebreathe.org:3000/

Changes since sneak peak 1

(I am a pretty terrible speller and typer, so it would be useful if you keep an extra eye out for spelling errors!)

Questions

@jywarren @shapironick @novakn

jywarren commented 10 years ago

Awesome Melissa - i'll answer at greater length soon but wanted to say thanks and I also left a few minor issues after trying it out.

On Fri, Jul 25, 2014 at 5:47 PM, Melissa notifications@github.com wrote:

Hi guys,

I've updated http://dev.wherewebreathe.org:3000/

Changes since sneak peak 1

  • I've 'finished' the logic for the questionnaire. Not all of the questions are asked yet, and that will be one of the things that I will be working on next. Follow up questions based on the answers to other questions now work, and users are also now able to go back and answer questions they have skipped once they reach the end of the survey. Answers are also validated both on client and server side of things.
  • Knowledge base page's copy test is now there and links an pdfs are now hooked up.

(I am a pretty terrible speller and typer, so it would be useful if you keep an extra eye out for spelling errors!)

Questions

  • Is it safe to assume that we will go ahead with a narratives page in some form so that I can start work on that next week? Its one of the last high priority tasks for phase I left for me to do, so I'd like to start it as soon as possible.
  • For year of trailer manufacture, it it safe to assume that we wont be getting answers prior to 1900?
  • I've left zip code's input validation flexible to allow for international users to participate and added a "What is the country of your housing-unit" question. Is that what is wanted?

@jywarren https://github.com/jywarren @shapironick https://github.com/shapironick @novakn https://github.com/novakn

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

jywarren commented 10 years ago

Well we'll certainly be showing people graphed data after they've answered the questions, so I think it's fine to move ahead with that, and the prompt to tell your story there.

shapironick commented 10 years ago

Hi Melissa--the site is looking great! Its feeling clean an smooth. Perfect. I'm a terrible speller too so hopefully others can catch any spelling mistakes.

Regarding your first three questions. 1) The narrative section is a definite. Please do wade into that. 2) Yes 1900 is definitely a safe bet. I think 1950 is the oldest ones we would possibly get. So lets start there. I think the ones we are really concerned about are the ones from the last decade though. 3) I assumed that this project would be specifically about the US. But there are housing units of concearn in other countries. They would probably not have VIN numbers and def not HUD numbers (as that's a US department of government) so I'm not sure if they would be able to register on the site. Maybe we could have that question in case contaminated US units were sold over seas? there are tons in Canada. and maybe we could have the United States be automatically selected or checked and they could change it to other (this might also leave room for indian nations within the US that would rather identify as autonomous).

Here are some notes about the site. Of course some might be for later.

• The front picture works really well, but I wonder if it would be possible to have more of the home visible, so it can be a little more immediately recognizable. Even if the crest of the roof can’t fit. It would be nice to be able to see the window. o The test along the asphalt works well but maybe the research question could be along the top in the trees and the join WWB could be along the bottom? • Maybe the first thing should be to identify the broad user group and the top question above the photo could be “Do you live in a mobile home?” And we could combine that with a statement of the problem, so the top question could be “Do you live in a mobile home? Did you know that studies have shown that manufactured housing to have elevated levels of formaldehyde, compared to site-built homes?” That would then lead into the photo and the question more smoothly. o Also the first sentence above the photo and the first sentence in the text box are slightly repetitive. The broadness of the second version I think is helpful on the first page and maybe “Sharing your story towards a better public understanding of indoor air quality health issues” is more of a motto that one needs to first understand who the “you” is and why air quality is an important issue for them. I think it’s a good motto and could maybe go in the footer. • Should we first identify ourselves as simply as possible? So perhaps instead of identifying ourselves as Public Lab and various universities we could first say that “Where We Breath is asking” and we can put PL and universities into the footer, if we need to have that on the front page. At that point in their reading of the website I’m not sure that they will have an understanding of what WWB is and they will maybe be reticent to join what they don’t understand. • Maybe we could rephrase the research question to say “Where We Breathe is website where manufactured home residents can work with our research team towards answering the question: How does formaldehyde exposure affect the residents of manufactured homes?” I think the “how” is perhaps more engaging than the yes/no way that we are currently posing the question. • Use this site to share information about indoor air quality health issues and read others' stories.” • Should we mention the tools we bring to the problem? We cover the user group, and the problem but not our tools, which might be the last part of the triad.

Sign in

Maybe we could have something more welcoming at the beginning of the sign in page as it begins now with warnings. “Thank you for interest in Where We Breathe!” [[I’m a little exclamation mark prone, feel free to tame that grammatical enthusiasm whenever]]

Please add a “I am at least 18 years of age” Check box under the VIN/HUD number box (this is for ethical review purposes).

I think we should move the text down to above the submit button and much of that text can be in the privacy page and not on the sign in page. How about the following text:

“To create a safe space for sharing health information please ensure that your username does not reveal your real name, address, or contact information. On the site, please be careful about not sharing potentially identifying information.”

We work hard to keep your data secure and we will never share your email address, password or VIN/HUD number with anyone.”

Also the “need help finding your VIN or HUD?” feels a little far away. Maybe we could have that in parentheses next to VIN or HUD.

Also could the help text say “need help finding your VIN or HUD number?”

On the Desired Username question: in the help text it would be great if it could say something about no spaces in addition to what it already says if you break the rules of the user name.

That’s all I can do for now as when I register I don’t get the verification link.

About

• Put acronym of Where We Breathe in parentheses after its first usage (WWB) as we use the acronym later in the page. • Change “help the exposed explore mitigation options” to “help those with elevated chemical levels explore mitigation options.”
• This sentence “The project is run out of Public Lab, a grassroots environmental monitoring non-profit based in New Orleans, and is funded by the Passport Foundation.” Could be moved up to be the second paragraph, as we refer to “we” in the later in the page and also because we may remove PL from a central mention on the front page. • “Click hereto” a space should be added and hyperlink added to the privacy page. • “Nicole Novak, Epidemiological:” Seems to be missing something. Maybe “Nicole Novak, is our lead epidemiologist.” And to make the bios more uniform we could change “Ellen (Stevie) Lewis, Outreach Manager” to “Ellen (Stevie) Lewis, Leads our community outreach. She is the Outreach Manager at Public Lab…”

jywarren commented 10 years ago

Just getting through these, but could you create new issues for each of them so the conversations are threaded? Thanks, Nick!

shapironick commented 10 years ago

Hey Jeff--I put them into their original threads where they fit in or new threads where they didn't. Hope that's ok. I can just make new threads for them all if that is preferable.

On Mon, Jul 28, 2014 at 6:23 PM, Jeffrey Warren notifications@github.com wrote:

Just getting through these, but could you create new issues for each of them so the conversations are threaded? Thanks, Nick!

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

mmnoo commented 10 years ago

I'd say if its a bug (like the verification email not being sent), make it a new issue regardless of how its categorized. Then we can close it when fixed even if other parts of its category's discussion are still being discussed.

If its something that is still in discussion like copy, or design, maybe keep it in old threads, and tag me when there is an ask (so my contract time doesnt get gobbled up in communications). I'm going to unfollow any conversations like that to limit distractions for myself, so please tag me on bugs, things I need to see, or specific instructions for me. (Its my first time collaborating via GitHub, so please le tme know if that sounds unreasonable or like something that doesnt make sense!)

jywarren commented 10 years ago

This sounds good. many of the issues don't need immediate response or work from Melissa, or only will after the functional parts of the site are done. We may eventually create new issues and tag them "content" or "design" to indicate that they're not part of Melissa's base responsibilities for functionality, but will be addressed after the site's otherwise done. Thanks!

On Mon, Jul 28, 2014 at 2:25 PM, Melissa notifications@github.com wrote:

I'd say if its a bug (like the verification email not being sent), make it a new issue regardless of how its categorized. Then we can close it when fixed even if other parts of its category's discussion are still being discussed.

If its something that is still in discussion like copy, or design, maybe keep it in old threads, and tag me when there is an ask (so my contract time doesnt get gobbled up in communications). I'm going to unfollow any conversations like that to limit distractions for myself, so please tag me on bugs, things I need to see, or specific instructions for me. (Its my first time collaborating via GitHub, so please le tme know if that sounds unreasonable or like something that doesnt make sense!)

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

shapironick commented 10 years ago

Great! Thanks and will do. This is my first time on GitHub as well, slowly learning the ropes.

On Mon, Jul 28, 2014 at 9:09 PM, Jeffrey Warren notifications@github.com wrote:

This sounds good. many of the issues don't need immediate response or work from Melissa, or only will after the functional parts of the site are done. We may eventually create new issues and tag them "content" or "design" to indicate that they're not part of Melissa's base responsibilities for functionality, but will be addressed after the site's otherwise done. Thanks!

On Mon, Jul 28, 2014 at 2:25 PM, Melissa notifications@github.com wrote:

I'd say if its a bug (like the verification email not being sent), make it a new issue regardless of how its categorized. Then we can close it when fixed even if other parts of its category's discussion are still being discussed.

If its something that is still in discussion like copy, or design, maybe keep it in old threads, and tag me when there is an ask (so my contract time doesnt get gobbled up in communications). I'm going to unfollow any conversations like that to limit distractions for myself, so please tag me on bugs, things I need to see, or specific instructions for me. (Its my first time collaborating via GitHub, so please le tme know if that sounds unreasonable or like something that doesnt make sense!)

— Reply to this email directly or view it on GitHub < https://github.com/publiclab/wherewebreathe/issues/31#issuecomment-50377872>

.

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