Wednesday Mar 20, 2013

UPK Player Optimized for Apple iPad

Did you know that UPK Player has an optimized view for the Apple iPad? This feature was introduced in UPK 11.1 ESP 1 (11.1.0.1). The best part is, you don't need to make any changes to your content or send a different link to iPad users. Keep reading to learn more.
[Read More]

Wednesday Jan 02, 2013

Knowledge Center Support of SCORM 2004 3rd-Party Content

You can now import a title that was created using any tool that builds SCORM 2004 3rd Edition content. For use in Knowledge Center the content should be exported and zipped, with the imsmanifest.xml file at the root of the zip file. Once imported, this content can only be played through a knowledge path; it is not available through the Player link in Knowledge Center.

While Knowledge Center does support the SCORM 2004 API as well as the Run-Time Environment Data Model 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 Sharable Content Object (SCO) must send this information to Knowledge Center directly rather than relying on setting the completion and scoring information of its primary objective.

Below is a list of the SCORM 2004 level of support in the Knowledge Center:

  • 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.
  • Knowledge Center does not support cmi.comments_from_lms 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.
  • 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.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.
  • 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.
  • 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.
  • 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.total_time Supported.
  • 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.
  • 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.total_time Supported.

Sunday Mar 20, 2011

Reusing UPK publishing settings

[Read More]

Monday Aug 16, 2010

UPK - Customizing Templates

[Read More]

Monday Jul 26, 2010

UPK - Going beyond the Topic

[Read More]

Monday Jun 14, 2010

Application Demos in UPK

[Read More]

Tuesday Jun 08, 2010

New User of UPK??

[Read More]

Saturday May 15, 2010

Customizing UPK outputs (Part 2 - Player)

[Read More]

Monday May 10, 2010

Extending UPK with Enablement Packs

[Read More]
About

The authors of this blog are members of the UPK product development, management, and marketing teams. On this blog, you'll find UPK news, tips/tricks, upcoming events, and general information on UPK - the easy-to-use, comprehensive content development, deployment, and maintenance platform for increasing project, program, and user productivity.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today