Fix Machine Translation Service code names to be consistent
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	MNeisler
	Sep 27 2022, 4:44 PM

Project Tags

Referenced Files

None

Subscribers

Description

When reviewing recent translation data for the analysis in T310773, I noticed that there are a couple of machine translation services that have inconsistent internal code names in the data (source: cx_corpora cxc_origin field.). See details below:

Google and Google Translate
154 total translations tagged with Google Translate instead of Google. Details below:

First Google Translate instance occurred on 13 July 2022
Last Google Translate instance occurs on 04 August 2022
Since 04 August 2022, all Google translations have been correctly tagged as Google so far.

Yandex and Yandex.Translate
Only 1 translation was tagged with Yandex.Translate. Details of the translation below:

translation start time: 28 July 2022.
Source Language: en
Target Language: mr

Can you please review to confirm if the code names for each Machine Translation service are consistent?

Related Objects

Mentioned Here: T317293: Translation options are not using the user-facing name for the services
T310773: Re-run and update the MT service usage report

Event Timeline

MNeisler created this task.Sep 27 2022, 4:44 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 27 2022, 4:44 PM

MNeisler updated the task description. (Show Details)Sep 27 2022, 4:52 PM

MNeisler added a project: Language-analytics.Sep 27 2022, 4:56 PM

MNeisler moved this task from Backlog to Tracking on the Language-analytics board.

Pginer-WMF added a project: Language-Team (Language-2022-October-December).Sep 28 2022, 1:48 PM

Pginer-WMF triaged this task as Medium priority.Sep 28 2022, 1:50 PM

Pginer-WMF moved this task from Quarter Backlog to Priority: Unified Content & Section Translation on the Language-Team (Language-2022-October-December) board.Oct 3 2022, 9:01 AM

Following our latest work for the user-facing names of the MT services (T317293), I think that this task is no longer relevant, as we are only using user-facing names like "Google Translate" for the UI and the proper MT names (e.g. "Google") for all the underlying functionality, including cx corpora translation units. However, this task cannot easily be verified by QA.

Thanks Nik.
@MNeisler, this is expected to be resolved. Let us know if you find similar inconsistencies in the future.

Fix Machine Translation Service code names to be consistentClosed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Fix Machine Translation Service code names to be consistent
Closed, ResolvedPublic
Actions