Page MenuHomePhabricator

Surface how much there is to translate
Closed, ResolvedPublic

Description

Idea originally proposed from the following wish below. The desire is to be aware of how big or time consuming will a translation task be for the user.

Community_Wishlist_Survey_2023/Translation/ContentTranslation_Article_size

Proposed solution

We can do show translation effort time in a more concise way in the suggestions (e.g., to easily identify quick translations) and in a more detailed way at the confirm step. In order to communicate the effort, expected time using some discrete levels (5 min., 15min., 30min., 1h, and a few hours) can provide intuitive and useful reference for users to estimate the effort based on the time they can/want to invest in the translation.

Translation effort - example workflow.png (1×2 px, 478 KB)

Derived Requirement

Ensure that the translation interface surfaces an estimate of the time required to complete a translation task, with discrete levels of effort such as "5 min," "15 min," "30 min," "1h," and "a few hours," to help users gauge the size and time commitment of the translation.

Expected impact

Data shows that translating a long source article results in more frequent deletions (T356765). By emphasizing quick translation opportunities, we may help direct users to the contributions where they are more likely to succeed. By informing about the expected effort, we help to set expectations when selecting a longer article too.

BDD

gherkin
Feature: Display of Estimated Translation Effort

Scenario: Surface estimated translation time for users
  Given the user is in the translation interface
  When the user views suggested translation tasks
  Then the system should display an estimated time to complete the translation, categorized as "5 min," "15 min," "30 min," "1h," or "a few hours"
  And at the confirm step, the system should provide a detailed estimate of the translation effort

Test Result - Beta|Prod

Status: ✅ PASS / ❓Need More Info / ❌ FAIL
Environment:Test Mobile Special:ContentTranslation
OS: macOS Sonoma 15.0
Browser: Chrome 129
Device: MBA
Emulated Device: NA

Test Artifact(s):

https://test.m.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions&from=es&to=en

Test Steps

Test Case 1: Ensure Detailed Estimate is Shown at Confirm Step

  1. Select a suggested article for translation and proceed to the confirm step.
  2. ✅❓❌⬜ AC1: Confirm that a more detailed estimate of the translation effort is displayed at the confirm step, including the same discrete levels for under and over 15 minutes.

QA Results - Test Mobile Special:ContentTranslation

ACStatusDetails
1T360570#10247456

Event Timeline

A recent report shows how translations based on longer source articles are more likely to be deleted (T356765). In the context of this task, as we communicate the effort to translate we may may want to emphasize the low effort ones.

I did some quick exploration. I think it makes sense to surface the expected effort in both the list of suggestions and the Confirm step. We can do this in a more concise way in the suggestions (e.g., to easily identify quick translations) and in a more detailed way at the confirm step.

In order to communicate the effort, I think expected time using some discrete levels (5 min., 15min., 30min., 1h, and a few hours) can provide intuitive and useful reference for users to estimate the effort based on the time they can/want to invest in the translation.

We also may need to account for the different situations of starting a translaiton for a new article or expand an existing one.

A possible approach is illustrated below:

Translation effort - example workflow.png (1×2 px, 478 KB)


Some additional context of options explored:

Translation effort - analysis.png (3×4 px, 527 KB)
Translation effort - options.png (3×5 px, 729 KB)

More details in Figma

Change #1055253 had a related patch set uploaded (by Eamedina; author: Eamedina):

[mediawiki/extensions/ContentTranslation@master] Translation time estimate - WIP

https://gerrit.wikimedia.org/r/1055253

Other patches associated to this effort:

Change #1055253 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] Translation time estimate

https://gerrit.wikimedia.org/r/1055253

eamedina updated the task description. (Show Details)

Change #1072700 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):

[mediawiki/extensions/ContentTranslation@master] CX3 Build 0.2.0+20240913

https://gerrit.wikimedia.org/r/1072700

Change #1072700 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] CX3 Build 0.2.0+20240913

https://gerrit.wikimedia.org/r/1072700

@eamedina They are working as designed for the detailed estimates for under 15 min vs over 15 min as seen in the gifs below. Thanks for all your work! I will be moving this to Done.

Test Result - *Test Mobile Special:ContentTranslation

Status: ✅ PASS
Environment:Test Mobile Special:ContentTranslation
OS: macOS Sonoma 15.0
Browser: Chrome 129
Device: MBA
Emulated Device: NA

Test Artifact(s):

https://test.m.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions&from=es&to=en

Test Steps

Test Case 1: Ensure Detailed Estimate is Shown at Confirm Step

  1. Select a suggested article for translation and proceed to the confirm step.
  2. AC1: Confirm that a more detailed estimate of the translation effort is displayed at the confirm step, including the same discrete levels for under and over 15 minutes.
Under 15 minutesOver 15 minutes
2024-10-21_09-51-39.mp4.gif (732×356 px, 2 MB)
2024-10-21_09-54-12.mp4.gif (732×366 px, 1 MB)

I replied to the original wish to inform and keep a link to this ticket for context. With that, I think we can resolve the ticket. Thanks everyone!