A client is delivering courseware without using an LMS. They want the learner to be able to bookmark and exit and then resume from where he left off. The catch is that they want the student to be able to resume an any other machine. In the current TOC settings, the navigation is set to Visited Slides Only to prevent a learner from skipping ahead. There is no problem stashing the slide number of the last slide the learner saw in an external database and returning to that specific slide. BUT, if, for example, the learner bookmarks page 20 and then is returned to that page (again, we can do this), the TOC shows that the previous 19 slides are unchecked and therefore cannot be accessed via the TOC. What is needed is a way to reestablish the completion checks on the previous slides (an array value, we suspect).
Yes, and the built in Captivate "resume" function works fine on the same machine. But if a learner starts the program on a computer at work and then tries to resume at his home computer, he has to start from scratch.
That's because the "cookie" is stored on the computer. You would need something external and common to both machines to share the information, like an LMS or Database or even a Google Sheet.
I realize the cookie is being written, I understand that, The issue I am raising it is it possible to grab the variable values that are the cookie data so that I can, in fact, store it in an external database and use that data to configure the set the TOC checkmarks on another machine?
I haven't actually messed with the TOC, but I imagine that it's writing localStorage with HTML5 so you should be able to type, localStorage in your console and see what it returns. For swf it's a sol or Flash Cookie.
I kinda figured it would be something like that, sorta. I was also hoping that someone would know what variable was tracking what I assume would be an array value and that I could get the array contents via a js routine when the learner click an save place and exit button. And I was also hoping to meet the Easter bunny.
It's actually writing an array to document.cookie, so not localStorage, just a regular cookie. So since you are running in the same domain you should be able to read the cookie, or possible the internal array.
You have absolutely confirmed my suspicions about the array, and it is, readable via the console. The issue the is to uncover the variable that the TOC creates the cookie from so that it can be set on program entry based on the array data stored in the database.
12
Replies
AdChoices