Happy Friday to ya.
A question out to the folks that are using the xAPI format for bringing in courses.
We are running through our annual compliance over here on the East Coast and are running into what I can only describe as the normal amount of issues with SCORM courses.
My finding with SCORM courses is that it is stable - but SCORM can be finicky format - it needs pretty constant communication with the LMS….and when a person walks away from their workstation...well there is always a risk with the LMS going out of session compared to the course remaining open in the browser - which is a common one that we find ourselves troubleshooting as folks put stuff down and then repick it up alot during this season.
Sometimes we have to do something special to put the course back on path. Other times - the course gets into such a funky state? We find ourselves needing to intervene heavily with the user experience.
We did do the typical LMS troubleshoot already to support SCORM. Session times before logout have been extended to assist our users. We can’t get to cray cray - we extended it to two hours before warning and logout.
My understanding - xAPI communication is not based on CMI interactions and is not based on the same communication approach. It is alot more verbose and was supposed to be a champ in terms of stability when I looked at it in the past. It is (what I read about years and years ago) supposed to be the “great white hope” in terms of communications and help with those folks with mobile devices and things going out of session was supposed to be a thing of the past.
So my questions | Is this true? For yawl using the xAPI course format - do you find that you have less of the typical SCORM issues?
We are not being tortured by it - but it would be nice to diminish the noise if it feels better.
