Export as SCORM package
Last updated
Was this helpful?
Last updated
Was this helpful?
All GMetri experiences can be exported as web SCORM packages and imported into any LMS. We support SCORM 1.2 and SCORM 2004 package versions.
After you are done creating your experience, follow the steps below to generate a SCORM package for your content.
Make the deployment live.
Select SCORM from the Authentication dropdown as shown below
Navigate to Others section in the Sharing options
Select either SCORM 1.2 or SCORM 2004 versions for export and click Download SCORM button to start downloading the file
This file can then be imported into any LMS having SCORM support
To support communication between LMS and a GMetri experience, we allow defining certain rules that can be triggered conditionally.
The following is an exhaustive list of SCORM actions that we support.
Set SCORM min score: This can is used to notify the LMS about the minimum score possible to get in the experience. This should usually be fired right at the beginning of the experience.
Set SCORM max score: This can is used to notify the LMS about the minimum score possible to get in the experience. This should usually be fired right at the beginning of the experience.
Set SCORM score: This can be used to notify the LMS about the current score of the user. Usually, LMSes show scoring after completion of the course but make sure to keep calling this action as and when the score inside the experience changes.
Set SCORM status as passed: This can be used to notify the LMS when the user has met the criteria of successfully passing the module.
Set SCORM status as failed: This can be used to notify the LMS when the user has failed the module.
Set SCORM status as complete: This can be used to notify the LMS when the module is complete. Call this action when the full experience has been completed by the user. This enables the LMS to track and show user attempts and show the final calculated score.
Set SCORM min score and Set SCORM max score actions should be added right at the beginning of the experience. Add rules to set scorm min score = 0 and set scorm max score = 100.
Set SCORM score should be called at the end of the experience when you want to relay the score value to the LMS.
Set SCORM passed/failed/complete should be called at the end of the experience when you want to relay this information to the LMS. Please note that certain LMS's don't track scores unless a rule for set SCORM complete is fired.
To test that information is correctly shared between GMetri and LMS, we suggest you to first import the test SCORM package which covers all the scenarios specified in the previous sections.
If the integration works perfectly, after importing the test package, you should be able to see the user's unique ID, be able to score the user and mark the course as completed right within the experience.
There are 2 types of data that needs to be shared between the LMS and the GMetri system. We categorize these as inbound and outbound data.
Inbound - This is the data that is required for day-to-day functioning of GMetri experiences
Learner ID - User's learner ID as stored in the LMS [cmi.core.student_id (SCORM 1.2) / cmi.learner_id (SCORM 2004 V3)]
Progress - User's progress through the course as stored in the LMS [cmi.progress_measure (SCORM 2004 V3)]
Suspend Data - Additional information stored in the LMS for course to run [cmi.suspend_data (SCORM 2004 V3 & SCORM 1.2)]
Score - Score stored in the LMS [cmi.core.score.raw (SCORM 1.2) / cmi.score.raw (SCORM 2004 V3) ]
Outbound - This is the data sent out by GMetri system that should be stored inside the LMS. This includes functions like scoring, course completion etc
Progress - User's progress through the course calclated in the GMetri system. (SCORM 2004 V3)]
Suspend Data - Additional information stored in the LMS for course to run [cmi.suspend_data (SCORM 2004 V3 & SCORM 1.2)]
Score - Score calculated in the GMetri system [cmi.core.score.raw (SCORM 1.2) / cmi.score.raw (SCORM 2004 V3) ]
