Change Details

====Background **Hypothesis:** If we developed a proof of concept that adds translation tasks sourced from WikiProjects and other list-building initiatives, and present them as suggestions within the CX mobile workflow, then more editors would discover and translate articles focused on topical gaps. By introducing an option that allows editors to select translation suggestions based on topical lists, we would test whether this approach increases the content coverage in our projects. By making topical lists visible in existing editorial workflows, in this case, the CX mobile interface, where editors land to translate articles: - To increase the visibility/discovery of topical gaps; if this works, more editors will become aware of these worklists. - To increase translations; if this works, worklists can offer an alternative source of translation suggestions. ====Description This ticket explores & defines: - what the parameters of the list would look like: **source article title**, **source language**, **target language**, **QID**, etc. - account for the fact that lists can be generated by different tools e.g. petscan, wiki-data queries, etc. - where the "list-infrastructure" would live. - how the "list-infrastructure" interfaces with the CX mobile tool. - how we track / tag translated articles sourced from these lists. Out of hypothesis scope: - futuristic: having the lists discoverable, shareable, and re-useable by editors. - futuristic: having the "list-infrastructure" useable by any project/ wiki. ====User story `Including WorkLists` As a campaign/ wiki project organizer, I want to include topical lists in the CX mobile workflow, So that more editors can discover and translate articles based on these worklists. `Managing WorkLists` As a campaign/WikiProject organizer, I want to manage the visibility of worklists, So that editors are directed to the most important content gaps. `Updating WorkLists` As a campaign/ wiki project organizer, I want to update the worklist that feeds into the CX mobile workflow, So that newer sets of articles within the topic can be translated. `Tracking Translated Articles` As a campaign/ wiki project organizer, I want to know which articles have been translated from the CX mobile workflow, So that the translation worklist can reflect the current status of the gap. As a product manager, I want to know how many quality articles have been translated, So that we can determine the impact of surfacing the translation worklist on the CX mobile workflow. ====Acceptance Criteria - Recommended approach - Dependencies - Risks

