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 would try to explore : - how best to store translation worklists with parameters such as **source article title**, **source language**, **target language**, **QID**, etc. - a "list-infrastructure" / "list-manager" / "list pipeline" that's 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. `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 true status of the gap. `Managing WorkLists` As a campaign/WikiProject organizer, I want to manage the visibility and prioritization of worklists, So that editors are directed to the most important content gaps. ====Acceptance Criteria - Recommended approach - Dependencies - Risks

====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:** 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 would try to explore :explores & defines: - how best to store translation work- what the parameters of the lists with parameters such as would look like: **source article title**, **source language**, **target language**, **QID**, etc. - a "list-infrastructure" / "list-manager" / "list pipeline" that'sccount 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 truecurrent status of the gap. `Managing WorkLists` As a campaign/WikiProject organizerproduct manager, I want to manage the visibility and prioritization of worklists, So that editors are directed to the most important content gaps.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