Forum Discussion
Storyline Suspend_data decipher
Just stumbled upon this conversation in search of the real point of the debug log if you can't decipher the data string(s.) I am in that situation now. I am looking at both debug and LMS course transaction reports from a sample course published in: SCORM 1.2, 2004 - 3rd and 4th ed.
I want to see the data interaction between the course/player and the LMS to see what is the most efficient platform. I haven't even worried about xAPI yet. I've been able to parse the debug and report data, but not make sense of it without the "decoder-ring."
In reference to David Keeling's request I believe the standard for SCORM 2004 will do just that.
In the parameters it has one for course tracking and completion and one for tracking quiz completion.
SCORM1.2's (lesson_Status) was split into 2 parameters in SCORM2004; ‘completion_status’ (completed/incomplete) for the course and ‘success_status’ (passed/failed) for the quiz. Now whether SL sends both calls is another matter which is why I am attempting to decipher the debug and lms data reports. Is there any way to read or decipher the debug log?