basskins.blogg.se

Your entire published Storyline course needs to be stored somewhere, be it on the LMS or on web servers outside the LMS (if the LMS supports that).

Then story.html gets launched for viewing the content. With that, at launch, some things are set up and then the AICC or SCORM or Tin Can code gets loaded that's lets the content "talk to" and "report back" to the LMS. Such Storyline courses use index_lms.html as their launch file. When published to those standards the course determines completion and passes it on to the LMS, or works with the LMS to determine completion, be it by viewing so much content or by passing a final quiz. The learning standard defines how content and the LMS communicate together. I'm more old school-a completion should be earned.įor that, you need to publish Storyline courses to LMS and a "learning standard"-either AICC, SCORM, or Tin Can (if your LMS supports that last new learning standard). Personally, I was never a big fan of using that (i.e., launch a course and you get a completion). In Saba, the content could be anywhere on a web server (or you could load it into Saba)-you just enter the launch URL pointing to story.html in Saba. For this with Storyline, you'd want to use the story.html as your launch file. Saba has a similar feature it sounds-where you can launch "regular" HTML content and get passing credit just by launching the training. Don't know how you load or refer to content into the Oracle LMS. Most of my experience is with Saba and a couple of other LMS's.