Page MenuHomePhabricator

Design a weekly translation rate chart for CXStats
Closed, ResolvedPublic1 Estimated Story Points


Design a weekly translation rate chart for CXStats.

Event Timeline

Amire80 assigned this task to Pginer-WMF.
Amire80 raised the priority of this task from to High.
Amire80 updated the task description. (Show Details)
Amire80 added subscribers: Amire80, Aklapper.
Nikerabbit edited a custom field.

The goal is to better understand the growth in user productivity. Making it easier to answer questions like:

  • Are more articles being published now than there used to in a past period?
  • Is the publication pace increasing? (to get a better picture we may need to compare this with the info about users which have no visualisation at all. Related tickets: T100034, T100035)
  • How was the pace of publication affected by a change we made on date X?

My current thinking is based on the following:

  • Avoid adding clutter. Frequency is an alternative view on the existing published translations graph. It makes sense to present
  • Avoid confusion about views. To avoid confusion, it is important to visually distinguish whether the graph represents values accumulated or not. For that purpose, I'd recommend using a line for accumulative values (values are connected) while use a bar chart (not connected to each other) to represent independent values.
  • Adjust the scale, With the current system the local language is shown compared to "al languages" however, the difference in scale makes the local language graph hard to interpret intuitively. Options to select which graph to view (local language, all languages or both) will be useful if the scale is adjusted. This is related to T102408.

Design details

Current accumulative view showing the evolution of the total number of translations (default view):

translations-per-week-initial.png (796×960 px, 50 KB)

Translations per week:

translations-per-week.png (796×960 px, 42 KB)

Translations per week (once the "all languages" have been disabled:

translations-per-week-only-local.png (796×960 px, 42 KB)

Note that we should not allow disabling both checkmarks (an empty graph is of little use for anyone). Thus, if there is only one checkbox checked, the result of disabling it would be the other checkbox to become enabled.

There is a problem in this design as it conflicts with the idea in T90538

If a single graph shows two languags, we cannot show total, draft, deleted in same graph because they are different concepts.

I would suggest the following:

  • At any time show graph for one and only one language. Or graph for all languages total. Do not mix them up. If we do, for many languages, the scale of difference between total and local language is very big and the visualization wont make sense.
  • The above design shows both language only when user select both check boxes, but I suggest removing the check boxes and make it tabs. Or even list the total and local language one after another. Either of this approach automatically address T102408
  • For a language or total graph, always show total, draft, deletion in different colors. - So that the relative plotting is always about status of translation.
  • weekly trend bar chart shows weekly translation, deletion, draft trends too

For the iterative implementation of T102408, T90538 and T105192, I suggest the following iterations:

  1. Separate the total and local language graphs, show them one after another under different headings ( )
  2. Show draft counts with a different color line for both graphs (
  3. Show deletion counts with a different color line for both graphs (
  4. Just like the cumulative graphs, show trend bar charts, show deletion, translation, draft trend in same graph(
  5. Club the cumulative and trend under tabs
  6. (if needed) club the total and local language under tabs
Arrbee moved this task from In Progress to Done on the LE-CX6-Sprint 3 board.

We need new ticket for

  • Club the cumulative and trend under tabs
  • (if needed) club the total and local language under tabs

and then we can close this ticket