Today we released an exciting new feature for Storyline 360: glossary import and export. Now it’s a cinch to add a glossary to your Storyline 360 projects.
Build your glossary in a spreadsheet, save it as a .csv file, and import it directly to your course. After you import, you can easily make edits right in your project. Simply click a term or definition and start typing.
You can even export your glossary to a .csv file to reuse it in another project.
I'd never added a glossary directly before because it was such a chore. Having links to external documents was okay but always seemed a bit of a bolt on. Just tried this function out and really impressed with the simplicity.
Re: Jerson's question - I didn't try it it but the intro information does show a couple of options when importing a new file to an existing glossary where you can just import additions or delete the original and just import the new file.
Hi, I am thinking on using the functionality to create a course only with the glossary. Is there any template created that allows the learner to jump from one letter to another so it become a little bit more interactive?
Hi, Jack! Great question about CSV requirements. If you're using a spreadsheet app to create your CSV file, you just need to add terms to the first column and their definitions to the second column. You can learn more about importing CSV glossaries in this user guide.
Hi Jerson! Short answer: you can choose to overwrite - or add. I tested it - seriously slick... it gives you a choice. I created a single row item in a new CSV called "Fruit" (see attached for those curious about CSV formatting) and attempted to upload it to an existing Articulate 360 glossary of 28 terms. It popped up a window and politely asked me if I wished to replace what I had, or add it to existing. Works perfectly.
I just tried it, and first issue I run into was that special letters like ß, ö, ü, etc are not displayed correct after the import from excel. It looks like it has something to do with the csv file format as those characters are not correctly displayed once saved as csv.
I like it! I imported a pretty robust glossary of 22 pages of definitions. Since there are so many terms and definitions I will look forward to the ability to allow my learners to search versus being forced to scroll-and-scroll. And as others have mentioned before, the ability to link to click a link that opens the glossary to the same term and definition. Great progress on this.
Hi Margit, thanks for reaching out! Excel supports multiple CSV formats, and some of them could cause problems for accented characters. If you're using Excel for Windows, choose one of these file formats when you save: CSV UTF-8 (Comma delimited) or CSV (Comma delimited). If you're using Excel for Mac, choose the Windows Comma Separated (csv) format. Then import your CSV file into Storyline again. Your accented characters should be preserved. Other CSV formats might change your accented characters to symbols. Let me know if that helps!
That is a good poin David. I tried your suggestion with the file I included. Storyline says sucessfully imported but no terms are there after the import.
Hello Wendy, It is scribbling, with me it does not work with csv file either, wahrscheinlch it is to do with csv format. If I want to save the file as a CSV (separator-separated), I always get the message: Some features in the workbook may be lost if you save them as CSV (separator-separated). Do you want to use the format anyway? If so, then I do not see in SL360 what I have imported. Thanks in advance!
64 Replies
Hi Mike,
This is a great feature that will allow us to save a lot of time. I am looking forward to test it!
Thanks!
Raquel
Great! I've always wanted to be able to do this!
Thank you!!
This will be a great addition, looking forward to testing it out! :)
This is awesome - so simple and such a time saver. Thank you!!
This is a great addition. I have a question though, if you reimport the CSV file, will it overwrite the existing information or add to it?
I'd never added a glossary directly before because it was such a chore. Having links to external documents was okay but always seemed a bit of a bolt on. Just tried this function out and really impressed with the simplicity.
Re: Jerson's question - I didn't try it it but the intro information does show a couple of options when importing a new file to an existing glossary where you can just import additions or delete the original and just import the new file.
If you reimport it should ask what you want to do.
What are the requirements for CSV Datei?
Will this feature be made available to Storyline 3 users?
Hi, I am thinking on using the functionality to create a course only with the glossary. Is there any template created that allows the learner to jump from one letter to another so it become a little bit more interactive?
Hi, Raquel - thanks for reaching out. We have lots of standalone glossary downloads in ELH you can take for a spin. Check them out: https://community.articulate.com/search?only_type=resource&page=1&q=Glossary&utf8=%E2%9C%93&search_sort=desc
Hi, Tom. This feature is exclusive to Storyline 360.
Hi, Jack! Great question about CSV requirements. If you're using a spreadsheet app to create your CSV file, you just need to add terms to the first column and their definitions to the second column. You can learn more about importing CSV glossaries in this user guide.
Thanks, David!
That's exactly what I want to know.
Thank you Borden! These resources are so useful!
Regards,
Raquel
Hi Brandon, I appreciate this is exclusive to SL360, do you have any plans to roll it out to SL3 users?
Hi Jerson!
Short answer: you can choose to overwrite - or add. I tested it - seriously slick... it gives you a choice. I created a single row item in a new CSV called "Fruit" (see attached for those curious about CSV formatting) and attempted to upload it to an existing Articulate 360 glossary of 28 terms. It popped up a window and politely asked me if I wished to replace what I had, or add it to existing. Works perfectly.
I just tried it, and first issue I run into was that special letters like ß, ö, ü, etc are not displayed correct after the import from excel. It looks like it has something to do with the csv file format as those characters are not correctly displayed once saved as csv.
I like it! I imported a pretty robust glossary of 22 pages of definitions. Since there are so many terms and definitions I will look forward to the ability to allow my learners to search versus being forced to scroll-and-scroll. And as others have mentioned before, the ability to link to click a link that opens the glossary to the same term and definition. Great progress on this.
Hi Margit, thanks for reaching out! Excel supports multiple CSV formats, and some of them could cause problems for accented characters. If you're using Excel for Windows, choose one of these file formats when you save: CSV UTF-8 (Comma delimited) or CSV (Comma delimited). If you're using Excel for Mac, choose the Windows Comma Separated (csv) format. Then import your CSV file into Storyline again. Your accented characters should be preserved. Other CSV formats might change your accented characters to symbols. Let me know if that helps!
+1 for "organising" the glossar with links, search etc.
Endless scrolling is not a user friendly method to find a definition.
I would also like to have the ability to link to a specific glossary term on a slide. So a user can access definitions easy.
That is a good poin David. I tried your suggestion with the file I included. Storyline says sucessfully imported but no terms are there after the import.
Do you know why this happens?
Hi Margit
I got your glossary to import by formatting the .csv file into columns instead of the ; between term and definition
Hello Wendy,
It is scribbling, with me it does not work with csv file either, wahrscheinlch it is to do with csv format.
If I want to save the file as a CSV (separator-separated), I always get the message: Some features in the workbook may be lost if you save them as CSV (separator-separated). Do you want to use the format anyway?
If so, then I do not see in SL360 what I have imported.
Thanks in advance!
Hi Jack
did you follow this KB article
For Margit's file I removed the ; she had and placed the Terms in columns and the Definitions in another and it imported as expected.
This discussion is closed. You can start a new discussion or contact Articulate Support.