Page MenuHomePhabricator

Connect MediaWiki translation interface to Qualtrics.
Open, Needs TriagePublic

Description

In order to facilitate translations from CE insights, it would be great to have a way to automatically export a translation done using Extension:Translate to Qualtrics.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 8 2016, 12:27 PM

I believe that @Ijon, @ThatAndromeda was working on making mediawiki translation extension talk to qualtrics. Is this still happening?

We were able to find a way to use google spreadsheets to simplify the process, but its still not as ideal as removing the manual work altogether.

Thanks!
E

It is possible to import a CSV on MediaWikiwiki, mark it for translations and when translated to copy everything to re-import it on Qualtrics, but, trust me, that's long and very painful.

Nikerabbit moved this task from Backlog to Watching on the User-Nikerabbit board.Sep 14 2016, 7:18 AM

Does Qualtrics provide any kind of APIs?

Yes but also no. Qualtrics APIs allow for automating some of this process, but they don't expose the translation system.

(Yes, @Ijon and I are still working on this.)

Thanks @Trizek and @ThatAndromeda. I've figured out a way to export a csv and translate using google sheets. It's easy/fast to use, even though its not ideal (because its google). But still looking forward to the mediawiki translation :)

Nemo_bis updated the task description. (Show Details)Oct 24 2016, 12:46 PM

LimeSurvey uses an XML format, which might be easier to support (in FFS rather than page translation): https://manual.limesurvey.org/Exporting_a_survey_structure

I've figured out a way to export a csv and translate using google sheets

How is that easier than copy and pasting CSV files hosted in wiki pages, which seems to be what Trizek was doing?

If you want this task to proceed, please provide Qualtrics documentation on what formats they use and how they can be loaded/imported/deployed automatically.

Thanks @Nemo_bis for the ping on this.

You can find all the information about translating here:
https://www.qualtrics.com/support/survey-platform/survey-module/survey-tools/response-management-tools/translate-survey/

The things I did differently from these instructions are:

  • we had many scales (strongly agree/disagree, difficult/easy, etc.) that were the same for several questions. To save time and reduce error, I only asked these be translated one time, and then used something like VLOOKUP and filters to help me duplicate these responses.
  • We translated into about 11 languages and it was going to be messy having all in one spreadsheet, so I split it up; one language per spreadsheet, and then used VLOOKUP to bring in the data back to the original file, since each translated item has a unique id.

Thanks for the answer.

  • we had many scales (strongly agree/disagree, difficult/easy, etc.) that were the same for several questions. To save time and reduce error, I only asked these be translated one time, and then used something like VLOOKUP and filters to help me duplicate these responses.

Translate has a translation memory, so if you translated the spreadsheet with Translate this would be unneeded.

  • We translated into about 11 languages and it was going to be messy having all in one spreadsheet, so I split it up; one language per spreadsheet, and then used VLOOKUP to bring in the data back to the original file, since each translated item has a unique id.

Perfect! Translate would create a separate CSV for each language, each in its own subpage.

I'm not saying using spreadsheets is ideal; but if you do, Translate seems to be still the easiest system.

Ok, so it seems they don't have a function to automate imports, perhaps because they want to force people to buy translation services from them instead. I sent the following request for clarification, you may want to ask more:

I would need to know how to import translations programmatically, e.g. with an API or by fetching updated localisation files for all languages automatically/on demand from a git repository. The localisation files should be in some standard format The page also doesn't describe how grammatical localisation is handled, e.g. messages varying by grammatical gender or plural rule for the related numbers.

Given they only support manual importing of CSV files, I see little more that Translate can do: we could export CSV files to a repository but you'd still have to download them (e.g. in a ZIP file) and upload them one by one. So there seem to be just two options:

  1. keep doing the same things, just with the page translation feature;
  2. switch to a more user-friendly survey system like LimeSurvey and automate imports https://manual.limesurvey.org/Importing_a_survey_structure .

At this point you can upload a file with all or any of your languages—no need to import one at a time

If this is true, then it would be possible to do something that compiles all the translations into one file from Translate. But they don't explain what is the format of such file that contains multiple languages.

Is this still a valid task that someone plans to work on, and is this tracked in Phabricator?