Tin Can (xAPI)
Because of the nature of our courses, we have started using Tin Can API, and being of very little brain, I don't really know much about it, so I'm just hoping for some suggestions on this problem.
Using SCORM 2, our LMS provider was able to force our content to talk to the LMS when the content was unexpectedly closed, giving users a fighting chance of retaining the score they had achieved up to that point. The nature of our organisation means that's not uncommon, doctors often drop a learning module to do something more urgent, and expect to see their progress to that point recorded.
We've lost that option with Tin Can, Rustici, in short, say it can't be done, and the 'early stop logic' would have to be part of the course code itself. I'm just wondering if anyone has experienced this , and could suggest a way of applying that early stop logic to a course in terms a simple person like myself would be able to use?
Thanks in advance :-)