Page MenuHomePhabricator

Run multiple choice quicksurvey about reader motivation.
Closed, DeclinedPublic

Description

Ideal timing: 2015-11-23 to 2015-11-30 (assuming this is NO risk to destabilizing fundraising campaigns starting Dec 1)

We'll be using the same privacy policy that Discovery is using, linked here: https://wikimediafoundation.org/wiki/Quick_Survey_Privacy_Statement

"@question"=> "survey question message key",
		"question"=> "quicksurvey-reading-desc",

		"@description"=> "description of the survey (appears under question)",
		"description" => "quicksurvey-reading-question",

		"@answers"=> "possible answer message keys for positive, neutral, and negative",
		"answers"=> array(
			"neutral"=> "quicksurvey-reading-quick",
			"neutral"=> "quicksurvey-reading-summary",
			"neutral"=> "quicksurvey-reading-depth"
			"neutral"=> "quicksurvey-reading-other"
		),

		"@coverage"=> "percentage of users that will see the survey = .05%",
		"coverage"=> ".005",


		"@platform"=> "for each platform (desktop, mobile), which version of it is targeted (stable, beta, alpha)",
		"platform"=> array(
			"desktop"=> ["stable"],
			"mobile"=> ["stable", "beta", "alpha"]

Event Timeline

atgo raised the priority of this task from to Needs Triage.
atgo updated the task description. (Show Details)
atgo renamed this task from Run multiple choice quicksurvey for reader motivation. to Run multiple choice quicksurvey about reader motivation..Nov 21 2015, 12:22 AM
atgo set Security to None.

Thanks @Deskana. Not sure if case matters, but the messages have title with capital Q and the array I set up with lowercase q. @jhobs lmk if anything needs changing (we can adjust the array without bothering Dan any more).

Thanks @Deskana. Not sure if case matters, but the messages have title with capital Q and the array I set up with lowercase q.

MediaWiki forces the prefixed text of pages to begin with a capital letter, so they have to be created that way. But, you can refer to it elsewhere starting with a lower case letter and it will work just fine. This shouldn't cause you any issues. :-)

Perhaps, but on the other hand it's considered good practice in survey research to preserve the exact wording (and design) of the survey instrument for later analysis.

Also, while these messages are technically stored in the same way as longterm UI messages are, the more relevant comparison concerning existing Wikimedia practices would be with CentralNotice banners (we've discussed before how QuickSurveys has a lot of parallels with CN and might even be merged at some point). For those, the convention is that they are archived instead of deleted after the campaign ends.

This survey will not be able to be run until we've investigated the EventLogging issues. I've updated the description to reflect that the timeline will not be possible. In addition, a custom privacy policy for an internal survey requires @JGirault's patch (254328) to be merged and deployed. It also does not make much sense to SWAT right before a holiday, nor run a survey during such time (potentially skewed results).

Thanks @jhobs. I was thinking that since the privacy policy was the same as
the discovery one (multiple choice) we might be able to make it work. But
no big deal - we'll run in January.

Thanks @jhobs. I was thinking that since the privacy policy was the same as
the discovery one (multiple choice) we might be able to make it work. But
no big deal - we'll run in January.

Discovery won't be able to get theirs to work either until that patch is deployed (unless theirs is an external survey).

Also, we could still potentially run in December, it just depends on the result of that spike and when the patch gets merged & deployed (unless it would interfere with fundraising obviously).

Is this task outdated and should it be closed?

Given that we will be running T125946, we may want close this task, though I'd wait for @atgo to comment as she opened this task for specific needs of the Reading team.

atgo claimed this task.