Change Details

====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** already being curated by organizers and communities -> If this works, we increase the chances that more editors become aware of these worklists. b) We hope to **increase quality content contributions through translations** -> If this approach works, topical/campaign worklists can be a great, alternative source of translation suggestions for editors. ====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) Event/Wikiproject pages with translation worklists can be **read**, **parsed**, and **fed** into the content translation tool | a) Future requirements like sharing, re-using, and tracking of worklists are possible. b)There's also the aspect of private/personal lists vs public/collaborative lists on wiki. c) Worklists 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 do the following: -> 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 recommendation API: T369484; 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 mobile translation workflow, where editors come to translate articles: a) We hope to **increase the visibility/discovery of topical gaps** already being curated by organizers and communities -> If this works, we increase the chances that more editors become aware of these worklists. b) We hope to **increase quality content contributions through translations** -> If this approach works, topical/campaign worklists can be a great, alternative source of translation suggestions for editors. ====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) Event/Wikiproject pages with translation worklists can be **read**, **parsed**, and **fed** into the content translation tool | a) Future requirements like sharing, re-using, and tracking of worklists are possible. b)There's also the aspect of private/personal lists vs public/collaborative lists on wiki. c) Worklists 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 do the following: -> Have a way to **parse the topical/campaign lists** to the mobile translation tool to expose the lists beyond the current campaign pages/wiki projects. -> Have a way to allow editors to **opt in or opt out** of this service; so organizers can choose when to include their lists on the CX mobile flow. -> Have a way to feed the worklists into the recommendation API: T369484; so that editors can receive these as suggestions. -> Have a way to incorporate/allow **changes made to the worklists** which also reflect on the CX mobile flow; translators should have the most up-to-date translation suggestions presented. -> Have a way to **update already translated tasks**; organizers should be able to tell the progress made against their lists. ====Acceptance Criteria Recommended approach -> defined below in the comments. Follow-up technical tasks: -> T371515

====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** already being curated by organizers and communities -> If this works, we increase the chances that more editors become aware of these worklists. b) We hope to **increase quality content contributions through translations** -> If this approach works, topical/campaign worklists can be a great, alternative source of translation suggestions for editors. ====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) Event/Wikiproject pages with translation worklists can be **read**, **parsed**, and **fed** into the content translation tool | a) Future requirements like sharing, re-using, and tracking of worklists are possible. b)There's also the aspect of private/personal lists vs public/collaborative lists on wiki. c) Worklists 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 do the following: -> Have a service thatway to **parses the topical/campaign lists** to the mobile translation tool; so that there's a way of to exposing thesee the lists beyond the current campaign pages/wiki projects. -> A-> Have a way to 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 editoso organizers can view the most up-to-date translation suggestionschoose when to include their lists on the CX mobile flow. -> Have a way to feed the worklists into the recommendation API: T369484; so that editors can receive these as suggestions. -> **Sync already translated tasks** back-> Have a way to incorporate/allow **changes made to the campaign page/wiki project;worklists** which also reflect on the CX mobile flow; so that organizers can view & track progress.translators should have the most up-to-date translation suggestions presented. -> Have a way to **update already translated tasks**; organizers should be able to tell the progress made against their lists. ====Acceptance Criteria - Recommended approach + Follow-up technical tasksch - Dependencies-> defined below in the comments. Follow-up technical tasks: - Risks-> T371515