Once you have created your learning module or assessment, you can publish Live Content via three standard distribution models:
•HTML – As a single, self-contained .html page that may be added to a website or intranet page or run from a network share or even emailed to an end-user.
•AICC – Imported into an LMS via the industry recognized AICC mechanism.
•SCORM 1.2 – Import into an LMS via the industry recognized SCORM mechanism.
Important! Ensure you have a firm-wide installation of the Live Content Launcher MSI. Publish all new content to Use new MSI Launcher - Turned On. Once selected, this will be left on as default and Live Content can be published in the normal way as HTML, AICC or SCORM. Each will use the Launcher if it is installed.
|
If you have a Learning Management System (LMS), we recommend you use the Publish as AICC option. Live Content is SCORM 1.2 compatible, so if your LMS doesn’t support AICC, that’s no problem. If you don’t have an LMS, the Publish as HTML option will allow you to create a standard, self-launching HTML page that contains all the necessary information to allow end-users to run the Live Content. Once published, you may manage the .html output file in the same way you would any web page, such as placing a link to it on your company website or intranet page or simply placing it in an accessible location for learners to open. You may also email the published .html page to users to open. |
For conventional, in-browser eLearning, which we call simulation at Intellek (wrapped using Adobe Captivate, Articulate Storyline, Camtasia, etc.), SCORM is often the most effective protocol for tracking usage back to a Learning Management System (LMS). This is because this type of eLearning is delivered in-browser and communication for SCORM tracking back to the LMS takes place via a JavaScript API located in the browser window in which the content is launched and played.
Live Content Studio delivers a completely different form of eLearning that takes place live in-application, across multiple applications, and does not remain in the browser. In order for SCORM tracking to work for Live Content, the browser window must remain open for the content to be tracked back to an LMS via the JavaScript API. While we know that you ask end-users to keep the browser window open, that instruction isn’t always followed, which can lead to frustration for the end-user and the trainer when tracking ceases after the window is closed. Even when the browser window is kept open for the duration of a module, the developers of the major browsers are always tightening security settings (rightly so), which makes it ever-harder for Live Content to locate the JavaScript API in order to ensure tracking of Live Content in the LMS. |
|
