Multiple Storyline files in one course

I'm trying to determine if there is a way to combine multiple storyline files into one course. I've searched and read the various threads about combining multiple SCOs into one multi-SCO course using Simple SCORM Packager or the Dreamweaver Manifest Maker extension, but what I am trying to do is slightly different...

I'm trying to create a multi-Language course. So rather than having a situation where the user is expected to complete all of the individual elements, I'm basically trying to create multiple versions (different languages) of the same content and the user has to just complete one.

All versions would launch as one course from the LMS, but the user is expected to simply branch to the appropriate language and then complete the content for that language.

The straightforward way of doing it would be to include all the various language branches within one Storyline file, but the size of the course and number of languages makes doing that unrealistic.

Has anyone done anything similar, or have any thoughts?

Thanks!

8 Replies
Nicole Legault

Hey David

Interesting topic, thanks for posting it here. I think you're right that having all the branches within one Storyline file could be unrealistic if it's a larger course. 

What you might want to consider is just developing your courses for different languages as different published modules. Usually an LMS will allow you to decide which course you assign to a learner, so you could hopefully just upload all the various languages to your LMS, and then only assign the learner the version in the appropriate language. 

Hope this helps and hope to hear some input from other community members with experience in this area. Good luck :)

Steve Flowers

You can assemble multiple languages into a single SCO. Sometimes this is preferable to publishing separate SCO's and having to aggregate reports. 

This method is pretty simple. An example is described in this thread:
https://community.articulate.com/discussions/articulate-storyline/localization-strategy-and-variables#reply-190324

This requires some post-publish surgery. This requires adding folders for each language within your SCO and the addition of an HTML file that the imsmanifest points to. This page provides links to each of your separate published SCO folders. 

 

David Oskorus

Hi guys-

Thanks for the replies.

Nicole- thanks! That would be the most straightforward way to handle it. Unfortunately my company is being contracted to build the course and the expectation is that we will be delivering one package.

Steve- thanks for the redirect and the response to the original thread. That is exactly the kind of thing I was thinking of and you and David touched on a lot of the things I was thinking could be potential issues... time out before language selection & potential misinterpreting of suspend data.

Love the "If the risk is low, maybe let it ride." I'll have to remember that. ;-)

I have downloaded the sample you posted and will start building my prototype. I'll update this thread with any additional questions or discoveries.

Thanks!

Julie B.

Hello all,

I know this thread is quite old here...BUT I am very interested in better solutions than what was discussed here a year ago..

I mean we face exactly the same situation: one course in 11 languages, every month, in different departments and for more and more courses developments ...

Nicole:

The LMS is not the solution in our case ....it basically can assign a course to a user (based on a SAP flag) but it can't  offer him the possibility to choose between 11 versions in a simple way..(would be to assign everyone with 11 courses...) (this is a very rough sum up of our nad LMS situation!)

David:

we have developed this "post-publishing" surgery file and it works fine...the learner enters a "Select your language" menu interface...and , the learner can chose one language, or exit, it loop sto the menu and select another one...and complete only one course...It works well....on PC but .but don't work on our LMS mobile app as it does  not loop back to the menu....

Well...my question is:

Did anyone found any easier way? we manage more and more developments here and they all have to follow this post-publishing delicate surgery operation... :( , it is too difficult and teckky for every Training developers ...Do you happen to have discovered or developed any easier tool that would provide this "surgery"?

THANKS A LOT

David Oskorus

Hi Hassaan-

The method that Steve described above worked for us with the particular client and their LMS. We've since created a few courses for them in a similar manner.

You can use the attached as a starting point. It's set up for four languages, but you can easily add more. The published files for each language go (unzipped) in each of the language sub-folders and the manifest and meta files in the root need to be updated accordingly.

Note: These were published as HTML5 only, SCORM 2004. But the basic folder structure should work for any setup. Adjust as needed.

...And as with anything, be sure to test thoroughly before investing too much into this one solution.

Good luck!

Lindy Mantin

Yeah....and yes, this all sounds good but is difficult for those of us who design but don't have a programming background!!!   In our global market it would be awesome to have a way of creating on package in two languages!  and having it provide question level reporting to our LMS.

I see David's answer below and downloaded the zip file....but where and what do I do with it?

 

David Oskorus

Hi Lindy-

Sorry, I know it can be daunting. That said, if you can do a little html and xml editing, it's actually pretty straight forward.Let's say you are creating a course called "Intro to pizza" with English and Spanish versions...

Create a new folder on your local drive. Call it "intro_to_pizza". Unzip the contents of the template into the new folder. You'll have the following folders:
intro_to_pizza/_images
intro_to_pizza/ENG
intro_to_pizza/ESP
intro_to_pizza/HAT
intro_to_pizza/VIE
...As well as a number of files.

Delete the 'HAT' and "VIE" folders.
Delete 'lang-HAT.png' and 'lang-VIE.png' from the '_images' folder.
(If your languages are different, you will need to create appropriate language buttons.)

Publish the English version of your course and place the published (not zipped) output in the 'ENG' folder. (NOTE: when you publish, the output is created in the location you specify inside a folder named after the course title. Do NOT move the folder to the 'ENG' folder. Move the contents of the folder to the 'ENG' folder.)

Do the same for the Spanish version of the course. Place the output in the 'ESP' folder.

Now the "hard" part...

In the course root (the 'intro_to_pizza' folder) find 'index_scorm.html' and open it in your favorite html or text editor.
Change the title in line 5 to:
<title>Intro to Pizza</title>
Remove the links to the other two languages by deleting lines 62 and 63.
Save and close your file.
This is the file the LMS will use when the course is launched.

In the course root (the 'intro_to_pizza' folder) find 'index_non-scorm.html' and open it in your favorite html or text editor.
Change the title in line 5 to:
<title>Intro to Pizza</title>
Remove the links to the other two languages by deleting lines 62 and 63.
Save and close your file.
This is the file you will use when you simply want to launch the course locally.

In the course root (the 'intro_to_pizza' folder) find 'imsmanifest.xml' and open it in your favorite xml or text editor.
Search and replace all instances of 'multi_language_course' with 'intro_to_pizza'
Search and replace all instances of 'Multi Language Course' with 'Intro to pizza'
Delete lines 43 and 44. These reference the two language buttons you deleted.
Save and close your file.

Zip everything in the 'intro_to_pizza' folder (not the folder itself) to create the course package.

Stage and test.

PLEASE NOTE: I tried to keep this as simple as possible. As such I left some things out that technically should be done (like updating the manifest resources as well as the meta.xml file). Most LMS systems are pretty forgiving as long as it can parse the xml, so rather than scare you away from attempting this at all, I thought it better to leave that stuff out.

Good luck!