This task [and its subtasks] is about the work involved with instrumenting both the existing and revised [1] adding/modifying links and citations workflows on mobile, in VE.
Open questions
- How will we be able to interact with the data our instrumentation/event logging is gathering?
- Will we need to oversample Edit events?
- Confirm: As part of this work, we will not be creating any new schema. This question is relevant to the analytics DACI steps (below).
Background
We know what proportion of edits using the visual editor involve using common editing features. [2] We do not yet know how many contributors take which actions within these workflows. We are pursuing instrumentation to help us answer questions related to this second part. Questions like...
- What % of contributors who start to add/modify a link and citation are successful in doing so? How do these proportions compare across the existing and revised workflows?
- This kind of information could be helpful in identifying opportunities to make adjustments that will help these contributors find their way (read: be successful in) adding/modifying links/citations.
- Do "Edit cards" encourage more people to engage more deeply with adding/modifying links and citations?
- Asked another way: "What percentage of contributors who are shown the edit card (revised) or context item (existing) end up engaging with it?"
- What % of edit sessions, in which contributors successfully add/modify a link, result in them attempting to save their edits?" How do the revised and end existing flows compare in this way?
- Do "Edit cards" cause more people to add/modify links and citations more efficiently?
This work sits within our larger effort to improve the mobile edit completion rate. Work that depends on us being able to know what contributors actually do after starting an editing session.
"Done"
| Status | Task | Owners |
| Define research questions instrumentation needs to answer | @ppelberg | |
| Define metrics to be derived from instrumentation | @ppelberg @Neil_P._Quinn_WMF | |
| Define data instrumentation will need to generate | @ppelberg @Neil_P._Quinn_WMF | |
| Confirm instrumentation definition | @DLynch @Neil_P._Quinn_WMF | |
| Define schema and queries and other attributes of the logging | @DLynch @Neil_P._Quinn_WMF | |
| Create queries that will generate results | @Neil_P._Quinn_WMF | |
| Make legal aware that schema privacy review will be needed | @JTannerWMF | |
| Email "privacy@" with link to Phabricator ticket for review | @JTannerWMF | |
| Finalize schema | @DLynch @Neil_P._Quinn_WMF | |
| Implement instrumentation | @DLynch | |
| Test instrumentation | @DLynch @Neil_P._Quinn_WMF @ppelberg | |
| Update data dictionary | @Neil_P._Quinn_WMF | |
| Activate production level logging | @DLynch | |
Instrumentation needs
The instrumentation specification is defined in this doc (publicly commentable).
Resources
- Schema:VisualEditorFeatureUse
- Wireframes: linking w/ contextual inputs
- Mobile context items hypotheses
- Desktop VE feature use
References
- Revised workflows: https://phabricator.wikimedia.org/T221247
- Feature use data: https://www.mediawiki.org/wiki/VisualEditor_on_mobile_report