scorm-for-wordpress

Introducing Native SCORM Support for WordPress

The Tin Canny LearnDash Reporting plugin has been a very interesting initiative for us. It opened up LearnDash in a bigger way to enterprise users and proved that it was possible to use WordPress as a viable Learning Record Store (LRS) with advanced reporting. Organizations around the world are now using it, but one thing that’s always been missing is a way to capture SCORM data inside LearnDash. Maybe a business had some content output to SCORM that they couldn’t republish to Tin Can/xAPI, or maybe they were using a product like Articulate Rise, which doesn’t even support Tin Can/xAPI. Whatever the case, today we’re very excited to announce that SCORM modules can be tracked natively inside WordPress with our Tin Canny plugin.

At this time of this post, the Tin Canny plugin officially supports SCORM 1.2 and 2004 as well as xAPI / Tin Can for Articulate Storyline 2, Storyline 360, Articulate Rise (SCORM only), iSpring, Adobe Captivate 9 and H5P (xAPI/Tin Can only). It’s been a lot of work but we’re especially excited to welcome Rise, iSpring and Storyline 360 to the plugin.

Please note that this is the first release for supporting all of this modules, so it’s a good idea to test your modules first and make sure data is being tracked as you expect it to be. The SCORM support is especially important to consider here, as what we’re doing is capture the SCORM data and then using a wrapper to essentially translate it into Tin Can statements. This makes it reportable along with all Tin Can/xAPI data for consistency, but this also means it may look different than expected if you’ve been using another Learning Management System (LMS).

Version 1.2 of Tin Canny LearnDash Reporting includes all of these updates and more. We also added an easy way to clear all Tin Can data for testing purposes, additional quiz data validation and made some minor changes to user experience.

We hope you enjoy the addition to the Tin Canny plugin!

4 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *