SCORM Packaging
Some thoughts and experiences in SCORM Packaging.
First of all, two parts in a SCORM packaged learning objects, “Content Aggregation” and “Run time environment”.
There are four levels in packaging a learning object in SCORM conformant:
Level 1: Basic
Simply use the “imsmanifest.xml” to link up all the assets for the learning object. One may easily accomplish this by using tools like LRN (Microsoft).
Level 2: Intermediate
Define the object as SCO, add extra metadata in the description. Provide the “imsmanifest.xml” to link the assets in the object. One may accomplish this by using LRN and some metadata editing tool. Or one can simply write everything in Notepad if you understand XML well.
Level 3: Advanced
Define the object as SCO, every active components in the object should be paired with two javascript: “APIWrapper.js” and “SCOFunctions.js” and call the “LMSInitialize()” and “LMSFinish()” to acknowledge the LMS for basic tracking purposes. One can use Flash SCORM extension to do the wrapping and program the trigger as a FS command call in the flash movie. You may reference my hand out for the pre-con workshop in the NMC conference.
Level 4: Professional
Define the object SCO, code all the necessary javascripts and having the object calling customized functions to communicate with the LMS such as: “LMSInitialize()”, “LMSFinish()”, “LMSGetValue()”, “LMSSetValue()”, “LMSCommit()”, “LMSGetLastError()”, “LMSGetErrorString()” and “LMSGetDiagnostic()”. During the presentation of the learning object, essential data such as user information, object tracking information can be sent back and forth between the learning object and the LMS.