SCORM Support and Recommendations

Support

Thriving Springs is compatible with SCORM versions 1.2 and 2004 3rd Edition. 

While the core configurations are supported in Thriving Springs, every platform has a different set of support for the configurations. SCORM checkers (like SCORM Cloud) implement parts of the SCORM standard that could either be not implemented or implemented differently in Thriving Springs.

The SCORM file name and all file name inside the package should not contain any special characters.

When the user completes the SCORM topic, make sure that the package emits complete status. If the SCORM topic contains lesson quiz, make sure to emit Completion status with pass and Incomplete with failed status. 

SCORM files can be added with other type of content like videos and assessment in a course. 

Recommendations

SCORM 1.2 was stablished in 2001 and is an aging standard. SCORM 2004 is more robust and is recommended over 1.2 standard. 

SCORM packages that include assessments with pass/fail criteria are expected to emit both the score and the pass/fail status at every attempt. 

Following are the common pitfalls across different SCORM packages that impacts how this data is communicated.

1. Incomplete Emission of Status Information

• Pass Scenario: Some SCORM assessments emit only a "passed" status along with the score.
• Fail Scenario: When a user fails an assessment, no failure status is emitted, leading to ambiguity about the outcome.
• Recommendation: At the end of each SCORM assessment, a lesson status (pass/fail) should be emitted for the LMS to capture the learner’s attempt.

2. Lack of Segregation Between Completion and Success

• There is a need to separate the SCORM completion (i.e., the fact that the user attempted the assessment) from the SCORM lesson success (i.e., whether the attempt was passed or failed).
• This separation is critical because in some user flows, even a failed attempt should mark the SCORM as "completed" while still indicating that the attempt was unsuccessful. Similarly, it may be required to mark an attempt as "incomplete" if the user fails, based on the desired workflow.
• Recommendation: Along with the lesson status (pass/fail), a completion status (complete/incomplete) must be emitted in order to segregate lesson status and completion status.

3. Inconsistent Score Emission Patterns

• Early Score Emission: Some SCORM packages emit a score after the first question irrespective of whether the answer is correct or not.
• Subsequent Questions: For later questions, the score is only emitted when the answer is correct.
• Resulting Problem: The early emission of a score incorrectly triggers the system to mark the attempt as "failed" and "completed," even though the assessment is still in progress.
• Recommendation: Always share the score after the last question. 

Recommendation with Tools

• Utilize Articulate 360's In-built Quiz and Result Slide
  • Score Sharing: Leverage the in-built quiz functionalities to consistently share the score for every attempt.
  • Completion Tracking: Use the result slide to accurately track the  success status of the assessment.
• Implement a Completion Trigger
  • Purpose: Add a trigger that explicitly indicates the completion of the SCORM package.
  • Benefits: Ensures that the SCORM package is marked as "completed" .