Is there a way to import a glossary in Storyline 2? Or to do a global edit? Our situation is that we create 6-8 courses in a curriculum for a particular customer, and each one should have the same glossary. Our customer makes updates after we have started developing different modules, each in their own unique file, and with Storyline 1 we had to make the same edit in each file. We tried using the "translation" file but that didn't work well. Just wondering if anything new has been added to export/import in Storyline 2.
There isn't a way to import a glossary into Storyline 2. The suggested method is still the same: to create a template with the glossary and then use that template.
Or, another way described here by Christine Hendrickson
You may have already seen those links - which don't help you with the post-development updates - but figured I'd post just in case, and for anyone else who may come across this thread.
Also, staff will hopefully update here if/when things change for SL2.
Thanks Rebecca. We've done the import. It works fairly well, although we do sometimes have to go back and fix navigation or interactions. I was hoping for a change in Storyline 2 (as well as a good justification for the upgrade!)
Looks like Becky has you covered here - as that's the only current method to import a glossary or resources from another project.
I did also want to point out, that when you reply via email your signature may be included in the post as yours is above. You can edit your post to remove it if you'd like.
I have been asked to import a huge amout of glossary terms. It would be a useful feature to do this by importing a xml or csv file, considering that the structure of the glossary is really simple. The first time you must do this copy/paste manually for each term/definitions, it is really something you don't "deserve"....
There should be an alternative way to import the glossary, that i discovered. Rename your .story extension into a .zip. open it and extract the content to another folder. Find the file playerProps.xml and open it with a html editor. You may want to de-minify the file for better reading. you will find an xml structure, at the end there is a node <glossary>and a subnode ><terms> that contains a structure of 3 subnodes: <term><definition> and <TranslationGuid>. The last one is the id used to name each element for translation. If you have your glossary to be imported defined into an excel file, you can setup the export into an xml node with that structure. The "only" problem is the value of the third node TranslationGuid, that i'm not sure if can be generated using that alphanumeric structure. Any idea?
hi Ashley, I wrote before a way to import, but you must play with xml and generate some random values for the variable "tralsationGuid", it s a bit complicated if you dont know how to manage xml data.
Why oh why is this not a basic feature (ability to import glossary - and resources - content)? Cutting and pasting is not really an acceptable answer. Starting from a template is too late once the course is built.
Please make this a feature request. Generally love Storyline (and Storyline2) but there are odd gaps in functionality - like this - that have me puzzled.
What is the point of submitting requests? I have found dozens of requests for this VERY basic feature - some of which are over 4 years old - and nothing has been done.
Today we released an exciting new feature for Storyline 360: glossary import and export! You'll find this feature in Storyline 360, build 3.30.19518.0. You can see more details on how to use it in this post.
To install, launch the Articulate 360 desktop app on your computer and click the Update button for Storyline. Details here.
13 Replies
Hi Rebecca,
There isn't a way to import a glossary into Storyline 2. The suggested method is still the same: to create a template with the glossary and then use that template.
Or, another way described here by Christine Hendrickson
You may have already seen those links - which don't help you with the post-development updates - but figured I'd post just in case, and for anyone else who may come across this thread.
Also, staff will hopefully update here if/when things change for SL2.
Thanks Rebecca. We've done the import. It works fairly well, although we do sometimes have to go back and fix navigation or interactions. I was hoping for a change in Storyline 2 (as well as a good justification for the upgrade!)
Hi Rebecca,
Looks like Becky has you covered here - as that's the only current method to import a glossary or resources from another project.
I did also want to point out, that when you reply via email your signature may be included in the post as yours is above. You can edit your post to remove it if you'd like.
Thanks Ashley, for the tip on replying via email. My first time doing that, and my last!
I have been asked to import a huge amout of glossary terms. It would be a useful feature to do this by importing a xml or csv file, considering that the structure of the glossary is really simple. The first time you must do this copy/paste manually for each term/definitions, it is really something you don't "deserve"....
There should be an alternative way to import the glossary, that i discovered. Rename your .story extension into a .zip. open it and extract the content to another folder. Find the file playerProps.xml and open it with a html editor. You may want to de-minify the file for better reading. you will find an xml structure, at the end there is a node <glossary>and a subnode ><terms> that contains a structure of 3 subnodes: <term><definition> and <TranslationGuid>. The last one is the id used to name each element for translation. If you have your glossary to be imported defined into an excel file, you can setup the export into an xml node with that structure. The "only" problem is the value of the third node TranslationGuid, that i'm not sure if can be generated using that alphanumeric structure. Any idea?
Hi Zio,
I don't know of any way to import the glossary elements, so I hope that the community is able to assist you here.
hi Ashley, I wrote before a way to import, but you must play with xml and generate some random values for the variable "tralsationGuid", it s a bit complicated if you dont know how to manage xml data.
Hi Zio,
You're welcome to share the steps here and then those users who do know how to work with the XML data would have that as an option.
Why oh why is this not a basic feature (ability to import glossary - and resources - content)? Cutting and pasting is not really an acceptable answer. Starting from a template is too late once the course is built.
Please make this a feature request. Generally love Storyline (and Storyline2) but there are odd gaps in functionality - like this - that have me puzzled.
Thanks Nancy for chiming in here and you are also always welcome to submit feature request here as those go directly to our product development team.
What is the point of submitting requests? I have found dozens of requests for this VERY basic feature - some of which are over 4 years old - and nothing has been done.
Hi all,
Today we released an exciting new feature for Storyline 360: glossary import and export! You'll find this feature in Storyline 360, build 3.30.19518.0. You can see more details on how to use it in this post.
To install, launch the Articulate 360 desktop app on your computer and click the Update button for Storyline. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.
This discussion is closed. You can start a new discussion or contact Articulate Support.