Have you ever run into a situation where your course doesn’t pick up where you left off when you view it more than once on your LMS? Or maybe it does, but you’d prefer it start over from the ...
Published 10 years ago
Version 1.0
Blog Post
Your LMS doesn;t conform to the SCORM 1.2 standard then, which in this case is a happy situation for you. 4K is the limit. A lot do conform to that limit.
cmi.comments is another read write data field available to the courseware. The official definition is:
cmi.comments (CMIString (SPM: 4096), RW) Textual input from the learner about the SCO
Note it's read / write and is another 4K so basically 'doubles up' on the suspend_data field.
It's not something you could implement yourself (well you could with Javascript calls, but there would be no point as the suspend_data is still going to be used to store bookmarks currently as that is what Articulate decided). It is something that Articulate would have to implement in the back end.
cmi.comments is another read write data field available to the courseware. The official definition is:
cmi.comments (CMIString (SPM: 4096), RW) Textual input from the learner about the SCO
Note it's read / write and is another 4K so basically 'doubles up' on the suspend_data field.
It's not something you could implement yourself (well you could with Javascript calls, but there would be no point as the suspend_data is still going to be used to store bookmarks currently as that is what Articulate decided). It is something that Articulate would have to implement in the back end.
- 4K in the spec is a floor (minimum), not a ceiling(maximum) :) An LMS that doesn't limit suspend data string length isn't necessarily non-conformant.
I'm in agreement about using bookmarks for the bookmarking string. Suspend data truncation is something we contended with frequently when we published to SCORM 1.2. OR, at the very least, moving the restore location to the front of the string so it's never chopped off.
We've been using SCORM 2004 for awhile because our system supports better reporting of interactions in 2004.- The SCORM 1.2 specification states that suspend_data is of type CMIString4096. The specification defines CMIString4096 as "A Set of ASCII characters with a maximum length of 4096 characters". Note the use of the word maximum, not minimum. In software implementation specifications, limits are always maximums so the appropriate data type can be used to ensure efficiency.
The other way to look at it is that if courseware sends a string in excess of 4K characters, then the courseware is non-compliant. In that sense Storyline sending over 4K is non-conformant and the LMS that rejects it is conformant.
