Page MenuHomePhabricator

Add an initial set of collections by tagging some existing community pages
Closed, ResolvedPublic

Description

As part of the work on Custom translation suggestions (T113257), support was provided to define collections of topics to translate to make them visible in Content Translation on mobile (T378958). Currently, only one collection is available for users, which is a hardcoded collection based on vital articles (T374597). With only one collection users may not understand the potential of collections, the option for "all collections" becomes redundant, and a "special" collection does not serve as an example for communities to discover how collections are created.

bn.m.wikipedia.org_w_index.php_title=%E0%A6%AC%E0%A6%BF%E0%A6%B6%E0%A7%87%E0%A6%B7_%E0%A6%AC%E0%A6%BF%E0%A6%B7%E0%A6%AF%E0%A6%BC%E0%A6%AC%E0%A6%B8%E0%A7%8D%E0%A6%A4%E0%A7%81_%E0%A6%85%E0%A6%A8%E0%A7%81%E0%A6%AC%E0%A6%BE%E0%A6%A6&active- (5).png (568×320 px, 44 KB)

This ticket proposes to add more collections by using the <page-collection/> tag on existing pages that list relevant articles. As part of this process, we'll check with communities whether there is any objection for their list of articles to be visible in Content Translation. These are the proposed pages to mark as collections:

For the pages listed, it should be possible to mark them as collections just by adding the <page-collection/>tag. If there are technical complications or communities object, we can skip the particular case and consider alternatives.

Having several collections will be useful for users to switch between different collections, better differentiate the purpose of the "all collections" option, serve as an example for communities to adopt this feature and start to assess the impact of different types of collections (e.g., broad vs. narrower topic areas). This becomes more relevant as the translation dashboard becomes more accessible with the enablement of new entry points in more wikis (T371692).

Acceptance Criteria
  • Successful states:
  • Visibility of the added collections on the CX mobile UI.
  • Visibility of the added collections under this category
  • Getting a list of article suggestions after selecting one collection at a time.
  • Getting a list of section-level suggestions after selecting one collection at a time.
  • Getting a list of article suggestions after selecting the all collections filter.
  • Getting a list of section-level suggestions after selecting the all collections filter.
  • Unsuccessful states:
  • Getting the appropriate message/view when there are no article suggestions after selecting one collection at a time.
  • Getting the appropriate message/view when there are no section-level suggestions after selecting one collection at a time.
  • Getting the appropriate message/view when there are no article suggestions after selecting the all collections filter.
  • Getting the appropriate message/view when there are no section-level suggestions after selecting the all collections filter.
  • Getting the appropriate view when there are no collections that work for a particular source<>target language pair.

If an article cuts across multiple collections, how does this currently appear in the UI?

Derived Requirements

  1. Implement the <page-collection/> tag on the following community-maintained pages to define them as collections for Content Translation:
    • "List of articles every Wikipedia should have"
    • "Wikiproject Women's Health Vital articles"
    • "Wiki99"
    • Additional collections pending confirmation, such as CEE 2024 and Wikimedians of Turkic Languages User Group.
  2. Ensure added collections are visible and selectable in the Content Translation (CX) mobile UI.
  3. Allow users to access a list of:
    • Article suggestions for each collection.
    • Section-level suggestions for each collection.
    • Article and section-level suggestions for the "all collections" filter.
  4. Provide appropriate feedback for unsuccessful states, including:
    • No article or section-level suggestions available.
    • No collections applicable for a specific source-target language pair.
  5. Address edge cases, ensuring clear display of articles that appear in multiple collections.
Test Steps

Test Case 1: Ensure collections are visible in CX mobile UI

  1. Add the <page-collection/> tag to the "List of articles every Wikipedia should have" page on beta wiki.
  2. Navigate to the Content Translation mobile interface.
  3. ✅❓❌⬜ AC1: Confirm that the collection "List of articles every Wikipedia should have" is visible in the collections list.

Test Case 2: Validate article suggestions for a single collection

  1. Select the "List of articles every Wikipedia should have" collection in the CX mobile UI.
  2. Check for a list of article suggestions related to the collection.
  3. ✅❓❌⬜ AC2: Confirm that article suggestions are displayed correctly for the collection.

Test Case 3: Validate section-level suggestions for a single collection

  1. Select the "List of articles every Wikipedia should have" collection in the CX mobile UI.
  2. Check for section-level suggestions related to the collection.
  3. ✅❓❌⬜ AC3: Confirm that section-level suggestions are displayed correctly for the collection.

Test Case 4: Validate "all collections" filter

  1. In the CX mobile UI, select the "all collections" filter.
  2. Check for a combined list of article suggestions from all collections.
  3. ✅❓❌⬜ AC4: Confirm that article suggestions from all collections are displayed correctly.
  4. Check for section-level suggestions from all collections.
  5. ✅❓❌⬜ AC5: Confirm that section-level suggestions from all collections are displayed correctly.

