Write a Spark module to collect survey responses. Filter down to responses to our survey. Push limited demographic information into Spark to validate sampling. Decide how to sum choices, but the most basic method would be to calculate the percentage of individuals who voted for each choice.
Monitor total number of responses and changes in impression and response rate, decide when to end the surveys.
Omit responses submitted internally:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | awight | T256880 Summarize results from the template prototype surveys | |||
| Resolved | Lena_WMDE | T253112 Create survey for TechWish prototype announcements on dewiki and metawiki | |||
| Resolved | awight | T254322 Support new "embedded" survey type | |||
| Resolved | Lena_WMDE | T254224 Remove Do Not Track support for QuickSurveys | |||
| Resolved | Lena_WMDE | T255745 Create survey messages on German Wikipedia | |||
| Resolved | Lena_WMDE | T255969 Create survey messages on Meta wiki | |||
| Resolved | awight | T256200 Debug survey message translation on betawikis |
Requested a new repo, https://gerrit.wikimedia.org/r/admin/repos/analytics/wmde/TW/template-survey mirrored from https://gitlab.com/adamwight/template-survey
Data will be scrubbed after 90 days, so we should anonymize and copy to a less transient table if we might need to revisit these results later.
I think it should be fine to just refresh it one more time before the meeting, so either on the 14th or 17th?
@awight - forgot to mention, we also factored in/discussed these results in relation to priority and community interest. Thanks again for making the gitlab page.
@ECohen_WMDE to answer some of the questions which came up recently,
Thanks so much! Very helpful. And you didn't refresh responses because there were no additional ones right?
Also I agree on the zero votes for 1f - I don't think it's necessarily a clear reflection on how people might feel about the feature but instead a reflection on it's presentation.
Also - is it possible to see the total number of participants, separate from the responses?
Only because I was being lazy, and partially because I felt that the long tail (at least 1 week with no additional responses) could be unfair to include in the response rate. But now I'm thinking, it's worse to "peek" at results and let that affect how analysis is done. I'll recalculate...
... and there's one more survey response in the mailbox as of Monday, thanks for making this suggestion!
The report is refreshed, and now includes a text table with total votes, in case you want to refresh your graphs as well. I could try to port them into the notebook but hesitated because the fidelity would suffer.
Good point, I was completely wrong about the response rate above! I'll update that comment in place, but the bottom line is that we had 9 participants through dewiki and 5 on metawiki. As it turns out there was a session ID included in each row, so this is an accurate estimate of unique individuals.
I still don't have a nice way to deduplicate users between the two groups, I found that the user's session ID is different across each site.
The report is refreshed, and now includes a text table with total votes, in case you want to refresh your graphs as well. I could try to port them into the notebook but hesitated because the fidelity would suffer.
Thanks! And glad to hear we have another response. I took a look at the report though and it doesn't look like any of the numbers have changed?
9 participants through dewiki and 5 on metawiki
This is also great news! Means we ~tripled the number of users we are hearing from through this. Glad there was a way to do this.