Remembering progress, capturing resume data without scorm

[Adam Palethorpe]

Hi All, I have searched the forum and cannot find a fix for our specific needs, hopefully someone can point me in the right direction...

Task: Remembering student progress to continue from where they left off

Hurdles:

We do not use scorm, and we use our own LMS. The problem we have at the moment is our courses are split into modules, at the end of each module we have an advanced action that points to a page that then logs the module as complete on our system and it allows them to continue from the next module once they log in.

We want to switch this to remember each slide, just like other mainstream LMS do. Initially we thought about looking for the 'resume data' captivate sends out but we have had no luck. We don't use a TOC either. Is there any data that captivate sends out (ideally in the html5 version) that we can capture to use as a unique ID for that slide?

OR

Is there something else we can explore to try and get this feature added?

Come on captivate gurus!

[shriyanshagnihotri]

Please answer following

1) Is your LMS is following certain LMS standard such as Scorm 1.2 or something similar? If so then which one.

2) What are the options selected by you in Quiz preferences, Please give value of field "LMS" and "Standard" that you have selected?

Regards

Shriyansh

[DennisLamberti]

Hi Adam

I am watching this closely because I would also like to do what you need. So far it looks like we may have to do some work in Javascript.

Regards

Dennis

[shriyanshagnihotri]

Hi Dennis,

That is right, In case if you want to track the current slide by user and your LMS dose not support resuming (considering you are using internal server as LMS), then the way to track is to subscribe The next slide event(defined in JS interface of Cp8) or something similar and implement a server side and client side code that can take care of resume logic.

I am not sure what exactly the details of Adam's LMS server, so not sure what difficulty he is facing.

Regards

Shriyansh

[Adam Palethorpe]

Thanks shriyanshagnihotri that looks very promising, I have forwarded that info on to our techies.

[shriyanshagnihotri]

Hi Adam,

May be this will help your team more. JS interface help.

Common JS interface

Regards,

Shriyansh

Adobe Engineering Team.

[Adam Palethorpe]

Shriyansh that link looks extremely valuable, I am not techie myself (just a Graphic Designer with limited tech knowledge) but it looks like it could really be of use. I have sent it on to the tech team, fingers crossed.

Thanks

[Adam Palethorpe]

Hi, sorry for the late reply.

We do not use any standard for LMS, we publish to html and flash and we do not use Quiz's to score, we use quiz slides just as interactions to keep the user engaged and have our own test at the end of the courses.

It is uploaded to an LMS created by our techie which is basically a system that 'plays' the published files in an iframe window or something similar. After each module the last slide has a continue button which points to a 'Congratulations' page which then logs that the user has completed the module and that is where they start from if they log out and return.

So we have say 20-40 slides in each module, and we have a system that remembers each module that is not reliant on captivate in any way.

It is driving us mad with problems and invonveniance for our learners - when things go wrong they have to re-sit the whole module. We have looked into getting a better LMS but it is very tricky as we have a complete custom built system that runs everything for the business and this taps in to that.

After my own research I have found that the key to other LMS remembering individual slides is in the 'send resume data' field, is that right? I was hoping we could find out where it sends that data too, or where it could be picked up from and then get our techie team to grab it just like any other LMS would.

At the moment a lot of the problems are being blamed on long modules, some of which are only 20 slides, the most being 45, which I do not see as a problem personally. It is a shame because captivate is such a lovely platform and this is not doing it justice at all.

If I can point them in the right direction in terms of capturing this slide by slide continue data using info sent out from captivate, it might not fix all of the problems but it will mean trainees will only lose the time of 1 slide as opposed to 30.