SCO packaging


In order to be SCORM compliant, an LO needs to contain some code (always in Javascript) that allows it to communicate with the LMS according to the SCORM model.

The following step is to make our LO uploadable and usable on any LMS.

This is made possible through the procedure called "packaging" which produces a single zipped file containing both the files of the LO and other specific files among which is the Manifest. This is a file containing metadata and information on the organisation of the package that are useful to the LMS.

The SCORM model identifies three types of content: asset, SCO and content aggregation. What is packaged is generally content aggregation, that is, a set of SCOs and Assets.

But is also possible to create a package from a single SCO, as we are going to do in this element.