Page MenuHomePhabricator

Data Validation Android Patroller Tasks
Closed, ResolvedPublic

Description

Schema: app_patroller_experience

Validation
Key Indicator 1: 65% of Target mature audiences that use the tool say they find it helpful for maintaining the quality of wikis and would recommend it to other patrollers
Key Indicator 2: Edits made by mature audiences increase by 5%.
Key Indicator 3: 10% of target mature audiences engage with filter for preferences.
Key Indicator 4: 65% of Target mature audiences engage with the tool at least three times in a thirty day window.
Guardrail: Experienced users without rollback rights, users that have and have not used alternative patrolling tools equally understand the workflow.
Guardrail: We do not receive reports of tool being used to negatively target underrepresented content or contributors based on in-app reporting mechanisms.

Things that would be helpful to know.
How does use of our tool compare to other patrolling tools when looking at MediaWiki Tags (SWViewer, Huggle, and Twinkle).
Do we see an increase in Undo/Rollback/Thank events.
How popular is this task with our target audience relative to other Suggested Edits task?
What actions are most popular in the feature?

User Stories
As a Wikipedia Android app user that has rollback rights, I want to easily fight vandalism while on the train and save my progress, so that I can maintain the quality of wikis while on the go.
As an accomplished experienced editor, I want to learn how to fight vandalism in a low stakes enviornment, so that I can earn admin privileges while still contributing in a way that enhances the quality of wikis, especially about topics that I am well informed about.
Target Quant Regions and Languages.

First Target Wiki

Indonesian.

Next Round Target Wikis
French
Chinese
Spanish

Final Target before full scale
English

Designs
Figma File

Event Timeline

First pass done - waiting for more data - needs more test events: Data validation

Note: @Sharvaniharan getting unexpected output for event action = onboarding_3_accept /active_interface = pt_onboarding. Seeing event text as onboarding_3_Function0<java.lang.String>

Second pass, seeing lots more events - found some issues @Sharvaniharan (highlighted rows here):

Rows with Waiting for data need test events, will try to generate some of these events myself on Test Wiki

actionactive_interfaceissue
undo_successpt_editmissing summary: value in action_data
publish_saved_message_clickpt_warning_messagesmissing message_type: value in action_data
user_info_impressionseeing some events (2) without active_interface value (others are coming in correctly with active_interface values)

Hi @SNowick_WMF

  • The summary and summary_text are getting sent with undo_confirm and the revId is getting sent with undo_success, since that was the best way to send. Will that work?
  • publish_message_click is the one that will get message_type, the publish_saved_message_click event is not expected to have action data.
  • I am seeing correct values for user_info_impression active_interface, so we might need to sync on that - Update to this: I saw an edge case where you could have gotten blank active_interface. Have tightened that code, so shouldnt be anymore.