Page MenuHomePhabricator

[Epic] ContentTranslation - Lists of articles to translate
Open, HighPublic

Description

Individuals and groups often follow some kind of list of articles to translate. Those lists are often informal (personal notes, a list in a user page or just an idea in the user's head) and lack integration with the rest of the translation process. By providing an integrated support for them, we can improve the whole translating experience.

This is a general Epic ticket to describe and discuss the idea. The workboard is at ContentTranslation-TranslationList. Specific tickets will be created for individual aspects. More details are provided below.

Goal

  • Increase engagement. Allow users to keep track of the articles they want to get translated easily. This will reduce missed opportunities for translation (e.g., not having time to translate the article they just found right now)
  • Increase discovery. Make it easy for users to find interesting articles to translate.
  • Increase collaboration. Sharing lists on specific topics that interest a community can encourage user participation. Participating together in a campaign can help to motivate users.
  • Track the progress of topic coverage in each language. Some languages cover some topics better than others, and this will help users understand which topics need better support and help complete it. The topics themselves can be defined by users and communities.

Scenarios considered

  1. Collecting articles for later. The user finds an interesting article but has no time to translate it now. The user can mark it so that it is easy to find later to do the translation. This can happen at different points:
    • Explicitly. The user just thought about an article and wants to add it for later.
    • While reading. Some content is missing or a page is not available in the user language (interlanguage link entry point).
    • When getting suggestions. The user finds an interesting suggestion, for later.
    • When translating. The user encounters missing links on articles that are worth creating in the user language.
    • When completing a translation. The user may want to add other articles from the same collection.
    • Based on other collections and the like. Other articles in the same category/collection/"list of"-article of a given article.
  2. Create a list of articles for a contest. The user is organising a campaign on their local wiki.
    • Add several articles efficiently.
    • Set the conditions of the campaign (languages, time period, etc.).
    • Allow other organisers to add/propose articles.
    • Share and connect the campaign with the information on-wiki.
    • Follow the progress of the campaign.
  3. Find interesting lists of articles.
    • Discover, keep accessing relevant lists (and not do so, when they are no longer relevant).
    • Get motivated on why pick a list and keep translating it.

Research information

There are many translation projects that use a task list that tracks the progress of translating a list of articles, with a different focus:

  • Some projects target single editors working on something that interests them. For example, with CX we already saw people translating articles on common topics, such as beaches of Spain, Fields medalists, or Queen albums. They can just look at categories in other languages that they know and see what's missing, or prepare a list of red links on their user pages.
  • Some projects target small groups of wiki editors working together. For example, in the Hebrew Wikipedia there is a small group of people that write or translate articles about UNESCO World Heritage sites. They have navigation templates for each country with the full list of heritage site in that country, with links to all the relevant future articles, and work according to these templates, gradually making all the links blue.

Learning the needs of these different groups of users and providing them with comfortable, automated and well-structured ways to create and update such task lists will help them focus on writing and translating and work less on the bureaucracy.

Solutions to explore

A prototype captures many of the design ideas which were later evaluated with user research.





  • Integrate the collections as part of the suggestions view. Suggestions, and "For later" will be just two special default collections.

List creation:

  • Allow to add articles to a list as an alternative to start translating for the different entry points:
    • Red links on a page (can be a recently translated page; a manually-created task list; a navigation template; etc)
    • Special pages (WantedPages, WithoutInterwiki)
    • Category in another language (Example: I know English and Hungarian. English Wikipedia has 200 articles about Nobel laureates in the appropriate category, Hungarian has only 70. I want to add the 130 missing articles to my task list in one click.)
  • Allow to add content not only from main namespace (e.g., allowing curated short article versions).

Campaigns and participation

  • Support list configuration and sharing
    • Support both monolingual ("I only care about translating from English to Hungarian") and multi-lingual ("I love Thai culture and I want articles about Thai music translated to as many languages as possible") cases for both the creators of campaigns and those accessing them.
  • Show user statistics and progress to motivate participation. (T114750)
  • Track progress of (big) campaigns you organised (presenting all the info organisers need about articles, participants and progress).

Discover lists and items to translate

  • Allow to create/add lists.
  • Surface shared lists when searching and getting suggestions.
  • Subscribe to get notifications for new opportunities to translate (e.g., subscribe/unsubscribe from lists to get notifications of new articles added).

The project is currently planned to be carried in three milestones:

  1. T114744: CXTL-MS1: Create a new translation list - planned for Language-Engineering October-December 2016
  2. T127016: CXTL-MS2: Share a Content Translation task list
  3. T114750: CXTL-MS3: Track translation task list progress

Each of them has its own subtasks. All are essential to the project's goals.

  1. Related tickets
  2. T87439 - Suggest articles to translate from the dashboard (can reuse at least some of the UI; suggestions list can come from personal or common task lists)
  3. T100283 - Simplify article selection to translate.
  4. Gather - it has lists in the database, although it requires more research about how useful it is to combine them

Related Objects

StatusAssignedTask
OpenNone
OpenNone
OpenNone
OpenNone
DuplicateNone
DuplicateNone
OpenNone
ResolvedAmire80
OpenNone
OpenNone
Resolvedsanthosh
OpenNone
ResolvedPetar.petkovic
OpenNone
Resolvedsanthosh
ResolvedPginer-WMF
Resolvedsanthosh
Resolvedsanthosh
Resolvedsanthosh
DeclinedPginer-WMF
ResolvedPginer-WMF
ResolvedAmire80
Resolvedsanthosh
ResolvedPginer-WMF
ResolvedPginer-WMF
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
ResolvedCapt_Swing
OpenNone
DuplicateCapt_Swing
OpenNone
ResolvedPginer-WMF
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
ResolvedAmire80
OpenNone
OpenNone
Resolvedsanthosh
ResolvedKartikMistry
ResolvedKartikMistry
OpenNone
OpenNone
Resolvedsanthosh
OpenNone
OpenNone
ResolvedPetar.petkovic
OpenNone
OpenNone
OpenNone
OpenNone

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Amire80 moved this task from Needs Triage to CX6 on the ContentTranslation board.Jun 23 2015, 8:15 AM

Trevor: In this design, Star means "save for later", but the Star has other meanings in other contexts. "watch star". It's probably being overloaded.
Dan: We use Star in flow for similar purposes - it makes sense to me.
Trevor: The difference is, when you click on this you won't be notified of anything. So clicking a star in different contexts will have different results.

What does happen when you click a star in this mockup?
The article is added to the list within this UI.

James: like the watchlist concept but it needs more filtering tools. How much work are you taking on? how many words to be translated? I would like to be able to sort my watchlist.
Surface the information they need to decide. we asked what criteria people use to decide what to translate? the quality of the article - size, completeness, contains good images, [popularity?].

How much gamification will this include? What about things you pinned but that got translated before you got to them? What 'stats' were you thinking of showing?

What happens when someone accidentally (or intentionally) does something bad? If we leave that for admins, that creates a backlog that pisses people off. Did you think about that for this interface?
Need to make it possible to flag problematic content.
Or if people are putting a ton of content into this collection.

What about collaboration issues? What if two people work on an article simultaneously?
This is part of a bigger issue about simultaneous editing.

(also this is a subset of a broader feature of work lists (not just for translation))

Is this UI meant to have subscrolling sections?

In our progress tracking sheets we mark if someone is already doing the translation.

The current list of articles we use for medical translation is one that I manage. Only articles I am happy with are added to the list. Have not had issues with other people trying to add to it

Wittylama added a comment.EditedJul 1 2015, 12:32 PM

Yesterday Magnus was able to include a geolocation feature in his "Not in the other language" tool https://tools.wmflabs.org/not-in-the-other-language/? - meaning that it's now possible to find candidates for translation about things that are "near me".
To extend this concept... can I please suggest adding a "map view" to the translation suggestions?

If you could have an open-street-map inferface, move-and-zoomable to the place of your interest, with markers for all geolocated articles that exist in the source language but not in the target language, that would be a super-engaging way for people (as individuals, schoolgroups or at editathons) to chose articles.

specific example (as a kind of user story) I wrote this article about a street in Mexico in the english wikipedia https://en.wikipedia.org/wiki/Francisco_I._Madero_Avenue initially translated from the spanish wikipedia article - because I wanted to write about something nearby to where Wikimania will be this year. But, there was no easy way for me to identify this as an possible translation candidate - I had to click around randomly for a while and ask locals to tell me what was missing.

Pginer-WMF updated the task description. (Show Details)Aug 3 2015, 11:34 AM
Pginer-WMF updated the task description. (Show Details)

After talking with @AndyRussG at Wikimania, it would be interesting to take a look to Editor campaigns (and the technical design) for their usecases and interesting ideas on a related area.

Pginer-WMF updated the task description. (Show Details)Aug 4 2015, 9:32 AM
Pginer-WMF updated the task description. (Show Details)Sep 17 2015, 12:01 PM
Pginer-WMF updated the task description. (Show Details)Sep 21 2015, 9:41 AM
Esh77 added a subscriber: Esh77.Sep 29 2015, 7:17 PM
Pginer-WMF updated the task description. (Show Details)Oct 6 2015, 8:45 AM
Ryuch added a subscriber: Ryuch.Nov 25 2015, 1:48 PM

This existing tool by Magnus Manske has some of the functionality you may be looking for

https://tools.wmflabs.org/listeria/dynamic.html#list=101

and with some small changes could do even more

https://bitbucket.org/magnusmanske/listeria/issues/11/create-links-for-create-article-and

Nemo_bis removed a subscriber: Nemo_bis.Jan 18 2016, 2:29 PM
Amire80 added a subscriber: Harej.Apr 2 2016, 11:51 AM
Pginer-WMF updated the task description. (Show Details)Apr 21 2016, 5:45 AM

Hi there, I want to bring a possible solution of this task from @Lucia Huang, a software engineer from Taiwan. What is her proposal please refer here for further details.

Thanks Shangkuanlc for introduce me here.

Hi all:

The idea is to use program to create a list of pages that requires translation and then prioritize the list with visiting number or other factors.

The motivation is from the time when I did TED video subtitle translation recently. I noticed there are many new volunteers joined the group each week and almost all the new video got assigned to someone soon after the video being put on-line.
And I noticed many interesting or important wikipedia pages do not have corresponding information in the Chinese page.
What if we can make the Wikipedia translation work similar to subtitle translations:
a. Prioritized list of translation tasks
b. Cut tasks into small items that each item can be finished in 4 hours by an experienced translator
c. Review policy
d. Credits for volunteers

I put the rough idea for #a at my personal page.

It is to figure out pages need better translation by some rules:

number_of_lines(target language page) / number_of_lines(English or original language page) < 10%

And prioritize the pages with factors including

  • recent visiting number of target language page
  • recent visiting number of English or original language page
  • recent edit times of English or original language page

Translation efforts on those tasks could give back the biggest influence and motivate volunteers to take the tasks.

Agree prioritizing by number of EN pageviews is an excellent idea.

Thanks for the input @Lucia_Huang. The prioritisation aspects are really relevant when exposing campaigns for users to translate. Since we expect many different campaigns to be created.

Currently the tool provides individual article recommendations and the number of views for articles are already considered. That work was done by the research team, and there are more details in this paper, and in T111028.

Abit added a subscriber: Abit.Aug 18 2016, 1:54 AM
Pginer-WMF updated the task description. (Show Details)Aug 31 2016, 1:37 PM
Amire80 updated the task description. (Show Details)Oct 2 2016, 2:30 PM
Amire80 updated the task description. (Show Details)
Framawiki added a subscriber: Framawiki.
Amire80 updated the task description. (Show Details)Oct 14 2016, 1:04 PM

This is certainly a sensible usage scenario for this feature. It should make TOTW easier to share and use, and consequently more popular.

Sadads added subscribers: SGill, Sadads.EditedMon, Jul 22, 5:14 PM

@Amire80 I am currently doing list-building research with @SGill around how to best build lists for Campaigns -- there is a larger need in the movement to have what I would describe as a "reusable worklist". Something that can be generated in both manual and semi-automated list building (i.e. we prototyped something like this at T187305 and https://tools.wmflabs.org/worklist-tool) -- that can then be integrated into both on-wiki and offwiki pages, and be portable so that if you want to use the same list for Event Metrics Education-Program-Dashboard or something like ListeriaBot, where its printed out into other pages.

The Worklist is a prerequisite to any collaborative effrot within the movement, and we should be able to generate them pretty easily with the various kinds of queries you can do with something like Wikidata or Petscan. Figuring out the portable format for that would be awesome :)

Whatever works. Translation is a major scenario for worklist / tasklist / campaign / whatever-you-call-it, but certainly not the only one.