| recent research results.
The basic workflow involves the following steps:
You can check this prototype or the video below for a better sense of how this workflow looks like: More detail on each step below: Home (T359401)A landing page for automatic translations. From there uses can start searching for a specific article to get a machine translation. More details at T359401: MinT MVP: Home Search for topic (T359494)Facilitate finding articles to be translated from languages the user may not know. From multilingual search to searching on a specific language Wikipedia or using identifiers such as Wikidata-Ids or urls. More details at T359494: MinT MVP: Search for topic Confirm (T359512)Represents the selection for topic and languages to translate. Allowing final adjustments to the selected languages, including the exploration of the different language-specific versions of the contents, and surfacing the human created contents as an alternative when available. This serves as the landing step for external entry points. More details at T359512: MinT MVP: Confirm Translation view (T359801)The machine translated contents presented to the user. With indicators and options to identify the contents as machine generated and access the relevant translation-related options. More details at T359801: MinT MVP: Translation view Link preview (T359824)More details at T359824: MinT MVP: Link preview Translation options (T359829)Options for users to adjust and navigate translation-related aspects. More details at T359829: MinT for Wiki Readers MVP: Translation options Explore languages (T359863)On a multilingual context such as Wikipedia, information about a topic can be very different from language to language. Users have a choice to select from which version to translate the contents. This step surfaces which contents can be accessed from each version to help a user explore the different contents available. More details in T359863: MinT for Wiki Readers MVP: Explore languages Entry pointsAccess from language selector (T363183)User use the language selector to switch across the languages they want to read content in. When they look for a language for which content is not available it may be useful to propose a machine translation as an alternative. This expands the current language support for the creation of new articles by translating with an additional option to access machine translation. More details in T363183: MinT for Wiki Readers MVP: Access from the mobile language selector Access from the footer of an article (T363338)Even when an article exists in a given language, the content present may be very different than what is available in other languages. This entry point provides access to machine translation from the page footer. In this way, after users have read a short article, they can find a way to read more about the topic from other languages by using machine translation. More details in T363338: MinT for Wiki Readers MVP: Access from the footer of an article EnablementsCurrently, the MVP is enabled on Test Wikipedia and a set of 23 pilot Wikipedias:
We have followed a gradual deployment approach where we enable the tool gradually and get new feedback on each iteration to improve the tool. These are some relevant tickets in this space:
InstrumentationIn order to check whether this MVP has the expected impact, user actions will be instrumented to analyze in which ways machine translation is accessed:
Related Objects
|
