Time to review the list of mandatory SCORM 1.2 data elements that I created in Step 19. The table shows:
- the name of the data element;
- is it readable;
- is it writeable;
- the format of the data; and
- the initial value for the element.
You’ll see that I’ve added a ‘dummy’ element called adlcp:masteryscore to store the value (if any) set in the IMS manifest file that’s used when setting cmi.core.lesson_status after LMSFinish() is called. You could argue that this should really be stored in the (optional) cmi.student_data.mastery_score data element, but I don’t want to support any of the optional data elements right now.
You’ll also see that I’ve highlighted 4 elements that require initialization from data that’s stored in the LMS – either student information (name and student ID) or data from the IMS manifest file that’s read during the upload and installation of the content aggregation (course) package. Handling these values will be the subject of my next post.
|Element Name||Read||Write||Type||Initial Value|
|Student Information from the LMS|
|cmi.core.student_id||Identifier||Initialized with data from the LMS|
|cmi.core.student_name||Str 255||Initialized with data from the LMS|
|Progress and Completion Tracking|
|cmi.core.lesson_location||Str 255||An empty string|
|cmi.core.credit||Vocab||‘credit’ or ‘no-credit’|
|cmi.core.exit||Vocab||Initialization not required ? write-only|
|cmi.core.session_time||Timespan||Initialization not required ? write-only|
|cmi.core.score.raw||Decimal/Blank||An empty string|
|adlcp:masteryscore||Decimal/Blank||Initialized with data from the LMS|
|Suspend & (Re-)Launch Data|
|cmi.suspend_data||Char 4096||An empty string|
|cmi.launch_data||Char 4096||Initialized with data from the LMS|