Skillport only supports single-SCO SCORM 2004 packages (where the SCORM PIF is only allowed to define a single SCO); otherwise, the SCROM 2004 package cannot be imported into Skillport. The result of this limitation is that the "sequencing and navigation" capabilities of SCORM 2004 are not directly supported (see Multi-SCO Support for more information).
Single-SCO is when the Manifest declares only a single organization node, and that node declares only a single child item node. This item node must have an identifierref attribute that points to a resource node that specifies adlcp:scormtype="sco" or adlcp:scormtype="asset".
Content labeled as adlcp:scormtype=”sco” is expected to behave like a normal SCORM 2004 “SCO”. It must call SCORM API JavaScript methods Initialize and Terminate. It may also optionally set parameter values, and call the Commit API method before calling the Terminate method.
Content labeled as adlcp:scormtype=”asset” is expected to have no calls to the SCORM API. It is a pure asset that can be launched as if it were a SCO. When the SPCSF file is created for a scormtype="asset" item, the launch mechanism includes a specialized wrapper that communicates with Skillport - therefore, the content can be purely passive. The specialized wrapper makes SCORM 2004 API calls to Initialize, SetValue and Terminate. The wrapper sets cmi.completion_status to completed and sets cmi.exit_status to normal, thus tracking the content's completion.
Initialize and Finalize calls - the only thing recorded is a successful launch.
© 2017 Skillsoft Ireland Limited