Page MenuHomePhabricator

Better announce new optional MT services available
Closed, ResolvedPublic

Description

Content Translation provides support for multiple translation strategies (starting from scratch, using the source text or choosing among the available Machine Translation services). As new translation services are added, users may not have visibility on the new options they have.

This is especially significant for those services added as non-default options (e.g., Apertium translation between Hindi and Urdu).

Event Timeline

I made an initial exploration, the design goals have been to:

  • Keep the information noticeable
  • Not being a blocker for editing (avoiding explicit interactions)

The proposed solution consists of:

  • Include a visual indicator to get the user attention
  • Include a message explaining the availability of new options (using the same color as the indicator).
  • When the user opens the selector, the new option is identified as such with the label "new" (in the same color used for the indicator)
  • Once the user has selected the new option, all the above clues are removed and they are never shown again to the same user during this or any other translation. Even if the user changes to different MT options.

I illustrated this below:

announce-new-mt.png (768×1 px, 240 KB)

announce-new-mt-selector.png (768×1 px, 243 KB)

announce-new-mt-back.png (768×1 px, 238 KB)

Amire80 triaged this task as Medium priority.Mar 3 2016, 7:22 AM
Amire80 moved this task from Needs Triage to CX8 on the ContentTranslation board.

Change 274682 had a related patch set uploaded (by Santhosh):
WIP: Better announce new optional MT services available

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

pasted_file (256×512 px, 20 KB)

Once the user has selected the new option, all the above clues are removed and they are never shown again to the same user during this or any other translation. Even if the user changes to different MT options.

This is not done in this commit(https://gerrit.wikimedia.org/r/274682). It require some ways to persisit the provider preference. To be done in different commit

Change 275365 had a related patch set uploaded (by Santhosh):
MT: Store the MT provider preference in localstorage

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

Change 277195 had a related patch set uploaded (by KartikMistry):
Better announce new optional MT services available

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

Change 274682 merged by jenkins-bot:
Better announce new optional MT services available

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

Change 277195 merged by jenkins-bot:
Better announce new optional MT services available

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

Change 275365 merged by jenkins-bot:
MT: Store the MT provider preference in localstorage

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