logo

SCORM Runtime:

Please visit SCORM SCOBot Runtime APIs for the latest info.


SCORM doesn't have to be a 4 letter acronym.


Lets take a look at implementing SCORM on your LMS.

Why would I use this?:

SCORM (Shareable Content Object Reference Model) was designed for the portability of shareable content objects (SCOs). We will take a closer look at 3 key areas to make this easier to digest. Once we get the general overview, we'll go a little further with some high level technical implementation. There is roughly 400 pages of whitepaper specification documents between both versions of SCORM. Ok ready? Lets go!


Authoring:

Content can be hand crafted, it can also be generated from templates, forms, and csv/excel. This is often blended with media (movies, audio, images). This can range from activities, games, quiz, surveys, quizzes which all can be reported on.


SCORM Package (export)

A zip file us used to bundle the files with a required manifest file. This manifest lists out things needed to inform the Learning Management System of the version of SCORM to use, Title, and Item(s) of content objects or Assets to launch. This is all described in XML which employs the ability to support a one-to-many relationship.

This enables the portability of taking content from one platform to another.


LMS with SCORM (import)

Learning Management Systems commonly act as a portal for administrators and students. SCORM packages are imported, parsed and added for assignment.
The LMS has the responsibility to expose SCORM Runtime APIs, set the student attempt data model and support the student as they interact with the content submitting data, committing it and retrieving it.


How do the SCOBot Runtime APIs work?

Made in tandem with the content API above, the Runtime API's use JavaScript Object Notation (JSON) data which is well defined within a student attempt. This is a vertical slice of logic that you would use in your lesson viewer. This is where you'll find all the collected data about status, score, time, and more. The runtime manages requests the Student Attempt Data by namespace. This makes it easy to save and retrieve this format against your own backend services written; managed in any language you support. In order for data to flow from your platform, to your backend services, SCOBot uses a series of events you can listen to. This is your queue to save student data or end the course. In short, the Runtime API's manage the flow and access to the student attempt data, and emit events you can subscribe to. With SCOBot, SCORM 1.2 and SCORM 2004 share the same data model structure so your team doesn't have to deal with version differences.


Please visit the main page for more info.


Check SCOBot (SCORM 2004, 1.2 Content API): SCOBot

Or visit cybercussion.com for more tools and support.