====Background **Hypothesis 2.1.4:** If we developed a proof of concept that adds translation tasks sourced from WikiProjects and other list-building initiatives, and present them as suggestions within the CX mobile workflow, then more editors would discover and translate articles focused on topical gaps. By introducing an option that allows editors to select translation suggestions based on topical lists, we would test whether this approach increases the content coverage in our projects. By making topical/campaign lists visible in existing editorial workflows, in this case, the mobile translation workflow, where editors come to translate articles: a) We hope to **increase the visibility/discovery of topical gaps** curated by organizers and communities -> If this works, more editors will become aware of these worklists. b) We hope to **increase quality content through translations** -> If this approach works, it would then expand our approach to closing content gaps. ====Description | **Considerations** | **Notes** | **PoC scope** |** Future Opportunities** | |1.List Management | Lists are knowledge gap areas that are curated collaboratively by organizers/communities using different tools e.g. petscan, and wiki-data queries. | a) Shortlisted topical/campaign worklists (TBA) can be **Moved**, **Stored**, and **Updated** between the campaign pages and tools. | a) Other capabilities could include; Sharing, Re-using, and Tracking of lists. b)There's also the aspect of private/personal lists vs public/collaborative lists on wiki. c) Lists are presented differently on meta/ campaign pages. | |2.Tasks/Contributions | Types of contributions/actions | **Translation tasks** with attributes such as source article title, source language, target language, QID. | Other use cases: creating new articles, adding images, adding info-boxes, adding references and citations, etc. | |3. Tools | Entry-points to surface & action the lists | **Mobile translation tool** has a more updated dashboard + tools. | Other tools: desktop translation, newcomer tools, suggested edits(apps), event page| This ticket aims to put together a PoC that can perform the following capabilities: -> Have a service that **parses the topical/campaign lists** to the mobile translation tool; so that there's a way of exposing these lists beyond the current campaign pages/wiki projects. -> Allow editors to **opt in or opt out** of this service; so that organizers can choose when to allow their lists to surface on the mobile translation tool. -> Any **changes made to the worklists** on the campaign page/wiki projects also reflect on the mobile translation tool; so that editors can view the most up-to-date translation suggestions. -> Have a way to feed the worklists into the **[[ https://phabricator.wikimedia.org/T369484 | recommendation API]]**; so that editors can receive these as suggestions. -> **Sync already translated tasks** back to the campaign page/wiki project; so that organizers can view & track progress. ====Acceptance Criteria - Recommended approach + follow-up technical tasks - Dependencies - Risks

====Background **Hypothesis 2.1.4:** If we developed a proof of concept that adds translation tasks sourced from WikiProjects and other list-building initiatives, and present them as suggestions within the CX mobile workflow, then more editors would discover and translate articles focused on topical gaps. By introducing an option that allows editors to select translation suggestions based on topical lists, we would test whether this approach increases the content coverage in our projects. By making topical/campaign lists visible in existing editorial workflows, in this case, the CX mobile interfacetranslation workflow, where editors landcome to translate articles: - To a) We hope to **increase the visibility/discovery of topical gaps; i** curated by organizers and communities -> If this works, more editors will become aware of these worklists. - To b) We hope to **increasee quality content through translations;s** -> If this approach works, if this works,it would then expand our approach to closing content gaps. worklists can offer an alternative source of translation suggestions. ====Description This ticket explores & defines: - what the parameters of the list would look like: **source article title**, **source language**, **target language**, **QID**, etc. - account for the fact that lists can be generated by different tools e.g. petscan, wiki-data queries, etc.| **Considerations** | **Notes** | **PoC scope** |** Future Opportunities** | - where the "list-infrastructure" would live.|1.List Management | Lists are knowledge gap areas that are curated collaboratively by organizers/communities using different tools e.g. petscan, and wiki-data queries. | a) Shortlisted topical/campaign worklists (TBA) can be **Moved**, **Stored**, and **Updated** between the campaign pages and tools. | a) Other capabilities could include; Sharing, Re-using, and Tracking of lists. b)There's also the aspect of private/personal lists vs public/collaborative lists on wiki. c) Lists are presented differently on meta/ campaign pages. | - how the "list-infrastructure" interfaces with the CX mobile tool.|2.Tasks/Contributions | Types of contributions/actions | **Translation tasks** with attributes such as source article title, source language, target language, QID. | Other use cases: creating new articles, adding images, adding info-boxes, adding references and citations, etc. | - how we track / tag translated articles sourced from these lists.|3. Tools | Entry-points to surface & action the lists | **Mobile translation tool** has a more updated dashboard + tools. | Other tools: desktop translation, newcomer tools, suggested edits(apps), event page| Out of hypothesis scope:This ticket aims to put together a PoC that can perform the following capabilities: - futuristic: having-> Have a service that **parses the topical/campaign lists discoverable, shareable,** to the mobile translation tool; and re-useable by editorsso that there's a way of exposing these lists beyond the current campaign pages/wiki projects. - futuristic: having the "list-infrastructure" useable by any project/ wiki. ====User story `Including WorkLists`> Allow editors to **opt in or opt out** of this service; so that organizers can choose when to allow their lists to surface on the mobile translation tool. As a campaign/ wiki project organizer, I want to include topical lists in the CX mobile workflow, So that more editors can discover and translate articles based on these worklists. `Managing WorkLists` As a campaign/WikiProject organizer, I want to manage the visibility of worklists,-> Any **changes made to the worklists** on the campaign page/wiki projects also reflect on the mobile translation tool; so that editors can view the most up-to-date translation suggestions. So that editors are directed to the most important content gaps. `Updating WorkLists` As a campaign/ wiki project organizer, I want to update the worklist that feeds into the CX mobile workflow, So that newer sets of articles within the topic can be translated. `Tracking Translated Articles` As a campaign/ wiki project organizer, I want to know which articles have been translated from the CX mobile workflow, So that the translation worklist can reflect the current status of the gap. As a product manager, I want to know how many quality articles have been translated,-> Have a way to feed the worklists into the **[[ https://phabricator.wikimedia.org/T369484 | recommendation API]]**; so that editors can receive these as suggestions. So that we can determine-> **Sync already translated tasks** back to the impact of surfacing the translation worklist on the CX mobile workflowcampaign page/wiki project; so that organizers can view & track progress. ====Acceptance Criteria - Recommended approach + follow-up technical tasks - Dependencies - Risks