Skip to main content
LMS_90
Inspiring
June 8, 2018
Question

Saving status/state in branching scenarios possible?

  • June 8, 2018
  • 11 replies
  • 928 views

Hi all,

I have an upcoming project where the one lesson has a million branches. They want status to be saved on each of the branches. They can jump around all over so there is no linear flow through it at all. They will be hosting as SCORM 1.2 in CornerStone.

So the regular bookmarking won't be good enough because they want the user to be able to see how much of each section they have completed. Now I can do that DURING a session by keeping variables and using states to show little progress bars. But when the user exits the lesson, those variables of course, are all gone.

I now Rod Ward had a cpExtra utility that could save variables, but the user has to log in from the SAME computer.

What I need is a way to save a whole bunch of variables as to the progress in each section and be able to retrieve them from the LMS to load up when the user launches the lesson a 2nd, 3rd, etc time.

Am I making sense here?

Is there ANY way to do this???

Big client and great job opportunity, but I don't want to tell them it can be done if there is no way.

Thanks everyone!!

Lori

This topic is closed to new replies. Start a new post to keep the conversation going.

11 replies

Inspiring
June 11, 2018

My company uses CornerStone OnDemand LMS as well, and with us variable values are persisted accross sessions all right. You're sure it's not working for you? Of course, they must not have a default value.

LMS_90
LMS_90Author
Inspiring
June 11, 2018

Interesting.

They must NOT have a default value? Never thought of that, but it makes some sense now that you say it.

How are the variables persisted? Are you actively doing something to store your user variables? Or are they getting stored automatically for you?

Inspiring
June 11, 2018

I think they're stored with the resume data. No specific action required to turn this on, other than making sure LMS Bookmarking is active ('Never Send Resume Data' unticked). But that's the default setting anyway, I think.
No Default Values on the tracking variables, as otherwise those would overwrite the values stored by the LMS on course relaunch.

thisguy4xapi
Inspiring
June 8, 2018

Another option would be to get use an LRS and save as an XAPI statement that could be recalled from LRS.

Brian

Moderator: ditto

LMS_90
LMS_90Author
Inspiring
June 8, 2018

can you elaborate on this. I've not done LRS or XAPI.

thisguy4xapi
Inspiring
June 8, 2018

Sure, xapi is a more robust way of reporting than Scorm. An LRS (learning record store) is how and where you store xAPI statements. They typically consist of 3 parts. An actor a verb and an activity. For instance Brian finished section 1.

The nice thing about an LRS is it can work in conjunction with an LMS, but unlike most LMS you can easily pull data back out.

Scorm Cloud is a good place to start for a free LRS. You do have to do a bit of JavaScript to hook it all up, but it’s fairly painless.

thisguy4xapi
Inspiring
June 8, 2018

You could save them to local storage for that user, and recall them that way.

Brian

Moderator: please do not post personal credentials!ç

Lilybiri
Legend
June 8, 2018

That is the same solution as with the CpExtra widget whch has been rejected: local storage is not an answer.

It is indeed something that should be solved with the LMS, externally.