SCORM Driver Cross Domain

Remain in control of your SCORM content—deliver it directly from your servers.

SCORM Driver

  • Allows your client to continue using their LMS rather than having data spread across systems, or worry about trying to push data back into their LMS from your system later
  • Allows you an easy way to push updates of your content to your clients without having to send them new files
  • Proxy files are small, so your clients don’t have to worry about hosting large content files

 

SCORM Driver is free for
non-commercial use.

SCORM Driver Cross Domain (SDXD)

SCORM really likes for content and the player to reside in the same domain.

Why?

Basically, SCORM requires that content be served from the same domain as the LMS API. Browsers intentionally prevent the JavaScript in the content from communicating with the SCORM API if they originate from different domains.

For content providers, this can be problematic for lots of reasons — maybe your content is database driven or the user experience is just better on your server. Regardless, we’ve come up with an option that lets you control the user experience and maintain the content assets on your server, but still meets your client’s request of delivering the course via SCORM. We call it SCORM Driver Cross Domain (catchy isn’t it?)

What is SCORM Driver Cross Domain and how does it work?

scorm-driver-cross-domain-diagram
 
SCORM Driver Cross Domain is our solution that enables your custom content to make calls to a 3rd party LMS. Your content can really be any format (no SCORM required!), but through the magic of SCORM Driver Cross Domain code, it will communicate the key SCORM data back to the Client LMS.

SCORM Driver Cross Domain produces a proxy .zip file (available as SCORM 1.2, SCORM 2004 or AICC) for your client to import and launch through their LMS. Upon launching the proxy file, the learner is actually directed to your servers to access the course. Once the user exits from your course, the SCORM Driver Cross Domain file sends the key information (Completion; Score; Time; Pass/Fail) “Big 4″ data back to the Client LMS. If you are using the SCORM 2004 proxy files, you can also send back interaction details to the client LMS.

As the content provider, you will have complete insight into how users are interacting with your content, and you maintain complete control over who has access to your content.

Will my clients have to do something different to use this type of course?

From a client perspective, the SCORM Driver Cross Domain package appears like any other SCORM package. The key difference is that you are providing a proxy file which will enable the course to be accessed from the Client LMS, but played on your servers.

Clients import the SDXD SCORM package on their LMS just as they would any other SCORM package. The course registration and launch process in the Client LMS also remains the same. When the learner launches the course, the Client LMS will pass Student Name and Student ID to your server so that you can track their progress.

Using SCORM Driver Cross Domain is also great for your clients:

  • SDXD allows your client to continue using their LMS rather than having data spread across systems, or worry about trying to push data back into their LMS from your system later
  • SDXD allows you an easy way to push updates of your content to your clients without having to send them new files
  • SDXD proxy files are small, so your clients don’t have to worry about hosting large content files

Interested in learning more? Contact us and we can talk about your specific use case to find the right solution.

 
 

Some places SCORM Driver is being used:

who uses scorm driver