Custom Surveys for Washington Commons Project

[Abby-Wheelis]

We're working with the Washington commons project to implement their custom surveys.

Right now I have the xls and xml files for the surveys they sent over. I have noted some extra options in the demographic survey that might be a mistake, so I need to ask about those and make sure the survey is final before I go through with getting the json files, since those are more labor intensive to generate.

[Abby-Wheelis]

I have tested this out by loading in the emulator:

• saw custom demographics survey instead of default
• trip labels with custom survey
• when survey is filled, the "1 mode, 1 purpose" text will show in the label

[Abby-Wheelis]

I went through the spreadsheets, updated names that were still "option_x" and several that were confusing -- some of the onboarding questions were using the same keys for options in questions that were very different

The names should all be intuitive now, and match the labels they represent

[shankari]

This is the first one, so it is OK to be so hands-on. But I do wonder what, if anything, we can do to clean up when we scale. We can't do this for every partnership, I think. Should we just allow them to ahead with the bad option labels, and let them find it in testing? Should we include this in validation?

[Abby-Wheelis]

We're going to have to make sure that the path to the surveys is valid, and if a trip survey there is a way to populate the text in the button after the user labels (this was one of the things that took some testing). I think that anything we can do to validate or run it against some phone tests is going to be very helpful.

We can try and validate that nothing is the "option_X" labels, but that won't catch the ones that were just 'weird' like I found in the spreadsheet. Some of it will probably fall to testing and we can try and warn people -- maybe put some instructions for writing surveys somewhere?