In T310774#8367151, @MNeisler wrote:

@Pginer-WMF I've created an initial draft analytics dashboard for review, which shows one approach to showing translation activity based on a unified content and section translation experience. These updated analytics can be found under the Translation-Unified Experience tab.

Thanks Megan. This is great!
Overall, I think the options provide the ability to focus on the areas of interest that we were looking for. Being able to view the overall activity or focus on a specific area of interest.
One missing aspect is the time range selector. It is present in the Section Translaiton tab but not on the unified dashboard. The new unified dashboard seems to show data for the last 14 months (with a year-over-year graph in some cases which is really useful, by the way). However, it does not allow to observe trends for a longer period of time or focus on particular incidents. Examples:

• I was comparing the recent translation activity between Catalan and Bengali, which is similar now, but I wanted to check how that compared prior to the enablement of mobile translation (Feb 20221) which Bengali Wikipedia has been active on.
• If we want to look back at the data for the translation campaign that took place on Benglai Wikipedia between Feb-Mar 2022 in some months it will be our of the graph.

Regarding the more specific questions:

• Are there any additional charts or filters that would be useful?
  • I have a note to add a chart comparing published, published needing review, and deleted translations to be completed as part of T210138 and T209868.

I think the current set covers the basics well for a first iteration. The following could be considered either to incorporate now (if they were trivial) or for future iterations):

• Number of users and retention. How many different users participate in translation. Maybe this is worth considering combined with the analysis of retention (T226170)
• Some of the data about entry point (T295757) or MT (T310773) reports. I don't know if it would be easy to integrate here, it would be preferred to have a separate dashboard or keep the report format to be run periodically. The aspects of those that could be more interesting to consider could be:
  • MT services used for the selected languages (interesting to correlate with deletions).
  • Percent of MT modifications for published translations (interesting to correlate with deletions)
  • Entry point events (interesting to correlate with published translations)
• As you mentioned: published, published needing review, and deleted translations as part of T210138 and T209868.

• Desktop: There have been 1.48M desktop edits (as indicated by platform = Other). The majority of these translations were used to create a new article (creates new page = True ); however, about 200K (14%) of these edits are recorded as expanding a translation. This is not expected as section translation is not currently available on desktop. This might be a case where non-desktop translations are being included in the platform = Other or a difference in how the create_new_page defines article creation compared to content translation . Will need to monitor to see if this number continue to grow.

On Dektop expanding a section is possible but only in recent months and when knowing the URL for it since it has not been exposed in the dashboard. Thus, I think there are two kinds of data mixed that we may want to separate:

• Expanding by translating a new section. These use the new section translation editor on desktop and are marked with the "sectiontranslation" tag in addition to the "contenttranslaiton" one. There will be very few of them, just from internal testing.
• Article overwrites. A translation is published when there is already an existing article . This can be overwriting a previous article by a different author or publishing a translation multiple times by the same author as a way to continue translating more content. These will have the "contenttranslation" tag but not the "sectiontranslation" one.

Thanks for the great work on this, Megan.
The dashboard looks good to me and I agree most of the additions can be considered as part of separate tickets (or periodically updated reports).

I just have a couple of additional comments:

• For the "Total translations since deployment" we could either (a) apply all filters except the time range or (b) have a set of separate counters for: total, new articles mobile, new articles desktop, sections mobile and sections desktop. Whichever is easier to support.
• The time range selector has no default value for the "end" field. However, when this is left empty, the "Monthly translations year over year" breaks because it needs such value. Having "Today" as a default value for the end period would avoid this issue. If it is not possible to have a predefined value for this, we can totally live with this (just need to remember to add it manually when interested in such graph)

@Pginer-WMF - See updates to dashboard below.

For the "Total translations since deployment" we could either (a) apply all filters except the time range or (b) have a set of separate counters for: total, new articles mobile, new articles desktop, sections mobile and sections desktop. Whichever is easier to support.

I went with option (a) and applied all filters except the time range for the "Total translations since deployment". Now, you can use the other filters on the dashboard to identify the total translations since deployment for any selected combination of platform, activity, language, and namespace. Note there is also a "Total translations for selected time range" count, which can be used if you're interested in the number of translations within a specific time range.

The time range selector has no default value for the "end" field. H

Thank you for catching this! I've updated the time range selector to have a default "end" time of "Today". This should help prevent users from leaving this field empty when adjusting the time range.

Perfect. Thanks @MNeisler !
Option (a) seems great. One minor adjustment to consider in terms of layout. Would it be possible to have the "Total translations since deployment" number next to the "Total translations for selected time range" in the dashboard. In that case we don't need to have a separate section at the beginning, connection with the filters may be more clear, and comparison with the numbers more direct.
Given that this is for internal use, consider this only if it were trivial to apply.

Thanks in advance!

Sure, no problem @Pginer-WMF. I've adjusted the layout to have the "Total translations since deployment" number next to the "Total translations for selected time range" in the dashboard.

Perfect. The dashboard looks great. Thanks for all the adjustments!

(No further nitpicks from my side)