I'm looking for a quick way to populate the Glossary in Storyline. I already have a large Glossary built. I do not really want to copy/paste each word/definition manually?
Is there a rapid way of doing this?
I'd like to have the same Glossary to appear in ALL my 11 different Story files. How do I do this? Do I build a template with the glossary built in?
Thanks, Michael. Good to know this could work if a glossary had been built previously in Storyline, I was more thinking that a glossary might have been built in a separate application, and wondering if there was a way to import it.
Thanks, Michael. Good to know this could work if a glossary had been built previously in Storyline, I was more thinking that a glossary might have been built in a separate application, and wondering if there was a way to import it.
Thanks, Michael. Good to know this could work if a glossary had been built previously in Storyline, I was more thinking that a glossary might have been built in a separate application, and wondering if there was a way to import it.
Agreed. I'd like the ability to create a single glossary in another application (i.e. Engage) and have the option to open up the glossary from within the Glossary menu option. That way I can maintain one centralized glossary and link to it from multiple SL courses.
Then again, I suppose I could remove the Glossary menu option, and create a resource called "Glossary" under the Resources menu.
Hy ! I'm new to articulate Storyline I created a glossary and I have no problem at all, except that I would like to know how to create a different on (glossary) on different scene so the learner can see only the one's that applied to that module, not all.
Welcome, J: If you've got access to Articulate Engage, you might bring in separate engage glossary interaction. Of course it wouldn't totally match the Storyline glossary, but you could also do that one in Engage (again if you had access to it.)
Hi J, and welcome to Heroes! You'll find the community here can offer great suggestions and ideas to help you accomplish what you'd like to do - so if you need anything else, just let us know!
Is the answer No, you can't upload say and excel spreadhseet with glossary terms and definistions? Do I really have to copy and paste 50 words and definitions if I want to stick with the Storyline glossary and not have to build a workaround?
Are you referring to Cheryl's question? You can't import a set of glossary terms/definitions from an excel file, but it would make a great feature request!
is there a way to print or export a Storyline Glossary? It is very hard to remember what is in the Glossary when you are going back and forth with your course/glossary.
Unfortunately not, although you could look at creating your owncustom glossary, in a lightbox or similar? That would allow you a bit more flexibility in terms of how it's triggered and shown to the user.
@ J Callodo. I am not new to Articulate but have the same question.
"I would like to know how to create a different on (glossary) on different scene so the learner can see only the one's that applied to that module, not all".
I don't know if I would call this "easy" but it is workable for the scenario of a *single* glossary that you might wish to port from another application, or between multiple projects, and *IF* you dont have an aversion to HTML/XML editing.
Essentially what I did was:
Publish a sample story with a few glossary [place-holder] terms in it (note: the [place-holder] term or terms should include all the characters you expect to see in your glossary, as they need to be included in the "fonts.swf" flash file to be rendered properly... [sigh].
Went looking in the published content to find the place where the glossary data was stored
Edited/replaced the data once I found it.
Turns out the glossary data is stored as an XML node in the "frame.xml" file that I found in the story_content folder of a published project. Open the "frame.mxl" file and look for the "glossary_data" node.
Once you find it, you simply need to make your data fit that structure, EXACTLY. And, to be sure, there are some rather, um... "wonky" bits of encoded HTML code in the exported XML (e.g., "<html><p") ... I think for text formatting; No matter what their purpose, you need to have them, otherwise you will not get the glossary working. You'll find them on both sides of your content.
Sidebar: I will try to attach the "template" I made, to use for future projects, for reference if anyone wants it, but I would suggest you publish your own, to make sure your actual version matches your project.
I already had an XML file of my existing data (i.e., wanted terms), but you can export one from many applications easily enough if you don't... and don't even necessarily need to start with one, as long as you *end* with one.
So, with my data and that code from the "frame.xml" file (which you can hopefully see in my attached file) I produced a chunk of code that had the structure of the "glossary_data" node and my content.
Hint: there are applications that allow you to search for and modify specific tags to make this easy... you can even remove tags and leave their contents, if necessary.
After that I BACKED UP THE ORIGINAL "frame.xml" file, just in case, and then replaced the original glossary_data node with the new one I created with my actual data, and presto, new, working glossary full of terms I wanted but did not have to paste one by one.
Sadly I could not bring that back into the file, but adding a bit of XML to a published doc is easier than copying and pasting a bunch of terms over and over...
You can edit glossary directly in Storyline source file. It is not good way, but sometimes not good way is the best possible way.
You must change the extension of source file from ".story" to ".zip" and unpack the file to some folder. There you will see (in subfolder "story") file "playerProps.xml". Glossary is there, almost on the end. Edit what you need, zip, change file extension to ".story" - and that's all.
25 Replies
Hi Gary,
I don't have the answer, but I think it's a really good question. I wonder if there's a way to import a glossary somehow. So, I'm subscribing here!
Hi folks...
This has been an item for discussion at least a few times on the Art boards. Taake a look at: http://community.articulate.com/forums/t/12522.aspx
MJF
And here: http://community.articulate.com/forums/t/15780.aspx
MJF
Thanks, Michael. Good to know this could work if a glossary had been built previously in Storyline, I was more thinking that a glossary might have been built in a separate application, and wondering if there was a way to import it.
Me too
Agreed. I'd like the ability to create a single glossary in another application (i.e. Engage) and have the option to open up the glossary from within the Glossary menu option. That way I can maintain one centralized glossary and link to it from multiple SL courses.
Then again, I suppose I could remove the Glossary menu option, and create a resource called "Glossary" under the Resources menu.
ah! Sometimes the workarounds are so easy, you completely overlook them. Great idea,Mark!
I still want to be able to import a Glossary from another format, say .csv.
Hy ! I'm new to articulate Storyline I created a glossary and I have no problem at all, except that I would like to know how to create a different on (glossary) on different scene so the learner can see only the one's that applied to that module, not all.
Thank for U help
Welcome, J: If you've got access to Articulate Engage, you might bring in separate engage glossary interaction. Of course it wouldn't totally match the Storyline glossary, but you could also do that one in Engage (again if you had access to it.)
Hi J, and welcome to Heroes! You'll find the community here can offer great suggestions and ideas to help you accomplish what you'd like to do - so if you need anything else, just let us know!
Is the answer No, you can't upload say and excel spreadhseet with glossary terms and definistions? Do I really have to copy and paste 50 words and definitions if I want to stick with the Storyline glossary and not have to build a workaround?
Hi Tricia,
Are you referring to Cheryl's question? You can't import a set of glossary terms/definitions from an excel file, but it would make a great feature request!
Yes, I was referring to Cheryl's main question. This would be a great feature. Thanks!
Thanks Tricia, and I agree - it would be a nice feature to request.
is there a way to print or export a Storyline Glossary? It is very hard to remember what is in the Glossary when you are going back and forth with your course/glossary.
Hi Wendy,
There isn't a way to export a glossary - although you could try keeping it open in a new Storyline template so that you could toggle back and forth easier.
Is there a way to link to your glossary from within a slide? That way if they click on a word, it will take them straight to the glossary?
Hi Courtney,
Unfortunately not, although you could look at creating your own custom glossary, in a lightbox or similar? That would allow you a bit more flexibility in terms of how it's triggered and shown to the user.
Hope that helps!
It does, thanks!!
@ J Callodo. I am not new to Articulate but have the same question.
"I would like to know how to create a different on (glossary) on different scene so the learner can see only the one's that applied to that module, not all".
Has anyone found a workabout for this one yet?
I don't know if I would call this "easy" but it is workable for the scenario of a *single* glossary that you might wish to port from another application, or between multiple projects, and *IF* you dont have an aversion to HTML/XML editing.
Essentially what I did was:
(note: the [place-holder] term or terms should include all the characters you expect to see in your glossary, as they need to be included in the "fonts.swf" flash file to be rendered properly... [sigh].
Turns out the glossary data is stored as an XML node in the "frame.xml" file that I found in the story_content folder of a published project. Open the "frame.mxl" file and look for the "glossary_data" node.
Once you find it, you simply need to make your data fit that structure, EXACTLY. And, to be sure, there are some rather, um... "wonky" bits of encoded HTML code in the exported XML (e.g., "<html><p") ... I think for text formatting; No matter what their purpose, you need to have them, otherwise you will not get the glossary working. You'll find them on both sides of your content.
Sidebar: I will try to attach the "template" I made, to use for future projects, for reference if anyone wants it, but I would suggest you publish your own, to make sure your actual version matches your project.
I already had an XML file of my existing data (i.e., wanted terms), but you can export one from many applications easily enough if you don't... and don't even necessarily need to start with one, as long as you *end* with one.
So, with my data and that code from the "frame.xml" file (which you can hopefully see in my attached file) I produced a chunk of code that had the structure of the "glossary_data" node and my content.
Hint: there are applications that allow you to search for and modify specific tags to make this easy... you can even remove tags and leave their contents, if necessary.
After that I BACKED UP THE ORIGINAL "frame.xml" file, just in case, and then replaced the original glossary_data node with the new one I created with my actual data, and presto, new, working glossary full of terms I wanted but did not have to paste one by one.
Sadly I could not bring that back into the file, but adding a bit of XML to a published doc is easier than copying and pasting a bunch of terms over and over...
Anyway, hope this helps someone ;)
Thanks Seth for sharing here.
You can edit glossary directly in Storyline source file. It is not good way, but sometimes not good way is the best possible way.
You must change the extension of source file from ".story" to ".zip" and unpack the file to some folder. There you will see (in subfolder "story") file "playerProps.xml". Glossary is there, almost on the end. Edit what you need, zip, change file extension to ".story" - and that's all.
Hi Vadim!
This thread is a bit dated, but I do appreciate you popping in to share your solution with the community.
Even if it does not assist the users here, it could help someone searching in the future for sure.
This discussion is closed. You can start a new discussion or contact Articulate Support.