SCORM standard courseware Creation

Make the courseware meet the SCORM standard and contain two aspects: 1. the courseware can be correctly imported to the platform; 2. the courseware can be successfully communicated with the platform.
I. SCORM courseware import: supports SCORM standard platforms to read "imsmanifest. XML file to obtain the course title, course structure, and course address. The "Manifest" node is the root node of the file, and there are two subnodes "organizations" and "Resources" under the root node ", the information in "organizations" describes the course structure, and "Resources" contains the storage location and type of the resources used by the course.
It is important to note the following points:
1. The "identifier" attribute of each node should be unique;
2. There can be multiple "Organization" nodes under the "organizations" node. The "default" attribute of "organizations" points to a "Organization" to decide which organization structure to use;
3. The "item" node under "Organization" can be nested to realize the hierarchical relationship of course chapters;
4. The value of the "identifierref" attribute of the "item" node is the value of the "identifier" attribute of a "resource" node, so that a chapter can correspond to the course resources;
5. The text on the title node is the text displayed on the platform of the course and chapter;
6. The "href" attribute of the "resource" node is the storage location of the course resources.
"Imsmanifest. the XML file can be generated by tools. Therefore, the SCORM standard courseware does not encounter any problems in terms of import, but different platforms do not have the same import methods. Some platforms simply import "imsmanifest. XML "is a file. Some platforms include the course file and" imsmanifest. the XML file is compressed into a zip package for the whole import. Apart from inconsistent import methods, the "imsmanifest. the encoding used by the XML file is also worth noting, as long as it can be correctly read by the platform.

Ii. SCORM courseware and platform communication: Any course that can be tracked should at least submit the status of each chapter of the course to the platform ("not accessed", "not completed", "completed "), score, and current position. SCORM courseware submits the above information to the platform through a set of standard functions. The function name of this set of functions is part of the standard, and the platform is unified, the courseware only needs to be called. The SCORM standard Creator also provides a set of script files ("apiwrapper. JS and scofunctions. JS "), the introduction of these files into the course can more easily communicate with the Platform:
1. "apiwrapper. js" directly calls the APIS provided by the platform to convert platform functions into local functions.
2. "scofunctions. js" calls the functions in "apiwrapper. js" and combines a single function into a function that can be directly called to complete a task.
After the above two files are introduced, the course directly calls "apiwrapper. the "loadpage ()" In JS "can complete the course initialization and call" docontinue ('completed') "to complete the course learning in this chapter,
Call "unloadpage ()" to cancel the course.
To implement complex interaction with the platform, call "scofunctions. "dolmsgetvalue (name)" and "dolmssetvalue (name, value)" In JS ", where" name "is a set of text defined by SCORM, for specific values, see the SCORM standard documentation.