SCORM (Shareable Content Object Reference Model) is a collection of standards and specifications for a web-based LMS. It defines the communication between client content and a host system, called a run-time environment. SCORM also defines how content is packaged into a transferable ZIP file, called a “Package Interchange Format.”
Your Docebo LMS 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 the Docebo LMS, but should not be used as an expert guide in SCORM content at large. To learn more about creating SCORM package, refer to this article for Articulate or this article for Abobe 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.
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 Courses item. On the main Courses Management page, select a previously created course from the list of courses. Press the menu icon in the course’s row, then select Training Material from the dropdown menu.
Once you have opened the Training Materials page, 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 computer.
When uploading SCORM packages that contain only 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 when uploading SCORM packages with no embedded sequencing. You can change the settings for this later when managing the learning object’s settings. For more information about SCORM sequencing, refer to this SCORM.com article.
Then, select the view mode for each device on which the course will be plated, and move to the Additional Info tab. Select or upload a thumbnail for the learning object, then give a short description of the content for your learners. In this tab you can also add tags to your learning object 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 object will be uploaded as new course material, and a message will be displayed on the top left of the page. The SCORM package object is now course content, and is ready to be displayed.
Uploading SCORM Content into the Central Repository
For those that want to upload a single SCORM package and push it into multiple courses so the learner only has to view the content one time, in any of the courses in which the content is placed, you should upload the package into the Central Learning Object Repository (CLOR).
By uploading the content directly in the CLOR and pushing it to one or more courses, the package is then share-tracked between all of courses. This means that the learner can avoid playing the content several times in several courses. To learn more about this process, refer to this article.
SCORM Package Requirements & Best Practices
Please remember the following information when uploading or editing SCORM content in your LMS:
– The learning object must be uploaded into the platform as a zip package. Please note that the manifest file (imsmanifest.xml) must be placed at the root level of the folder. It is also strongly recommended that everything needed to deliver the course should be placed within the zip file.
– The file size must not exceed 800 MB for Enterprise clients, and 350 MB for SMB customers.
– The Docebo LMS does not accept SCORM packages with content using the following file extensions: htaccess, phps, php5, php4, ph3, php, cgi, sh, shtml, asp, aspx, jsp, py, rb, pl.
You can only replace the original package of a SCORM learning object with a new package of the same SCORM version (i.e. if the original package that you uploaded in SCORM 1.2 version, you cannot edit the object by uploading a SCORM 2004 3rd edition version).
– If you plan to have learners play a SCORM object with a tablet device or smartphone using Docebo’s Mobile App, the package should be 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.
– If you are updating a SCORM object directly in the CLOR, the new version of the object will be published immediately and playable in the courses in which the object is placed. If you’re uploading the learning object directly in a course, you may have to wait approximately 30 minutes to an hour before the updated version is playable in the course. Therefore, it’s strongly recommended to upload and edit SCORM learning objects in the CLOR.
– Once you completely delete a SCORM learning object from the platform, the tracking of said object is also deleted and no longer retrievable.
– If you unenroll users from a course after he or she has completed the SCORM object in the course, the tracking for this user is not deleted. Once you re-enroll the user into the course, you will be able to view the tracking again.
– The LMS only accepts SCORM packages using HTTPS. If you upload a package that references an HTTP address, the browser will block users from playing the content in the platform. You should check the browser console or error messages, as the Docebo interface does not provide an error message in these cases.
– You may run into problems playing your SCORM package in the platform if it contains an iframe if you’ve set the view mode of the learning object to play inline or in a lightbox. To avoid issues, test playing the object in a new window, or check your browser console.
– In order for users to properly let the LMS know that they are done playing a SCORM object, it’s important that they press the Close button (may be called the Exit or Submit button) in the object so the package is recorded accurately. By not pressing this button when a learner finishes viewing the content, the progress may not be sent from the SCORM package to the platform, therefore please communicate to learners that it’s important to press this button before closing the window or tab.
– Please note that for SCORM 2004 3rd Edition packages, your LMS reports the score as it is reported by the cmi.score.raw and not by the cmi.score.scaled.