Change Details

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? == 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. == Instrumentation needs == ===🔗 //Existing// link workflows=== When adding a new link, the feature field should be //link-add//; when editing an existing link, it should be //link-edit-internal// or //link-edit-external//, as the case may be. - A link context item being shown because the user has tapped on a link (action //context-show//) - A link being deleted using the button in the context item (action //clear//) - A link dialog being opened (action //window-open//) - We will distinguish windows opened from the toolbar from windows opened from context items using the feature - With a link dialog open, text being typed or changed in the "search pages" field for the first time since the dialog opened (action //search-pages-input//) - With a link dialog open, text being typed or changed in the "external link" field for the first time since the dialog opened (action //external-link-input//) - With a link dialog open, the dialog being closed using the back arrow (action //abort//) - With a link dialog open, the link being inserted or confirmed by pressing "done" (action //insert-done//) - With a link dialog open, the link being inserted or confirmed by tapping on one of the results from "search pages" (//insert-search-pages//) ===🔗 //Revised// link workflows=== (@Neil_P._Quinn_WMF to finish defining) - When does the context item get shown? - When do contributors tap the "🔗" icon in the toolbar? - When do contributors tap the "unlink" button in the context item? - When do contributors tap the "edit link target" button in the context item? - When do contributors tap the "edit label text" button in the context item? - When do contributors tap the "edit link target" button in the context item? - When do contributors tap into the link search dialog in the link inspector view? - When do contributors tap/select a Wikipedia article link from within the inspector view search results? - When do contributors tap the "Done" button in the link inspector view? ===📚 //Existing// citation workflows=== When adding a new citation, the feature field should be //cite-add//; when editing an existing citation, it should be //cite-edit//. //Where to communicate which citation type? Currently in the feature// (@Neil_P._Quinn_WMF to define) - . - . - . ===📚 //Revised// citation workflows=== (@Neil_P._Quinn_WMF to define) - . - . - . ###Resources - [Schema:VisualEditorFeatureUse](https://meta.wikimedia.org/wiki/Schema:VisualEditorFeatureUse) - [Wireframes: linking w/ contextual inputs](https://wikimedia.invisionapp.com/freehand/document/s1duRw6io) - [Mobile context items hypotheses](https://phabricator.wikimedia.org/T221247) - [Desktop VE feature use](https://docs.google.com/spreadsheets/d/1FZsIZk7ty9xB92TQRBnxdmXpt3vEcWCjxZy0YPt85Nc/edit#gid=0) --- ###References 1. **Revised workflows**: https://phabricator.wikimedia.org/T221247 2. **Feature use data**: https://www.mediawiki.org/wiki/VisualEditor_on_mobile_report

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? == 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. == Instrumentation needs == ===🔗 //Existing// link workflows=== When adding a new link, the feature field should be //link-add//; when editing an existing link, it should be //link-edit-internal// or //link-edit-external//, as the case may be. - A link context item being shown because the user has tapped on a link (action //context-show//) - A link being deleted using the button in the context item (action //clear//) - A link dialog being opened (action //window-open//) - We will distinguish windows opened from the toolbar from windows opened from context items using the feature - With a link dialog open, text being typed or changed in the "search pages" field for the first time since the dialog opened (action //search-pages-input//) - With a link dialog open, text being typed or changed in the "external link" field for the first time since the dialog opened (action //external-link-input//) - With a link dialog open, the dialog being closed using the back arrow (action //abort//) - With a link dialog open, the link being inserted or confirmed by pressing "done" (action //insert-done//) - With a link dialog open, the link being inserted or confirmed by tapping on one of the results from "search pages" (//insert-search-pages//) ===🔗 //Revised// link workflows=== (@Neil_P._Quinn_WMF to finish defining) - When does the context item get shown? - When do contributors tap the "🔗" icon in the toolbar? - When do contributors tap the "unlink" button in the context item? - When do contributors tap the "edit link target" button in the context item? - When do contributors tap the "edit label text" button in the context item? - When do contributors tap the "edit link target" button in the context item? - When do contributors tap into the link search dialog in the link inspector view? - When do contributors tap/select a Wikipedia article link from within the inspector view search results? - When do contributors tap the "Done" button in the link inspector view? ===📚 //Existing// citation workflows=== When adding a new citation, the feature field should be //cite-add//; when editing an existing citation, it should be //cite-edit//. //Where to communicate which citation type? Currently in the feature// (@Neil_P._Quinn_WMF to define) - . - . - . ===📚 //Revised// citation workflows=== (@Neil_P._Quinn_WMF to define) - . - . - . ###Resources - [VE feature instrumentation notes](https://docs.google.com/document/d/1n0MKZWiNm2ZviBHiImnNRnUjSp5e5JqfXorYtIsuP-0/edit?pli=1#) - [Schema:VisualEditorFeatureUse](https://meta.wikimedia.org/wiki/Schema:VisualEditorFeatureUse) - [Wireframes: linking w/ contextual inputs](https://wikimedia.invisionapp.com/freehand/document/s1duRw6io) - [Mobile context items hypotheses](https://phabricator.wikimedia.org/T221247) - [Desktop VE feature use](https://docs.google.com/spreadsheets/d/1FZsIZk7ty9xB92TQRBnxdmXpt3vEcWCjxZy0YPt85Nc/edit#gid=0) --- ###References 1. **Revised workflows**: https://phabricator.wikimedia.org/T221247 2. **Feature use data**: https://www.mediawiki.org/wiki/VisualEditor_on_mobile_report

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? == 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. == Instrumentation needs == ===🔗 //Existing// link workflows=== When adding a new link, the feature field should be //link-add//; when editing an existing link, it should be //link-edit-internal// or //link-edit-external//, as the case may be. - A link context item being shown because the user has tapped on a link (action //context-show//) - A link being deleted using the button in the context item (action //clear//) - A link dialog being opened (action //window-open//) - We will distinguish windows opened from the toolbar from windows opened from context items using the feature - With a link dialog open, text being typed or changed in the "search pages" field for the first time since the dialog opened (action //search-pages-input//) - With a link dialog open, text being typed or changed in the "external link" field for the first time since the dialog opened (action //external-link-input//) - With a link dialog open, the dialog being closed using the back arrow (action //abort//) - With a link dialog open, the link being inserted or confirmed by pressing "done" (action //insert-done//) - With a link dialog open, the link being inserted or confirmed by tapping on one of the results from "search pages" (//insert-search-pages//) ===🔗 //Revised// link workflows=== (@Neil_P._Quinn_WMF to finish defining) - When does the context item get shown? - When do contributors tap the "🔗" icon in the toolbar? - When do contributors tap the "unlink" button in the context item? - When do contributors tap the "edit link target" button in the context item? - When do contributors tap the "edit label text" button in the context item? - When do contributors tap the "edit link target" button in the context item? - When do contributors tap into the link search dialog in the link inspector view? - When do contributors tap/select a Wikipedia article link from within the inspector view search results? - When do contributors tap the "Done" button in the link inspector view? ===📚 //Existing// citation workflows=== When adding a new citation, the feature field should be //cite-add//; when editing an existing citation, it should be //cite-edit//. //Where to communicate which citation type? Currently in the feature// (@Neil_P._Quinn_WMF to define) - . - . - . ===📚 //Revised// citation workflows=== (@Neil_P._Quinn_WMF to define) - . - . - . ###Resources - [VE feature instrumentation notes](https://docs.google.com/document/d/1n0MKZWiNm2ZviBHiImnNRnUjSp5e5JqfXorYtIsuP-0/edit?pli=1#) - [Schema:VisualEditorFeatureUse](https://meta.wikimedia.org/wiki/Schema:VisualEditorFeatureUse) - [Wireframes: linking w/ contextual inputs](https://wikimedia.invisionapp.com/freehand/document/s1duRw6io) - [Mobile context items hypotheses](https://phabricator.wikimedia.org/T221247) - [Desktop VE feature use](https://docs.google.com/spreadsheets/d/1FZsIZk7ty9xB92TQRBnxdmXpt3vEcWCjxZy0YPt85Nc/edit#gid=0) --- ###References 1. **Revised workflows**: https://phabricator.wikimedia.org/T221247 2. **Feature use data**: https://www.mediawiki.org/wiki/VisualEditor_on_mobile_report