Your client wants to deploy UPK content to a Moodle IMS server. The client mentions that
Moodle’s support for SCORM 1.2 is better than its support for either SCORM 1.3 or AICC. The
client wants to take advantage of the better support.
Identify two configuration settings that would make this possible when a course is published.
A.
Select “Create zip file from published Player package.”
B.
Select the SCORM version 1.2 from the drop-down list.
C.
Set the prefix URI to the location on the server where content will be deployed.
D.
Rename imsmanifesti2.xml in the player package imsmanifest.xnl.
E.
Set LmsConfig.ScormVersion in config.js to 1.2.
Explanation:
Note on B:
Note 2:Just created a LMS package without issue. But when publishing on our LMS (we’re using
Oracle iLearn) the module would work fine until I try to run one of the simulations. After clicking
“See It”, “Try it” or “Know It”, nothing would happen.
Turns out the reason why not was because I’d built the package with the wrong version of
SCORM. When publishing (and SCORM version is set when publishing, not as part of the UPK
options), UPK defaults to SCORM version 1.3 (2004).
However our LMS is only at 1.2. So the reason why the simulations were not loaded was simply
that the package and LMS could not communicate over progress/status.
Changing the SCORM version to 1.2 in UPK, and republishing the LMS package, resolved the
issue. The package now presents, completes and tracks perfectly.
[Annoyingly, this setting is not saved so you have to remember to reset it each time you publish.
Would be better as a global option – you listening Oracle?]
