SCORM 1.2 Suspend Data--Seems Wonky to My Pea Brain

Hi Robert,

Pretty much what happens is the storage on the LMS or cache is where the limit gets hit. So it doesn't matter what you're doing. It is the volume passed, hit limit and then dead end.

Best way to see what is happening. Have a course of 10 slides. Complete go through, and it gives completion. The learner relaunches the course and shows up on page 7, the learner has to complete the last three pages to get completion, or it will show in progress. The server holding the bookmarking information is complete, so it will never let you fill pages 8, 9 and 10. That is the cmi limit or cap. This puts everyone into a looping effect where don't go back into courses, or if you do, it ends up starting on the page it maxed out at.

So your discussion of javascript, etc., is a moot point. Solutions are pushed to the 2004 standard and make the content smaller in volume to fit within the limit. The limit is stupid for 1.2. 2004 a bit better, and in a tin can/cmi5, it is fully open throttle. Your javascript would work great in tin can/cmi5.

Having said this, the LMSs and Articulate need to do better at compression. Lazy design in the systems is what is creating this headache. Not us designers, the developers. The funniest thing ever is why on earth would a command that is on 6 mg be so limiting when size doesn't matter. The intelligent thing would be for LMS or Articulate to design a code that would stretch that limit; not like we don't have the size now since we are talking exabytes of information.

Cheers,
Doug Kipta, CTDP.
Advisor, Learning Systems and Platforms | HR Learning Services | Suncor Energy Inc.
C: 403.296.8696 | C: 403.650.4722
dkipta@suncor.com

HR Learning Services Portal