...
In the <metadata> tag there will be a <schemaversion> which should be 1.2. If the version is incorrect, the client must re-package the course using the correct version:
Old Manifest Mapping
When the SCORM course is imported into the LMS, a number of files get generated including a manifest (SCOManifest.js). This file is used to map the SCO Id, and other information desired (Currently supports: mastery score, time limit, and launch data. See: SCORM Data Model).
...
Note this does support multiple entries for backwards compatibility. E.g.:
Code Block | ||
---|---|---|
| ||
var myAPI = getAPIHandle();
if (!myAPI) { console.log("Mapping: Could not find API"); }
else{ console.log("APIFOUND");
myAPI.SCOIDMapping = {};
myAPI.SCOManifestMapping = {};
myAPI.SCOIDMapping["index_lms.html"] = "__6LMdt51ovdV_course_id_RES";
myAPI.SCOManifestMapping["index_lms.html"] = {"id":"__6LMdt51ovdV_course_id_RES","timelimitaction":"ContinueNoMessage"};
myAPI.SCOIDMapping["index_lms_html5.html"] = "__6LMdt51ovdV_course_id_RES";
myAPI.SCOManifestMapping["index_lms_html5.html"] = {"id":"__6LMdt51ovdV_course_id_RES","timelimitaction":"ContinueNoMessage"};
} |
New Manifest Mapping
As of version 4.0.x a new manifest mapping has been created and is used on ImportScorm. This is to prevent manual mapping of the multiple entry points (e.g. index_lms_html5.html) in the SCOManifest.js after import. The new SCOManifest.js should still have a value mapped after import (lines 6 and 7):
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
var myAPI = getAPIHandle(); if (!myAPI) { console.log("Mapping: Could not find API"); } else{ console.log("APIFOUND"); myAPI.SCOIDMapping = {}; myAPI.SCOManifestMapping = {}; myAPI.SCOIdFromManifest = '__6g7FD8imvYA_course_id_RES'; myAPI.SCODataFromManifest = {"id":"__6g7FD8imvYA_course_id_RES","timelimitaction":"ContinueNoMessage"}; } |
...
We have seen an error where invalid characters in the SCO Resource Id have caused our 3rd party extractor to silently ignore the resource/course and not give any error (This is fixed as in 4.3.0
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Note: the only confirmed invalid character is the colon ':' as of this writing. However, other reserved Reserved html characters should be viewed with suspicion. To To fix this issue, remove the offending characters, and re-zip the packaged files with a new name, and re-import the course to the LMS.
...