Scorm Package
Import SCORM files or publish using the platform's LMS-less environment.
What is SCORM?
"SCORM - which stands for Shareable Content Object Reference Model - is a set of technical standards for eLearning software products. SCORM tells programmers how to write their code so that it can “play well” with other eLearning software. It is the de-facto industry standard for eLearning interoperability. Specifically, SCORM governs how online learning content and Learning Management Systems (LMSs) communicate with each other." (scorm.com)
How to import SCORM files
Create a Scorm Package. Open Authoring and select +. From the content type options, select Scorm Package.
Upload a valid SCORM 1.2 or SCORM 2004 package.
Complete all the necessary details as you would do for a Learning Story. Once validated, your SCORM package will be saved in Authoring.
Manage and review. You can see upload versions, upload a new Scorm file, and review the Package Issues and Package Whitelisting. Stories imported to the platform will run on technologies that are licensed under the platform Terms & Conditions. Please also refer to the SCORM Export Terms
Unlike stories that can be saved offline, SCORM packages will not work offline on the platform app, i.e. an internet connection is required to view imported stories.
SCORM Import Validation
Valid SCORM 1.2 or SCORM 2004 packages may be uploaded to the platform. SCORM imports are validated against the standards as per scorm.com and SCORM Cloud. This means that SCORM files should run on and be tested on SCORM Cloud before being imported to the platform.
SCORM Import Analytics
The platform is able to provide detailed analytics not normally available in a SCORM package. You can also make use of selected story settings.
Analytics will record the following from a SCORM package:
Real-time analytics
Audience sessions
Map locations
Demographics
Retention
User ratings & reviews
Certificates of completion will be awarded to users who successfully complete the story with the required pass mark. Certificates are emailed to users and can be downloaded from the app.
SCORM logs (in progress/completed/failed)
Within logs, SCORM-saved data can also be viewed
Download/export log list as .csv
SCORM Import Error Handling
Our LMS-less environment is SCORM compliant. If the package does not work, please run it on SCORM Cloud to test and ensure that it works.
SCORM package issue and device compatibility are not related to the platform environment and import issues are not supported / fixed by the platform.
Package Issues
When packages are uploaded, the platform performs a vulnerability scan on files contain in the package and looks for files that require flagging:
Dangerous. Files that can perform harmful attacks. Packages that have these types of files are automatically deleted.
Unknown. Files that are not whitelisted throw a high / medium warning that should be reviewed.
Suspicious. Files whose extension does not match its mime type throw a high / medium warning that should be reviewed.
Deprecation. Files where technology deprecation has occurred or will soon occur.
Select the "i" icon to view details, and select the cogwheel icons to remove file/remove all types.
SCORM authoring software such as Articulate and Captivate export packages containing .html and flash .swf versions. It is safe to remove flash files from your package and we recommend doing this if they are not needed. The same applies to .gz zipped files.
SCORM "Invalid Package" error
If the uploaded SCORM package has been zipped incorrectly, the "Invalid Package" error may occur. The contents of the content folder should be located at the root of the zip file. When exporting from the Platform, the package is zipped correctly. If a package was unzipped and then rezipped with an additional subfolder, this issue could occur.
Please ensure to send zip packages "as is" from the Platform to avoid issues when the file needs to be uploaded to another system.
SCORM Export Display Issues
In some instances display issues occur when importing to an LMS even if a SCORM package works on SCORM Cloud (all images and elements are responsive). The issues may include:
Cropped images in fullscreen mode.
Cut off buttons when the window is maximised.
Responsiveness to window size appears broken or constrained.
Developer Console flags additional warnings and errors/issues.
The reason for such issues is that content packages have device screen adaption breakpoints. For example, the screen height could be hitting a mobile breakpoint correctly. An LMS configuration may frame the content in such a way that too little height is created on the content.
There are two routes to solving such display issues:
If available on the LMS, it may be possible to change the view setting that will give more height to the content.
Custom changes can be added along with other revisions done for various LMSes.
Please note: as this is a request outside of the scope of the platform's control, changes to support an external LMS are billable per hour.
LMS-specific Display Solution: Cornerstone:
Cornerstone has a full-screen option for the content player, which may solve the issue. The additional UI in the cornerstone LMS shrinks the content player height, causing a mobile breakpoint to occur.
Cornerstone One Player can be launched for supported Learning Objects from the "Training Details" page or from the Transcript. For "Online Courses and Contents", the system checks if a course can launch inline(Within the content player) or if it requires a new tab before users start the launch. This is determined based on the configuration at the "Learning Object (LO)" or provider level. Cornerstone users can configure this using the "Launch Inline" feature on the "General" tab of the online content or courses.
Steps to follow on Cornerstone
Navigate to Admin > Tools > Learning > Catalogue > Course Catalogue and search for an online course or content.
Edit the course.
On the General tab, locate the Launch Inline drop-down field.
Set the launch preference from the drop-down field.
If Launch Inline is set to ON and the provider supports it, the course will launch inline when the user registers and clicks "launch" on the learning details page.
If Launch Inline is set to OFF or the provider does not support launching inline, the user will see a placeholder screen indicating that the course will open in a new tab when they click "launch" on the learning details page. The user can then take the course in the new tab and exit to complete the workflow.
The provider level setting will be considered if the Launch Inline setting is Default.
The Learning Object level setting always takes precedence. If the LO level setting is ON, it supports inline launch even if the provider setting is OFF."
Package Whitelisting
The platform utilises strict CSP (Content Security Policies) to prevent data from being extracted to external links unknowingly - also known as cross-site scripting & phishing attacks. This ensures SCORM packages that may contain external network calls are blocked by default.
As SCORM packages are provided by a 3rd party and the source is unknown to the author, it's important for these risks to be mitigated with best practices when it comes to web application security.
When you import your package, the platform scans the URL links and authors can then decide what should and should not be whitelisted.
External domains included in the Scorm export/package can be enabled/disabled.
Import Errors
Contact your support team. If imported packages do not run once imported on the platform, please retest on SCORM Cloud. If it works on SCORM Cloud, you need to contact your Learning Management System/Authoring platform vendor for support. Bugs and Errors. We will not provide support for SCORM import errors and package runtime errors or bugs. If your SCORM package does not work on SCORM Cloud, you need to contact your Learning Management System/Authoring platform vendor for support.
Scorm Package Layouts. Scorm packages created by other authoring tools may have different capabilities when it comes to responsive design. The platform will only load the package in full screen but not correct display issues originating from external authoring tools. If you have mobile display issues, please query this with the vendor.
SCORM Export Terms
If you create Learning Stories and export them as SCORM files, please consider the limitations that apply.
SCORM packages are limited in their analytic ability due to the nature of SCORM. The exported story can therefore only offer a basic version of analytics, in comparison to the in-depth insights provided by the platform.
Reflective & survey page results can not be tracked on SCORM.
Assignment uploads are not possible on SCORM.
Independent support. We suggest you have support teams in place to assist with the Scorm Cloud testing and package exporting.
SCORM Import packages do not come with a warranty and we do not guarantee that exports will work. The platform can not be liable for any errors when imports do not work on SCORM Cloud.
SCORM packages running on a platform web app only work on evergreen browsers, including Microsoft EDGE, and above. Older or deprecated browsers are not supported.
If a vendor such as Apple, Google, or Microsoft deprecates a browser, the platform will discontinue support for such browsers accordingly. This ensures continued visual, interactive and secure compliance is maintained.
Last updated