I will have 10 separate Storyline 360 projects that I would like to link from a single Storyline 360 project--an index. Seems like this would be a common need? Would like to know the current state of the technology. Thanks,
How are you envisioning presenting this? If you are using an LMS, it can handle that sort of thing easier than SL. Otherwise, SL projects are HTML files, and you can easily create a web page as an index to access all of them. In my mind either of those methods has to be far easier than SL.
Multi-SCORM Packager applications have been around for a long time, but typically an LMS is used to present and track multiple SCORM objects as part of a course, curriculum or learning path.
5 Replies
How are you envisioning presenting this? If you are using an LMS, it can handle that sort of thing easier than SL. Otherwise, SL projects are HTML files, and you can easily create a web page as an index to access all of them. In my mind either of those methods has to be far easier than SL.
Multi-SCORM Packager applications have been around for a long time, but typically an LMS is used to present and track multiple SCORM objects as part of a course, curriculum or learning path.
Thank you.
We will eventually bundle these and offer them through an LMS.
I guess I will figure out how to link between them when I get there…
Robert
Very helpful—thank you.
Robert
ADobe offers the Multi-SCORM Packager as part of Adobe Captivate 2019; it can create Multi-SCOs for both SCORM 1.2 and SCORM 2004 content.
Ryan Donnelly of Rustici Software (stewards of the SCORM standard) posted Combining Multiple SCOs Into One SCORM Course, which describes how to manually bundle multiple SCORM content packages into a single SCORM course.