New data decision breaks translations

[mschwamb]

The new galaxies and illustrus simulated galaxies when shown in the interface are not pulling the translation jsons. @chrissnyder it appears to be impacting all the translations and that they are pulling the english text. This was brought up by the ASIAA EPO office. I'm not sure how long this has been going on ,but likely since the launch of the data.

[mschwamb]

If it's that those sections of the decision tree have new components to the json, if I'm sent the traditional character Chinese json and the english json I can get the ASIAA EPO staff to translate the additional text.

[willettk]

Both decision trees had new text (although the Illustris ones really should just re-use the Sloan wording to make things like this simpler). I recall we couldn't figure out how to properly do that at the time, but it'd be useful now since that'd re-enable the language support for all the existing translations, at least for half of the subjects.

Can you have your collaborators just use the interface at translations.zooniverse.org, @mschwamb? The new text snippets to translate should be up there.

[mschwamb]

Originally we translated galaxy zoo by json, maybe at that time the translations website wasn't ready? It appears I have access, but I may need to have the development team give the translators access through the translation tool.

I'm not sure how useful that classification data would be with some things translated and other portions/tasks showing up in English. We were planning on using Galaxy Zoo for an open house event in Taiwan, but since we didn't know that the translations needed updating we won't have that done in time. Maybe something to think about in the future for how translations are upkept and translators notified of text needed updates in the future for Zooniverse projects.

[willettk]

Totally agree on the updating aspect; I don't know who handled most of the
translation work for GZ, and it didn't occur to me to send out a call for
the new translations when we launched the new data. At minimum, that might
be a good thing to add into the "best practices for science teams"
documents; from the technical standpoint, it would be useful to have an
email list (or a button) notifying anyone who contributed translations to a
project that new content is available and needs attention.

On Fri, Oct 30, 2015 at 11:21 AM Meg Schwamb [email protected]
wrote:

Originally we translated galaxy zoo by json, maybe at that time the
translations website wasn't ready? It appears I have access, but I may need
to have the development team can the translators access through the
translation tool.

I'm not sure how useful that classification data would be. Some things
translated and other portions/tasks how up in English. We were planning on
using Galaxy Zoo for an open house event in Taiwan, but since we didn't
know that the translations needed updating we won't have that done in time.
Maybe something to think about in the future for how translations are
upkept and translators notified of text needed updates in the future for
Zooniverse projects.

—
Reply to this email directly or view it on GitHub
#233 (comment)
.

[mschwamb]

@willettk I've heard about this best practices document mentioned before, but don't know much about it. Translations is a Zooniverse core team/development team issue I think, not a science team issue. Especially right now since it only exists for non-panoptes projects.

There is a set of translators per project who did the work (and their contacts that the development team has) and an admin account has to give permission on the Zooniverse translations site for someone to access a project to begin translating it. Also once completed a developer has to do the deploy (and sometimes there are some technical things that need addressing with the specific translation).

I've provided the human interface between the ASIAA translators and development team. I don't know who's going to be taking on translations in the near future. Happy to give some input if someone wants to hear what things I think have worked well and could be improved in terms of translations and getting them live.

[willettk]

Thanks, @mschwamb - I'd like to talk more about that too, if a conversation
can be started.

For the immediate future - if you have the contact information for the
ASIAA translators, could you either put them in touch with me, or let them
know that there are new fields on the GZ site that they can access through
translations.zooniverse.org? The most important thing to tackle are the new
text for the questions.decals and questions.illustris fields - I can talk
to them if they have any specific questions about wording.

On Fri, Oct 30, 2015 at 11:33 AM Meg Schwamb [email protected]
wrote:

@willettk https://github.com/willettk I've heard about this best
practices document, but know much or anything about this. Translations iss
a Zooniverse core team/development team issue I think, not a science team
issue. Especially right now since it only exists for non-panoptes projects.

There is a set of core translators (and their contacts that the
development team has) and an admin account has to give permission on the
Zooniverse translations site for someone to access a project to begin
translating it. Also once completed a developer has to make the deploy
translations (and sometimes there are some technical things that need
addressing with the translations).

I've provided the human interface between the ASIAA translators and
development team. I don't know who's going to be taking on translations in
the near future. Happy to give some input if someone wants to hear what I
things have worked well and could be improved in terms of translations and
getting them live.

