After some more thought, we've decided that a SCORM package should be associated with a type of lesson rather than a type of resource. So now, when you try to add a new lesson, you get the choice between a lesson made of HTML sections or a lesson made from a SCORM package.
When you upload the package, we parse it, store it, and then create a lesson whose content is the SCORM package. The default name and description of the lesson are set from the SCORM manifest.
When you execute the SCORM content, we dynamically create a SCORM assignment if the SCORM package is one that tracks scores.
Getting the mapping between a SCORM package and the concepts in the current EDU 2.0 system is very important, and I think this shift from thinking of a SCORM package as a resource to thinking of it as a lesson with an optional assignment is a big improvement.
Comments