What is it? "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)
Falkor's 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 Falkor environment and import issues are not supported / fixed by Falkor.
When packages are uploaded, Falkor 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 ocurred 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.
Falkor 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, Falkor 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.
Contact your support team If imported packages do not run once imported on Falkor, 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 Falkor 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.
Upload your Scorm Package then complete all the necessary Editor details as you would for any story.
In "Scorm Package", you can see upload versions, upload a new Scorm file, and review the Package Issues and Package Whitelisting. Stories imported to Falkor will run on technologies that are licensed under our Terms & Conditions. Please also refer to Falkor's the SCORM import terms.
Falkor is able to provide detailed analytics not normally available in a SCORM package. You can also make use of selected Falkor story settings.
Falkor Analytics will record the following from a SCORM package:
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 Falkor app.
SCORM logs (in progress/completed/failed)
Within logs, SCORM-saved data can also be viewed
Download/export log list as .csv
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 Falkor.
Reflective & survey page results can not be tracked on SCORM.
Assignment uploads are not possible on SCORM.
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. Falkor will not be liable for any errors when imports do not work on SCORM Cloud.
SCORM packages running on a Falkor web app only work on evergreen browsers, including Microsoft EDGE, and above. Older or deprecated browsers are not supported.