Langauge translations in one SCORM - issue with passing score to LMS and states delay

Jan 15, 2020

Marek Olejnik
By Marek Olejnik

Hi,

I have big issue with keeping diffrent translations in one course. Due to some technical issues we can't upload diffrent SCORMs of the same course to the LMS. So all languages need to be in one SCORM file. Also SCORM is passing only percantage to the LMS, and we need points (this is calculated by setting max score in LMS and then multiplied by %). Scores are displayed in the Top Score list. Now we have this course live and uploaded with only one language and everything is working fine. But we need add more languages and for now I can't make it work on 100%. I decided to fetch lang indentifer from url (for ex. story.html?DE), store this as variable and then do stuff coresponding to the variable (this works fine, no issues here). My solutions so far and the results:

 

- Option 1: duplicate whole scene (it's short course so everything is on one scene) with course and translate it. On the first slide I put trigger, if var lang = DE then jump to slide 1 on scene DE. This is working great on the frontend, but as you can imagine, it doesn't work on the backend. In SCORM export I can choose only one result slide which pass score to LMS, and with duplicated scenes I have that many results slide as languages. So results are passed only from one language.

- Option 2: is variant of option 1, all languages on separate scenes, but only one result slide (last slide on each language points to the same results slide).  This works on frontend (we only need show points to the user), and kind of on backend. Issue with this solution is that I need to pass all slides to the results slide. So top score will change, and we already have this value hard coded in LMS. With one language we had max 100pts, and if user get 50% he get 50pts and this value is displayed on the top score. But with 3 languages, max is 300pts, so 50% will be 150pts. We need to update this value in LMS, so all old scores will be affected. And when in the future we will add new language, this will happen again. So this solution will work only if have complete course before uploading to LMS and don't add any new languages to it. In our case, useless

 

- Option 3: that's only fully working solution, but also with issue. Everything on one scene, and on the all texts I add another state which is translated to desired language. On each slide trigger if var lang = DE, change state of txt to DE when timeline starts. It works on frontend and backend, scores are ok. Only issue is that SL have some very small, but notciable, delay before changing state. So for half of second I have english text and then it switches to german. So not elegant and I don't really like it. I also tried adding new language as new layer, but lag still exist. I

 

I don't have any other idea, maybe someone of you faced similar issue and found solution? If something is not clear, please let me know, I tried to describe this as clear as I can and not to make essay, but still post seems quite large...

 

Thanks in advance for any tips!

Cheers

5 Replies
Judy Nollet
over 4 years ago01/15/20 at 7:18 pm (UTC)

Hi, Marek,

Instead of putting translations into different states, try this:

  • At the start of the course, set your language variable (which I think you're already doing).
  • On each slide, put all the text on different layers, one layer for each language. That includes a layer for the English text.
  • On each slide, add triggers to show the appropriate layer based on the variable. Like this:

Because there's nothing on the base of the slide, users won't see the course switching from English to the chosen language.

For the quiz, have the response buttons on the base, but put the question and the response text on layers. To keep that text visible if you're including feedback layers, set the feedback layers so they don't hide other layers when they appear.

The disadvantage to this approach is that it's more complicated to program an interaction that uses layers (though that would still be doable). But it would allow you to keep all the languages in one course and still send an appropriate score to the LMS.

Judy Nollet
over 4 years ago01/16/20 at 12:02 pm (UTC)

Hi again, Marek,

It occurred to me last night that you really only need to do the language layers on the quiz slides. In other words, have one scene of content slides for each language (which is simpler than all the languages on every slide). Each of those scenes leads to the same Assessment scene, where all the languages are on each question. 

Marek Olejnik
over 4 years ago01/16/20 at 12:24 pm (UTC)

Hi,

hmm, in my case I think it will be more complicated. Current setup is:

Scene 1: [info] -> [quiz] -> [info] -> [quiz] -> ... -> [results]

In your solution (if I get it correct) I need to:

Scene 1: [info] -> go to Scene 2 -> [info] -> go to Scene 2 -> [info]

Scene 2: [quiz] -> return to Scene 1 -> [quiz] -> return to Scene 1 -> [quiz] -> [results]

 

So there will be a lot of jumping between scenes, and I can't avoid add extra translation layers to quiz. So I think I will keep to the layers solution only, it seems more clear solution.

However your solution could be usefull on the project with a lot of info but only few quizes.

Thanks for the other solution, I think it could get handy in the future :)

This discussion is closed. You can start a new discussion or contact Articulate Support.