I need to update a module created in Storyline by someone else (who is no longer working with us) and I am unable to find the .story file from the exported folders when they published it and uploaded on the LMS. I have attached the image of the folders that were saves in our shared folder.
The .story file isn't included in the published output.
If the person didn't give a copy of the .story file to someone or backup the .story file in a shared location (e.g., in SharePoint, Teams), you're out of luck. Well, unless maybe you can get your IT folks to search the laptop and/or OneDrive (or other storage space)...
You should be able to scrounge some of the images from within the published folders. But, otherwise, you'll have to re-create the course from scratch if you can't locate the .story file.
Thank you Judy, I was afraid of that. So how do we ensure we get a .story file when we publish and opt for the zip file . is there an additional step we need to do to ensure we get that .storey file? I dont use Storyline that often so apologies if this is a silly question.
Sorry to hear you did not get editable assets from your developer. Reverse engineering a published SCORM package into an authored storyline package is not possible.
You need to require that your contract developer (if that is the case) archive their source files in your system daily and with delivery of the LMS package.
"Saving as" is non-contextual here as you need a source storyline or blank storyline file to Save or Save as a .story file. It sounds like you are still trying to reverse engineer a minified SCORM package back into author-able content and that is simply not possible.
The good news is that you don't necessarily have to start from scratch as graphics and audio will be saved within your SCORM package, and if you're interested someone from the community can show you how to pull those assets to make a rebuild quicker. Though not quite painless.
Here's another way to explain how the process works. Using Storyline to create a SCORM package is similar to using MS Word to create a PDF.
Both MS Word (part of MS Office) and Storyline 360 (part of Articulate 360) require you to have a license to use that software.
An MS Word .docx file and a Storyline .story file are sourcefiles. They contain the necessary elements for the project, which are entered and edited within those files.
In MS Word, you can save the source file as a PDF. That creates a separate file that can be viewed using any PDF reader. However, that PDF isn't editable in the same way that the source file is. That's like Storyline publishing a SCORM package. A published course can be viewed in any browser. But to edit and republish the course, you need the source file.
In MS Word and Storyline, you need to save the source file if you want to maintain the content. You can also use "Save As" to create a copy (which is always a good idea when you're going to work on a new version).
As Patrick said, it should be part of the process to ensure that all source files are properly stored where the company has access to them. There's no way for Articulate staff to retrieve a .story file for you.
Nice addendum Judy! I thought I could climb on your shoulders and improve on your analogy by saying that Word can PRINT a document on paper that can no longer be edited in Word, the same way Storyline "prints" a published package.
8 Replies
The .story file isn't included in the published output.
If the person didn't give a copy of the .story file to someone or backup the .story file in a shared location (e.g., in SharePoint, Teams), you're out of luck. Well, unless maybe you can get your IT folks to search the laptop and/or OneDrive (or other storage space)...
You should be able to scrounge some of the images from within the published folders. But, otherwise, you'll have to re-create the course from scratch if you can't locate the .story file.
Thank you Judy, I was afraid of that. So how do we ensure we get a .story file when we publish and opt for the zip file . is there an additional step we need to do to ensure we get that .storey file? I dont use Storyline that often so apologies if this is a silly question.
Thanks
Sorry just remembered , you need to do a "save as" to save a .story file . Is that correct?
Is there a way that the Articulate tech team can help retrieve this >
Sorry to hear you did not get editable assets from your developer. Reverse engineering a published SCORM package into an authored storyline package is not possible.
You need to require that your contract developer (if that is the case) archive their source files in your system daily and with delivery of the LMS package.
"Saving as" is non-contextual here as you need a source storyline or blank storyline file to Save or Save as a .story file. It sounds like you are still trying to reverse engineer a minified SCORM package back into author-able content and that is simply not possible.
The good news is that you don't necessarily have to start from scratch as graphics and audio will be saved within your SCORM package, and if you're interested someone from the community can show you how to pull those assets to make a rebuild quicker. Though not quite painless.
Here's another way to explain how the process works. Using Storyline to create a SCORM package is similar to using MS Word to create a PDF.
As Patrick said, it should be part of the process to ensure that all source files are properly stored where the company has access to them. There's no way for Articulate staff to retrieve a .story file for you.
Thank yoiu both ! I have been able to get the audi and graphics so now I am working on rebuilding this. Thank you so much for your help.
Nice addendum Judy! I thought I could climb on your shoulders and improve on your analogy by saying that Word can PRINT a document on paper that can no longer be edited in Word, the same way Storyline "prints" a published package.