|
|
|
|
|
|
|
SCORM Courseware Packaging1. Aggregate all resources into a content package: To have a SCORM compliant content package, there must be a "master" imsmanifest.xml file that contains references to all resources of your content. Should this file be absent, the content is not SCORM compliant and will not perform in a SCORM compliant Learning Management System (LMS). The aggregation process groups all of the content resources into one folder and creates the "master" imsmanifest.xml file. To see an example of a SCORM 1.2 imsmanifest.xml file, click here (a SCORM 2004 manifest example is under development). This can be done manually, or by using a tool supplied by the authoring vendor. 2. Add Army meta-data: To meet Army requirements, there must be SCORM and Army meta-data; refer to Business Rules and Best Practices. 3. Readying the package: The content package must be made into a package interchange file (PIF) before being transferred. The PIF file allows for ease of transfer, storage, and loading onto the ALMS. Creation of this PIF follows SCORM guidelines; to find out how, click here. |
|
|
AKO |
Army Home |
ATHD Help |
CAC |
TRADOC Home |
|
|
| Address comments, suggestions to atsc.technical.webmaster@conus.army.mil | |||||||
Page last updated: 9/9/2009 2:29:44 PM