Captivate enables you to create a Package Interchange File (PIF), which the SCORM guidelines recommend but do not require. A PIF file allows for smooth movement of files between systems. This means that to avoid a Tower of Babel scenario of conflicting languages and standards, the contents of the file must be packaged in a similar manner. The standard used is PIF. At the root of the package, there must be an XML file called imsmanifest.xml, which is the manifest file created when you set the manifest options earlier in this chapter. This file, the manifest, describes the learning materials that make up the eLearning application. To create a PIF file
If you open the directory, you will see the ZIP file and a folder named SCORM_support. Inside the ZIP file (Figure 11.45) are the SWF file, the HTML file, and the SCORM manifest file, imsmanifest.xml. Figure 11.45. The published file. The files in the ZIP file, shown below the line, should all be placed in the SCORM_support folder.Overall, the SCORM_support files/folder are required to facilitate two-way SCORM communication. These files (the ones under the line in Figure 11.45), must be available when playing back a file after publishing to the SCORM standard. The files prefaced by SCORM_support should be placed in the SCORM_support folder. You should be able to open the SCORM_support.js file in Notepad or another text editor unless there is some corruption in the publish process. |