Glossary Issues

Jan 03, 2017

Building 26 ELearning courses with the same glossary.  I understand that using the same glossary requires building a template that can be used with all 26 courses. When updating the glossary is it possible to update it without changing all 26 courses. If so, how do I do it?


4 Replies
Judy Nollet

Alas, when you use the built-in Storyline Glossary, you have to update it in each course when revisions are needed.

An alternate option might be to create the Glossary as an Engage interaction and insert that into every course (e.g., add a player-level button to lightbox the slide with the interaction). However, you would still have to re-insert the Engage file after updating it to ensure the course published the most recent version. (Yeah, even that sounds like a lot of work, especially if it's a simple revision. It might not be too bad to do it that way if you can get approval on the Glossary before importing it to all the courses.)

In short: There's no automatic way that I know of to update all the shared Glossaries at the same time. That'd be a good feature request!


Michael Shannon

Another possibility is to use a web object. If you have all of your .story files in the same folder you can create a folder within that folder for the glossary. Then create a glossary page within that folder and call it index.html. When you add the web object to the storyline page you click the folder icon and find and select that folder on your hard drive. If you do this for all of your courses they will all use the same file and you'll only need to edit it once. You can make it look any way you want. 

One caveat: after adding the web object, if you edit the file you should change the name of the folder and relink the webobject on all of your .story files to this new folder name. I usually  just put a version number on it (glossary_v01). I'm not sure why this is, but I think what happens is when you add a webpage it creates the link and in this instance caches the page. When you publish I don't think it looks at that page again. That's my best guess. 

Hope this helps. 

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