SCORM (Sharable Content Object Reference Model) is a set of technical standards for E-learning platforms. It provides the communication method and data models that allow E-learning content and platforms to work together. SCORM also defines how to package content into a transferable ZIP file, called a “Package Interchange Format”, to be uploaded in the platform.
Docebo is compatible with SCORM versions 1.2 and 2004 3rd Edition. Please note the following limitations for each version:
- SCORM 1.2. 4,096 characters (Articulate’s default is 256 characters) for the suspend_data CMI element.
- SCORM 2004 3rd Edition. 64,000 characters for the suspend_data CMI element. Sequencing is not supported by this version.
NOTE: This article outlines best practices and how to manage SCORM content within the context of Docebo, but should not be used as an expert guide in SCORM content at large. Learn more about creating SCORM packages with Articulate and with Adobe Captivate.
Also, note that every platform has a standard set of core components that are used for SCORM objects. Some systems or SCORM compliance checkers (like SCORM Cloud) implement parts of the SCORM standard that could either be not implemented or implemented differently in Docebo.
Preparing a SCORM Package
This section provides you with some rules and suggestions on how to prepare a SCORM package, reducing the risk of problems during the upload and the playback. SCORM packages must be compressed zip files and must include everything you need to deliver the course.
– The platform does not accept SCORM packages including files with the following extensions: htaccess, phps, php5, php4, ph3, php, cgi, sh, shtml, asp, aspx, jsp, py, rb, pl. Remember to put the manifest file (imsmanifest.xml) in the folder root level before zipping it.
– The maximum file size varies according to your plan‘s features (it must not exceed 350 MB or 800 MB).
– The platform only accepts SCORM packages using HTTPS. If you upload a package referencing an HTTP address, the browser will prevent users from playing the content in the platform. If this happens, check the browser console for error messages, as the Docebo interface does not provide an error message in these cases.
– When uploading your SCORM package, make sure that, when users complete it, the SCORM package does not update the platform with the completion status multiple times.
Uploading SCORM Content into a Course
To upload SCORM content into a course, access the Admin Menu by scrolling your mouse over the gear icon in the top right corner of the platform. Then, in the E-Learning section, select the Course Management item. On the main Course Management page, select the course for which you would like to upload your SCORM content by clicking and its description, then move to the Training Material tab.
Please Note: SCORM content can be uploaded as training material only into e-learning courses.
Select the Add Training Material button, then select SCORM from the dropdown menu. On the following page, press the Upload File button to choose the SCORM file from your device.
When uploading SCORM 2004 3rd Edition packages containing simple and linear sequencing into a course, you can flag the option to convert the package sequencing into platform prerequisites, once the upload reaches 100%. This option is also available for SCORM packages without embedded sequencing and does not manage SCORM packages including complex sequencing. You can change these settings at any time when managing the training material’s settings and prerequisites. For more information about SCORM sequencing, refer to this SCORM.com article.
Select the view mode for each device on which the course will be played in the View Mode area. Check the description under the available view modes type for further information on the available options. Define whether your SCORM content is playable on the Mobile App. Please note that if your SCORM package includes Iframes, your learners may experience problems while playing it if you set the View Mode to Inline or Play in Lightbox. We suggest you try playing the content in a new window or check your browser console before delivering the content to learners.
If your SCORM package includes tests, configure the Score Calculation method by selecting whether the course score will be based on the last test taken by the user, or calculated as the sum or the average of the scores coming from all the tests in the package. If your SCORM includes a single test, then select the first option. Please note that these settings can no longer be edited after the SCORM content is completed for the first time. Remember that for SCORM 2004 3rd Edition packages, scores are reported by the cmi.score.raw and not by the cmi.score.scaled.
Move now to the Additional Info tab. Select or upload a thumbnail for the training material, then give a short description of the content for your learners. In this tab, you can also add tags to your training material to improve its searchability in your platform’s global search. Some tags may be automatically generated based on the content of your asset, as understood by your platform using artificial intelligence; note that this only works for English, Spanish, French, German, Italian and Portuguese content and it may require a few minutes: you’ll receive a notification once the artificial intelligence engine has tagged your object. You can edit or remove tags at any time, with a limit of 15 tags per training material.
When finished, press Save Changes. If the file format is correct, the SCORM content will be uploaded as new course training material, and a message will be displayed on the top left of the page. The SCORM package content is now course content and is ready to be played.
Uploading SCORM Content into the Central Repository
Uploading a SCORM package to the Central Repository allows you to push its content into multiple courses, so learners only have to view the content one time in any of the courses in which the content is placed. When content from Central Repository is pushed to one or more courses, the package is then share-tracked between all of the courses. This means that the learner can avoid playing the content several times in several courses.
Please note that when uploading SCORM packages including tests in the Central Repository, the Score Calculation option selected when the first version of the package is uploaded cannot be changed when uploading new versions of the same SCORM package.
Updating SCORM Content
Whenever you need to update your SCORM content by replacing it with a new version of the same package, remember that the new package must have the same SCORM version as the previous one. For example, if the original package you uploaded used SCORM 1.2 version, you cannot edit the package by uploading a SCORM 2004 3rd edition version.
If you are updating a SCORM content directly in the Central Repository, the new version of the package will be immediately published and playable in the courses in which the content is placed. If you are uploading the learning content directly in a course, it may take from 30 minutes up to an hour before the updated version is playable in the course. Therefore, we strongly suggest you upload and edit SCORM packages in the Central Repository.
Please Note: When updating SCORM content, by changing the structure of the SCORM, where users have already interacted with the content, users whose status is ‘In Progress’ will lose their progress in the training material. These users will have to start the content from the beginning.
Playing SCORM Content on Mobile Devices
If you are planning to play your SCORM content on mobile devices with the Go.Learn App, make sure that the package is created and exported with the latest version of the authoring tool you’re using in order avoid display errors or glitches related to unpatched versions of the tool. In order to play smoothly in offline mode, packages must be completely encapsulated, meaning that they must not have any reference to external websites.
Remember to test your content both on IOS and on Android, and using different versions of the Operating Systems, to make sure that your content is properly displayed for all your learners. Please note that if your SCORM object includes Flash or Silverlight content, it may not be playable on mobile devices: we strongly suggest replacing SCORM objects including Flash and Silverlight content with HTML5 responsive content.
Please note that when SCORM content is not played in full-screen mode in your desktop platform accessed with the Safari browser, on iPad iOS 13.4.1 and iOS 13.5.1, the content tracking should not be kept properly.
Tracking the Progress of SCORM Content
The platform identifies SCORM content as completed when learners press the Close button (also named Exit or Submit). Failing to press this button may result in the learning progress not being sent from the SCORM package to the platform and in the SCORM content not being marked as completed. Remember to tell your learners to press the button before closing the window or tab, or they will lose their progress. If you are using a custom domain, make sure that your custom domain is fully secured using HTTPS.
If you unenroll a user from a course after he or she has completed the SCORM content in the course, the tracking for the user is not deleted. If you re-enroll the user into the course, you will be able to view the tracking again.
If you delete a SCORM package from the platform, the tracking of the content is also deleted and no longer retrievable.
In order for the system to keep track of the user progress for a SCORM training material, make sure that cookies aren’t blocked, and that the third-party cookies aren’t blocked in the user browser settings (for Google Chrome: Settings > Site settings > Cookies and site data > Block third-party cookies). If the cookies are blocked, even if the user takes the course, it will be shown as not started.
If you have uploaded multiple SCORM training materials in a single course, remember that the tracking is managed independently for every single training material. The tracking is not cumulated by training material type.