Switching off parts of the API that send certain SCORM data to the LMS sounds ideal, I only wish I knew how to do this.

Through some experimentation, I have been able to prevent ALL cmi.suspend_data from being recorded in the LMS, by:

1. Opening the file: lms.js

2. Finding the section: // SCORM_Save

3. Removing (for case 1.2): SCORM_SetValue("cmi.suspend_data", sTmp);

This seems to remove ALL data for the element: cmi.suspend_data, which prevents the alert message that David mentioned earlier. Unfortunately, this also prevents any data from being recorded, i.e., no tracking.

On the discussion boards of the LMS (Moodle) that I’m using, I’ve seen other people posting their SCORM output/tracking data using the cmi.interactions data element (e.g., cmi.interactions.x.id and cmi.interactions.x.student_response). I was thinking there should be a way to this for a CourseLab course as well.

It seems that each authoring tool is different in how it writes the code that will make the API calls. So I’ve been trying to better understand the code that CourseLab uses in order to customize the SCORM output that results.

I’m open to suggestions … thanks!
-Dan