Forum Discussion
Glossary import Export
yes you can, but it needs a bit tweaking, I explain how:
You must know that each .story file is a sort of big zip archive, so you can access several resource inside it, by renaming from .story to .zip.
So the first step is renaming the source glossary ,story file to .zip,
Extract the content into a folder, enter the subfolder "story" and open the file named "playerProps.xml" that contains all player properties, included the glossary therms and definitions. All the data you need is inside the <glossary> node (and subnodes).
What you need to do is to copy all the tag and content
<glossary> ..... </glossary>
from the source playerProps.xml file to the destination (inside the course you need to import the glossary).
so you need to rename the destination .story file to .zip, extract the content, open the "story/playerProps.xml" file inside the archive, paste the <glossary> node from the source file, save it, recreate the archive, rename it to .story.
You may find difficult to identify the <glossary> node since the file xml is "minified" (no word-wrapped to save space), you cand search the file for the <glossary> and </glossary> string to identify the node to copy (it is near the end of the xml), in editors that support tag recognition (i.e. Dreamweaver) you can easily select all the tag from the opening to closing declaration, or as an alternative you can de-minify the xml for better viewing (there are several online copy/paste tool to do that) and then minify again the xml file.
this is a bit tricky, but it can save you lot of time, expecially if source and destination .story use very different themes/templates, or if you need to move the glossary quickly from existing courses, or also if you need to translate glossary in other languages.
- MiriamKrajewski3 years agoCommunity Member
Thanks Zio, this is brilliant. Then I read to the end of the thread and realized Articulate has added an export option, so thanks as well to Ashley! But I'm very impressed by your workaround Zio, and it taught me something about how to look "under the hood" of a Storyline file.