SCORM content

What is SCORM?

SCORM is a standard that allows interactive learning content created outside Shapeshift to be launched inside a Course and communicate learner activity back to the platform.

SCORM content is normally supplied as a ZIP package containing the learning experience and an imsmanifest.xml  file describing how the content should be launched.

A SCORM package controls the learning experience itself. Shapeshift provides the environment in which it runs and records information the package reports back, such as completion, progress and session data.

Supported SCORM versions

Shapeshift supports:

  • SCORM 2004, which is the preferred format for new content
  • SCORM 1.2, with some limitations depending on the information the package needs to report

SCORM 2004 is recommended where possible because it provides clearer separation between completion and pass/fail status and supports more comprehensive session data.

If you are migrating existing SCORM content from another learning platform, we recommend testing representative packages before importing a large content library.

Adding SCORM content

SCORM content is uploaded to the CMS as a ZIP package.

The package must contain a valid imsmanifest.xml  file, which Shapeshift uses to identify and launch the learning content.

Once processed, the SCORM item can be added to a Course curriculum in the same way as other module types.

Package compatibility

Not all SCORM packages are structured in the same way.

Shapeshift currently works best with single-SCO packages, where the package has one primary piece of learning content to launch.

Packages containing multiple SCOs or relying on complex SCORM sequencing may require additional testing or customization before they can be used.

If you are moving SCORM content from another LMS, providing a representative package to Plume before migration allows its behavior to be validated.

Completion

The SCORM package tells Shapeshift when its learning activity has been completed.

For SCORM 2004 content, this is normally reported using the package's completion status. SCORM 1.2 packages use their equivalent lesson status.

Once the package reports completion, the learner can progress from the SCORM module and Shapeshift records the module as completed against their Course enrollment.

The rules determining when a package reports completion are controlled by the SCORM content itself.

Scores and pass/fail

SCORM packages can also report assessment results.

Where supported by the package and platform version, Shapeshift can record:

  • A score
  • Whether the learner passed or failed

Completion and pass/fail are separate concepts. A SCORM activity may therefore be completed even where the learner did not achieve its required score, depending on how the package has been authored.

SCORM 2004 is recommended where score and pass/fail reporting are important.

Resuming SCORM content

Shapeshift stores SCORM session data reported by the package and restores it when the learner returns.

Compatible packages can use this information to resume the learner's previous session, for example by returning them to the page or point they previously reached.

The exact resume behavior depends on how the SCORM package has been authored.

Migrating SCORM from another LMS

Existing SCORM content can often be reused in Shapeshift, but compatibility should be verified before a large migration.

We recommend testing at least one representative package from each authoring tool or content source and checking:

  • The package launches successfully
  • Completion is reported correctly
  • The learner can progress after completion
  • Scores and pass/fail are recorded where required
  • The learner's position is restored correctly when returning to an incomplete activity

Where possible, use SCORM 2004 single-SCO packages for the most predictable integration with Shapeshift.