DISCLAIMER: Some content in this article outlines how to use functionalities with the new Course Management. Check out this article for further info.
SCORM (Sharable Content Object Reference Model) is a set of technical standards for Elearning platforms. It provides the communication method and data models that allow Elearning content and LMSs 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 for 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. To learn more about creating SCORM packages, refer to this article for Articulate or this article for Adobe Captivate.
Also note that every LMS 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.
This feature is available for Docebo Enterprise plan and Growth plan clients.
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 file size must not exceed 800 MB for Enterprise clients, and 350 MB for Growth customers.
Please note that 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.
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 Courses 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.
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 LMS 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.
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 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 learning object.
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 Learning Object Repository (CLOR) 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 CLOR 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.
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 CLOR, 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 CLOR.
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.
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, refer to this article for further information.
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.