Setting up SCORM packages for successful completion reporting - should each SCORM be generated from its own .story project?

Mar 11, 2022

Hello E-Learning community - I'm looking for some 'best practice' advice around how to get completion reports for SCORM packages in our LMS to work for us. Currently, the project I'm working on is in one big .story project file, and I export the different scenes as distinct SCORM package 'modules'. When setting up reporting, the completion criterion is only able to see the number of slides in the entire project, not the number of slides in the scene that I'm about to export as a SCORM. I'm wondering if this is the reason why all SCORM packages are reported as 'incomplete', as it is not possible to view, say 90% of the 150 slides in a project when the SCORM (one scene) only has 25. Is it better, therefore, to have a separate .story project file for each SCORM package? 

2 Replies
Judy Nollet

I always use a separate .story file for each SCORM package. 

Since you already have the content in one big file, I suggest you save a copy for each scene. Then, in each one, delete what's not needed (that is, delete everything except the desired scene and any slides used in all packages). And be sure to make any other adjustments, such as revising the title.