—
Reply to this email directly or view it on GitHub
#233 (comment)
.

[mschwamb]

it's already being done. I got the translators access to the Galaxy Zoo section, so that they can now see it.

I do recommend that all of the translations should be pulled from Galaxy Zoo ASAP until they are up to date. The backend records what language the site says its in, but currently for all translations it's giving wrong information. You might get some spurious classifications for the more popular translations as all of the decision tree and help is now in english.It's also not very welcoming to someone who switches to the translation and then sees the rest of the site is translated but the decision tree.

[willettk]

I don't think pulling the translations is a necessary step; I don't want to
lose the data from the translations, and the pictographs + help images
should be designed (I hope) so that classifiers even with no knowledge of
English could give it a reasonable go. It's also not giving "wrong
information" - it just gives the English version of the text if it can't
find the corresponding translation.

I'm all for updating the translations ASAP (I've asked Zooniverse for help
in contacting the other translators), but we can look at the
classifications in post-processing if we think it's necessary. Every
analysis I've seen on the Galaxy Zoo data so far doesn't show any
meaningful difference in interface language.

On Thu, Nov 5, 2015 at 4:28 PM Meg Schwamb [email protected] wrote:

it's already being done. I got the translators access to the Galaxy Zoo
section, so that they can now see it.

I do recommend that all of the translations should be pulled from Galaxy
Zoo ASAP until they are up to date. The backend records what language the
site says its in, but currently for all translations it's giving wrong
information. You might get some spurious classifications for the more
popular translations as all of the decision tree and help is now in
english.It's also not very welcoming to someone who switches to the
translation and then sees the rest of the site is translated but the
decision tree.

—
Reply to this email directly or view it on GitHub
#233 (comment)
.

[mschwamb]

Perhaps because I currently live in a foreign country where English isn't a primary language I have a different perspective and where getting outreach and science materials in the local language is difficult. Not my project, so I realize my vote doesn't matter. I'll coordinate with the Zooniverse development team on the traditional character chinese version. good luck with the rest of the translations and the new decision tree.

[willettk]

I sent a broad email out a few weeks ago to all the translators asking for help on updating the new text in GZ. I got very little direct response - do you know if any of your colleagues in Taiwan got that, @mschwamb?

[mschwamb]

I don't know, they haven't spoken to me about it. I know when they have time they've been trying to translate when they have. I can inquire.

I get the feeling most translators ebb and flow in business that perhaps you want to be a blog post out asking for volunteers?

[willettk]

That's not a bad idea - I'll ask Grant about the best time to do that.

On Sat, Dec 12, 2015 at 6:52 PM Meg Schwamb [email protected]
wrote:

I don't know, they haven't spoken to me about it. I know when they have
time they've been trying to translate when they have. I can inquire.

I get the feeling most translators ebb and flow in business that perhaps
you want to be a blog post out asking for volunteers?

—
Reply to this email directly or view it on GitHub
#233 (comment)
.

[mschwamb]

Though once you get that they need to be given permission to access Galaxy Zoo on the translations tool. My understanding was that Chris S took over dealing with that. I'm not sure if there's now a Zooniverse core team member or developer who's in charge of translation now or if any Zooniverse core team member can give access. I always had to ask Chris S to give permissions per zooniverse account and per project being translated.

[murraycu]

So many of the strings in new surveys are identical to the same questions in older surveys, that there should probably be some automatic copying when adding the new survey.

[willettk]

I couldn't agree more. It's done for a few of the trees here: https://github.com/zooniverse/Galaxy-Zoo/blob/master/app/models/question.coffee#L56

But I couldn't figure out how to properly do that question by question for the DECaLS and Illustris decision trees (admittedly it might have started to get very clunky). I'd think it was possible to retool the site to do automatic copying of selected strings, though I don't know how to do that myself. I'm going to open a new issue for that. (#244)

[bamford]

Are the translations also broken for the current data sets (including GAMA)? If so, can anyone advise how to go about fixing them?

[eatyourgreens]

There aren't any translations yet for the new questions. You can see them by logging in to http://translations.zooniverse.org

[mschwamb]

I believe that would require contacting the previous translators and asking them to fill in the content.

[eatyourgreens]

Hebrew translation is up now for the new decision tree. That was fast.