You are here

SCORM / AICC

SCORM stands for Sharable Content Object Reference Model.  It is a standardized set of calls that allow lessons and courses (Sharable Content Objects, or SCOs) to communicate with a Learning Management System (LMS), such as Moodle or BlackBoard.

SmartBuilder has a number of preconfigured SCORM calls that can be sent on appropriate triggers, as well as the ability to send any other recognized SCORM call.

The SCORM / AICC is an object that only exists in action menus, and not on the Authoring Stage at all.

scorm aicc

There are two versions of SCORM, SCORM v1.2 and SCORM 2004.  It is not the place of this help documentation to question why a collection of standards does not choose to standardize their own version numbering system, but SCORM 2004 is more recent and has a number of improvements and additional methods available to it than v1.2 does.  However, v1.2 is more widely used.

Upon downloading a lesson, one must specify if they want their content to be SCORM compliant, along with the version.  SmartBuilder will automatically convert its SCORM calls to the appropriate version, if those calls are available in that version (for example, there is no v1.2 equivalent of setInteractionResponse).

SmartBuilder is not an LMS, and as such SCORM calls will not work when previewing or viewing content from SmartBuilder.  The best way to test a lesson's SCORM calling functionality is to download it and upload it into your LMS.  If you are troubleshooting, and want detailed logs of what is being transmitted to your LMS, www.scorm.com's TestTrack is an extremely useful (and free) tool for testing your SCORM compliant content.  You must still download your content from SmartBuilder and then upload it into TestTrack.

Question Sets can automatically submit their raw score to the LMS without having to set up an action.  If you wish to get or set a SCORM call that is not prebuilt, use the LMSSetValue or LMSGetValue to manually enter the SCORM call you wish to send.

You can use the LMS to store information such as a bookmark, user notes, or the status of a menu object, all of which can be retrieved later.  For bookmarking, please see the Template > Master Page: Resources folder, and refer to the example in the above collapsed section on how to store data.