Rise & Storyline: Reflections/Journaling issues

Hi Robin

We have done a number of projects in Storyline where the creation of a downloadable learning journal was required and I have published a couple of articles here on how to use JavaScript to do this.

I also published an article on doing this in RISE using local browser storage. The problem with RISE being that you can embed Storyline Blocks to collect learner input - BUT the Storyline variables are not retained once you exit the Storyline block. To some extent this is similar to your challenge. In the RISE demonstration we did, there are a number of Storyline blocks and we needed to consolidate the learner input from each block into a single pdf document at the end of the RISE course.

In your case you have a number of Storyline modules, but the problem is the same. As Robert correctly surmised, this can be done using local browser storage BUT, the caveat is that you will lose the data betweeen modules (a) if you change browser (b) if the learner clears the browser cache or (c) if you take each module on a different device. So, although it would work it isn't ideal.

The real answer is that you need to find somewhere to store the data between modules. And that means writing it to a file or a database somewhere. We use pdf forms as the template for our learning journal because it means they can be modified easily withoout having to change any code. We are about to start a project where we will attempt to open a pdf form template - write to it - save it with a filename specific to the learner - then pick that file up again and append more input to it. I will let you know how that goes!

The other possibility is to write the learner input to a Learning Record Store (LRS) using xAPI - but I'm sure there are far better qualified people here to advise you on using xAPI calls from Storyline.

Hope that helps.