When publishing to SCORM the Publish Wizard includes an additional dialog (or two if you want to set your own identifiers in the manifest.
The first allows you to set what part of the SCORM packaging process you want Opus to undertake.
You first need to choose the SCORM version you are supporting. This should have already been decided as it needs to be consistent with the data models you have used to get and set values between the LMS and your publication.
Most LMS support SCORM v1.2 and most of the ones which support v2004 will also support v1.2 so supporting the earlier version is probably the best option if you are not sure where your material is being used or if you do not need some of the extended features of 2004.
There are then three options to select which refer to how you want your publication packaged.
If your publication is to be uploaded to an LMS as a complete item (as in most cases) then you will need to wrap it in a package. This SCORM content package is basically a .zip file containing all the required elements of your publication together with an index or catalogue (called the manifest). The manifest lists the resources in the package, gives everything individual alphanumeric IDs and titles which the LMS can use to identify and display the content. It also includes a set of additional documents required by the SCORM specification which define parts of the specification. These are called the "controlling documents" and set lower level parts of the specification such as naming conventions used for IDs. You do not need to be concerned with the controlling documents unless you need to the naming convention for creating your own IDs.
This creates the manifest or catalogue of your lesson. It is an XML file listing the resources in the lesson and the way they are organised. It is mandatory for any lesson being uploaded to an LMS so unless your publication will be included as part of group of publications with a manifest of its own then this option is required.
This creates the .zip file of all the elements required for your SCORM content. Primarily this includes the publication and any associated files together with the manifest file. It also includes some additional documents required by the SCORM specifications.
This .zip file is what you will import into the LMS so unless your publication will be included as part of group of publications with a manifest of its own then this option is required.
However, during testing you may wish to leave this option unchecked so that you can run test the finished publication without having to unzip it all.
This option will ask Opus to generate SCORM-compliant IDs and titles for the various elements in the manifest. These names are used in various places in the manifest to identify the elements and some may be used by the LMS as a default name for the lesson when it is imported.
If you deselect this option you will then be presented with an additional dialog (illustrated below) which allows you to create your own ID’s and Titles. The SCORM manifest requires these elements so they need to be generated one way or another.
If you do not choose to let Opus generate the manifest Ids then a second dialog appears allowing you to set the relevant elements yourself.
Your publication may reference some external files such as a PDF manual or a custom HTML video player or perhaps a separate SWF file. In SCORM publications these associated documents must either be provided as weblinks and linked to within the publication using the Launch action, or provided with the publication and included in the SCORM Manifest.
The Add Files dialog allows you to browse for these files and include them both in the Manifest and the zipped package.
Once you click Next on this dialog the Publishing process continues as with a standard publication.
Once the publication has been created Opus and depending on the options you selected in the first dialog, Opus will automatically create the additional files and the manifest file and combine everything into a zip file.
Note:
If the final output of the SCORM publishing process is the zip "content package" then the Test button will not be active. You will need to unzip the final file and manually run the HTML to test the publication.