Forum Discussion
Storyline Course that Branches by Roles
Wouldn't it be simpler to use the LMS to do the branching part? Any modern LMS will "know" the person's role (if by that you mean "job"), and you can just assign the appropriate version of the course to each person.
Even though an LMS may (or may not) "know" a learner's role, unit, department, division, and/or leadership hierarchy, because the SCORM data model does not include it, there is no mechanism to retrieve that information into a course.
Learner-specific data elements consist of:
cmi.learner_id (long_identifier_type (SPM: 4000), RO) Identifies the learner on behalf of whom the SCO was launched
cmi.learner_name (localized_string_type (SPM: 250), RO) Name provided for the learner by the LMS
The "learner preference" data elements, which may or may not be supported on your LMS, include:
cmi.learner_preference._children (audio_level,language,delivery_speed,audio_captioning, RO) Listing of supported data model elements
cmi.learner_preference.audio_level (real(10,7), range (0..*), RW) Specifies an intended change in perceived audio level
cmi.learner_preference.language (language_type (SPM 250), RW) The learner’s preferred language for SCOs with multilingual capability
cmi.learner_preference.delivery_speed (real(10,7), range (0..*), RW) The learner’s preferred relative speed of content delivery
cmi.learner_preference.audio_captioning (“-1”, “0”, “1”, RW) Specifies whether captioning text corresponding to audio is displayed
Nowhere in the SCORM spec are there either learner data elements beyond user ID and name, there also isn't a means to retrieve it if you wanted to go the route of using GetValue(element : CMIElement) : string, because it is expecting an existing SCORM data element in the parameter.
