In addition to content created with Developer, Knowledge Center can import and host most content created to SCORM 2004 specifications by other tools. Such content is referred to as "external content" or "3rd party content." Knowledge Center uses SCORM 2004 RTE semantics to communicate with learning objects (SCOs). While Knowledge Center does support the SCORM 2004 API as well as the Run-Time Environment Data Model (see specifics on conformance below), it does not support the Sequencing and Navigation functionality of SCORM 2004. For external content to operate correctly when hosted in Knowledge Center, it must be written to function correctly in the absence of this functionality. In particular, if completion and scoring information is to be properly recorded, the SCO must send this information to Knowledge Center directly rather than relying on setting the completion and scoring information of its primary objective.
Conformance With the Run-Time Environment Data Model
Below is a list of each of the data model elements and level of support in the Knowledge Center
cmi.comments_from_learner
Knowledge Center includes a more versatile mentoring and feedback facility that allows for two-way conversations. Therefore it makes no use of comments submitted through the cmi.comments_from_learner data model element. However, any user comments written by a SCO will be saved and be available for retrieval by the SCO throughout the current attempt.
cmi.comments_from_lms
Knowledge Center does not support this functionality outside of its mentoring and feedback facility. Therefore, the cmi.comments_from_lms array will always be empty, and a get on cmi.comments_from_lms._count will return 0.
cmi.completion_status
May be set either directly through setting the value of cmi.completion_status or indirectly through setting cmi.progress_measure.
cmi.completion_threshold
Set in manifest file. Allows the Knowledge Center to set cmi.completion_status based on setting of cmi.progress_measure.
cmi.credit
Always returns "credit".
cmi.entry
Returns "resume" if resuming a suspended attempt. Otherwise returns "ab-initio".
cmi.exit
Accepts all vocabulary tokens, but all values other than "suspend" are handled as normal session end. Logging out is handled through the Knowledge Center user interface and there is no special support for timeout.
cmi.interactions
Supported. However, since Sequencing and Navigation is not supported, interaction objective id's will not map to anything. The SCO is still free to use interaction objectives for its own internal use.
cmi.launch_data
Supported.
cmi.learner_id
Supported.
cmi.learner_name
Supported.
cmi.learner_preference
Knowledge Center does not use user preferences and has no mechanism to set these preferences outside of the RTE. Therefore, user preferences will initially return their default values. These may be set by the SCO and will be maintained for the duration of the attempt, but when the attempt ends they will revert to their defaults.
cmi.location
Supported.
cmi.max_time_allowed
Set in manifest file. Knowledge Center does not support any special time-out condition, so if the SCO supports time-out and sets cmi.exit to "time-out", this will be no different from setting cmi.exit to "normal".
cmi.mode
Always returns "normal".
cmi.objectives
Available for use by the SCO. However, since Sequencing and Navigation is not supported, objective id's will not map to anything and the array will initially be empty. Setting the success status or score of an objective will have no external effect. The SCO is still free to use the objectives array for its own internal use.
cmi.progress_measure
If set, in combination with a specified value of cmi.completion_threshold, the Knowledge Center will override any explicit setting of cmi.completion_status and evaluate completion status on its own.
cmi.scaled_passing_score
Part of Sequencing and Navigation and not supported.
cmi.score
Supported.
cmi.session_time
Supported.
cmi.success_status
Supported. Since Sequencing and Navigation is not supported, cmi.success_status must be set explicitly, rather than through objectives or cmi.scaled_passing_score.
cmi.suspend_data
Supported.
cmi.time_limit_action
Set in manifest file. Knowledge Center does not support any special time-out condition, so if the SCO supports time-out and sets cmi.exit to "time-out", this will be no different from setting cmi.exit to "normal".