Forum Discussion
SCORM 1.2 Suspend Data--Seems Wonky to My Pea Brain
For the last couple of weeks I've been working on a SCORM 1.2 resume issue for a Storyline 2 course that I'm trying to finish up on for a client. I posted on this previously but that post appears n...
Hi All, I don't know if we've ever seen a solution that has improved this yet over the years. I totally follow and get what everyone is saying.
Something new is now rearing it's head. Articulate Rise - which we don't know how it layers and we don't know what version updates they do to the software because it is cloud based. The problem is back.
I build a 30 page course. I completed it to 100% but when i go back in to use it as a resource it only shows i took 71% of the course. Perfect case that i can recreate.
So everything above is back again and now we don't even know and are guessing what is going on in the versions of the cloud based software.
Problem is not the authoring tool is saying do this and the LMS's are taking the brunt of possible lazy design or coding.
Thoughts.
Hi Doug,
I had this problem once and it got resolved by changing all my slides and layers to "reset to initial state". that fixed it for me.
I appreciate your advice but I've tried this where possible. The base
layers must stay Saved State due to variables. This hasn't helped so far.
Thanks for the feedback.
NoraNora.
Did you publish as scorm 2004? Because that is pretty much the only solution. Until articulate fixes their compression. My gut says it’s a fight between lms not letting more through and authoring getting lazy on compression until we all get frustrated and force them to fix it. Which ain’t gonna happen.
only other solution may be to make smaller file or don’t worry about the bookmarking after you complete. Hit that threshold. Funny thing is we don’t know when or what page it’ll hit the limit.
I’ve used scorm 1.2 for since 2001 and never had problems until last year. Never used 2004 until then. It solved the problem. Cmi5 and tin can will resolve it as well as they handle bug data very well. But reporting is way different. But worth time.
thoughts. I have more thoughts and suggestions maybe pm me.
Hello all,
If most suspend data threads are saved (when tested across devices and browsers), then the logic is working.
If there are occasional problems, it is likely that the suspend data thread is corrupted due to a loss of connection between the client and the server, while the client (the learner using the courseware in the browser) had continued to navigate through the course.
I suggest developing JavaScript that runs in the Storyline client, and that pings the server, and saves the suspend data thread each time the learner navigates from one screen to another. If the "ping" returns a message that the server is not found, then message the learner that they should close the browser, and re-launch the course. It should (all else being equal) re-launch from the previous screen.
This is a suggestion, others please join in. If this doesn't make sense, please post your reasoning.
Thanks!
Robert
Robert Edgar
Program Manager, Learning Systems Design and Development
Director, Stanford Redwood City Digital Production Studio
Stanford | University Human Resources | Learning Solutions Group
485 Broadway, University Hall, 3rd Floor, Room U309
Redwood City, CA 94063
Cell: 650-387-5914
Visit Us Online: Learning Solutions Group
Stay Connected: Cardinal at Work Connect
See Our Studio: https://redwoodcity.stanford.edu/campus-resources/srwc-digital-media-production-studio
Robert,
Not all of us are proficient in JavaScript to be able to utilize this type
of high-end coding solution. I really need something that I can apply
either within Storyline or within the LMS without having to resort to
outside custom solutions. I'm not trying to be offensive, I am just sharing
where I sit in terms of my expertise.Nora