Test Case 5: Handle no suggestions for an individual collection

  1. Select a collection with no available suggestions.
  2. ✅❓❌⬜ AC6: Confirm that an appropriate message/view is displayed for no article suggestions.
  3. ✅❓❌⬜ AC7: Confirm that an appropriate message/view is displayed for no section-level suggestions.

Test Case 6: Handle edge cases of overlapping articles

  1. Ensure articles appearing in multiple collections (e.g., HIV/AIDS, Bread) are clearly indicated in the CX mobile UI.
  2. ✅❓❌⬜ AC8: Confirm that overlapping articles are displayed without confusion across relevant collections.

QA Results - Test Mobile ContentTranslation

Details

Other Assignee
UOzurumba

Event Timeline

PWaigi-WMF updated Other Assignee, added: UOzurumba.
PWaigi-WMF moved this task from Prioritized to In-progress on the LPL Hypothesis board.

The team has added these three collections but found some issues with the RecAPI > T380699, T380838
-Wikiproject Women's Health Vital articles> seen as Women's Health
-Wiki99 > seen as Wiki99/food
-List of articles every Wikipedia should have > seen as Essential Articles

@PWaigi-WMF Can you please review my findings and the possible issues section? If you have any questions, please let me know.

Test Result - Test Mobile ContentTranslation

Status: ✅ PASS / ❓Need More Info / ❌ FAIL / ⬜ Not Testable
Environment: Test Mobile ContentTranslation
OS: macOS Sonoma 15.1
Browser: Chrome 131
Device: MBA
Emulated Device: NA

Test Artifact(s):

https://test.m.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions&from=fr&to=en&filter-type=automatic&filter-id=collections

Test Steps

Test Case 1: Ensure collections are visible in CX mobile UI

  1. Add the <page-collection/> tag to the "List of articles every Wikipedia should have" page on beta wiki.
  2. Navigate to the Content Translation mobile interface.
  3. AC1: Confirm that the collection "List of articles every Wikipedia should have" is visible in the collections list.

2024-12-04_13-27-41.png (733×1 px, 207 KB)

Test Case 2: Validate article suggestions for a single collection

  1. Select the "List of articles every Wikipedia should have" collection in the CX mobile UI.
  2. Check for a list of article suggestions related to the collection.
  3. AC2: Confirm that article suggestions are displayed correctly for the collection.

Gif

2024-12-04_13-31-20.mp4.gif (1×694 px, 1 MB)

Test Case 3: Validate section-level suggestions for italic texta single collection

  1. Select the "List of articles every Wikipedia should have" collection in the CX mobile UI.
  2. Check for section-level suggestions related to the collection.
  3. AC3: Confirm that section-level suggestions are displayed correctly for the collection.

See AC2

Test Case 4: Validate "all collections" filter

  1. In the CX mobile UI, select the "all collections" filter.
  2. Check for a combined list of article suggestions from all collections.
  3. AC4: Confirm that article suggestions from all collections are displayed correctly.
  4. Check for section-level suggestions from all collections.

2024-12-04_13-36-48.mp4.gif (1×646 px, 2 MB)

  1. AC5: Confirm that section-level suggestions from all collections are displayed correctly.

SEE AC4

Test Case 5: Handle no suggestions for an individual collection

  1. Select a collection with no available suggestions.
  2. AC6: Confirm that an appropriate message/view is displayed for no article suggestions.

There is no message but displaying empty under Create new pages as seen in the screenshot. Is this fine?

2024-12-04_14-24-18.png (1×729 px, 162 KB)

  1. AC7: Confirm that an appropriate message/view is displayed for no section-level suggestions.

See AC6, there are no categories that I can test with that displays no section-level suggestions

Test Case 6: Handle edge cases of overlapping articles

  1. Ensure articles appearing in multiple collections (e.g., HIV/AIDS, Bread) are clearly indicated in the CX mobile UI.
  2. AC8: Confirm that overlapping articles are displayed without confusion across relevant collections.

Let me know if there is a way to test this because as of right now, this is not QA testable.

❓❌ Possible Issue

  1. If a category has for an example, 4 articles for page, if you close them out, you can never get them back again for suggestions? What happens if you "X" one of them by accident, will you be able to undo that?

2024-12-04_13-38-14.mp4.gif (1×624 px, 679 KB)

  1. When I select "Vital articles", I also get Women's Health

2024-12-04_14-18-33.mp4.gif (1×684 px, 1 MB)

GMikesell-WMF updated the task description. (Show Details)
GMikesell-WMF moved this task from Needs QA to In-progress on the LPL Hypothesis board.

@GMikesell-WMF We can pack the edge case for now.

@Pginer-WMF I wanted to confirm that issue 1 is the expected behavior.

