Forum Discussion

Tim_'s avatar
Tim_
Community Member
2 months ago

The persistance is the main problem, and probably why Articulate won't tackle it. Where do you store what the user has typed?

  • In SCORM 1.2, there's no part of the API that lets users store long text.
  • In SCORM 2004 there's a way to store long text, but different servers/solutions might not let you read it back again afterwards.
  • in xAPI you can notify an external record store what the interaction was, but it's not a read-write situation either.
  • If you just publish to web, there's no way to store anything.
  • If you use the Mighty browser extension which extends what Rise can do, they have a long text entry - but again, it doesn't persist the value properly.

You might have seen I've got posts on this all over the community about this subject, it comes up all the time. My current solution is to embed a special Storyline into Rise which persists the value onto an external service.

You can download the latest version of my Storyline file from Github - https://github.com/frumbert/blob.frumbert.org/tree/main/resources

This site shows the full source code for both the web service and Storyline javascript.

I mainly run my Rise courses on Moodle, and as such I also made a Moodle plugin that acts as the data-store, and the above Storyline file already tries to connect to that before failing over to an online server. You can get the plugin here - https://github.com/frumbert/local_blobstorebackend

There's also a 'Export' button Storyline file which compiles all the learners responses in the course and downloads them as a PDF, which I normally add to the conclusion pages in my courses.