❓❌ Possible Issue

  1. If a category has for an example, 4 articles for page, if you close them out, you can never get them back again for suggestions? What happens if you "X" one of them by accident, will you be able to undo that?

2024-12-04_13-38-14.mp4.gif (1×624 px, 679 KB)

@ngkountas @SBisson This is strange; I've tried to re-create it without much success but could you check?

  1. When I select "Vital articles", I also get Women's Health

2024-12-04_14-18-33.mp4.gif (1×684 px, 1 MB)

I tried to reproduce the second issue with no luck, too. @GMikesell-WMF is this something you can reproduce consistently? If so, could you please share the exact steps to reproduce?

Test Case 6: Handle edge cases of overlapping articles

  1. Ensure articles appearing in multiple collections (e.g., HIV/AIDS, Bread) are clearly indicated in the CX mobile UI.
  2. AC8: Confirm that overlapping articles are displayed without confusion across relevant collections.

@GMikesell-WMF We were able to see and address Test Case 6 in T381777.

@PWaigi-WMF Please review my findings below, thanks!

@GMikesell-WMF We can pack the edge case for now.

@Pginer-WMF I wanted to confirm that issue 1 is the expected behavior.

❓❌ Possible Issue

  1. If a category has for an example, 4 articles for page, if you close them out, you can never get them back again for suggestions? What happens if you "X" one of them by accident, will you be able to undo that?

2024-12-04_13-38-14.mp4.gif (1×624 px, 679 KB)

@ngkountas @SBisson This is strange; I've tried to re-create it without much success but could you check?

  1. When I select "Vital articles", I also get Women's Health

2024-12-04_14-18-33.mp4.gif (1×684 px, 1 MB)

  1. I can still recreate the issue. If you select Women's Health and close out all the articles, which I feel is around 30 clicks, you'll run out as seen in the gif below. I click refresh suggestions and I can't get them back anymore. The only way is if I empty the cache with a hard reload.

2024-12-17_14-27-00.mp4.gif (832×968 px, 932 KB)

  1. "Vitals Articles" is now gone so I won't be able to test it anymore

Test Case 6: Handle edge cases of overlapping articles

  1. Ensure articles appearing in multiple collections (e.g., HIV/AIDS, Bread) are clearly indicated in the CX mobile UI.
  2. AC8: Confirm that overlapping articles are displayed without confusion across relevant collections.

@GMikesell-WMF We were able to see and address Test Case 6 in T381777.

  1. I'll answer it in T381777

"Vitals Articles" is now gone so I won't be able to test it anymore

@GMikesell-WMF So, this issue only appeared with the Vital Articles + Women's Health scenario?

We removed Vital Articles list from en.wiki since it was hard-coded; it added to the maintenance cost and code complexity T374597 + it's very similar to the Essential Articles list.

@PWaigi-WMF The rest are ok now but I am still experiencing the same issue or when articles are closed out.

  1. I can still recreate the issue. If you select Women's Health and close out all the articles, which I feel is around 30 clicks, you'll run out as seen in the gif below. I click refresh suggestions and I can't get them back anymore. The only way is if I empty the cache with a hard reload.

2024-12-17_14-27-00.mp4.gif (832×968 px, 932 KB)

@PWaigi-WMF The rest are ok now but I am still experiencing the same issue or when articles are closed out.

  1. I can still recreate the issue. If you select Women's Health and close out all the articles, which I feel is around 30 clicks, you'll run out as seen in the gif below. I click refresh suggestions and I can't get them back anymore. The only way is if I empty the cache with a hard reload.

2024-12-17_14-27-00.mp4.gif (832×968 px, 932 KB)

This is the current expected behavior; once a user discards all article/ section suggestions, they will not be able to see them again. Here is a follow-up ticket, T382476, that outlines similar scenarios and design a better way to communicate with users + interact with these states.

In terms of naming consistency, we may want to consider whether to include "wiki99/" prefix in the collections from the Wiki99 project or not. Current collections from wiki99 are listed as "Sustainability" and "Wiki99/food" which seems inconsistent.

For the long term, we may need to also think on whether some kind of authorship indicator could be useful to distinguish the "Food" collection from the Wiki99 project from a potential collection with the same/similar name from the Food and Drink Wiki project. And whether that indicator, if necessary, should be part of the Collection name or structured in.a different way (e.g., "Food" by Wiki99).

In terms of naming consistency, we may want to consider whether to include "wiki99/" prefix in the collections from the Wiki99 project or not. Current collections from wiki99 are listed as "Sustainability" and "Wiki99/food" which seems inconsistent.

Due to the current issue of long names breaking the UI, we had to add it as Sustainability instead of wiki99/Sustainability until T380702 is done. I will therefore proceed to close this ticket.
<page-collection name="Sustainability"></page-collection>