Publishing directly from your PC

If you want to publish an object directly from your PC, it must already be formatted in SCORM 1.2 format.

You can also publish files that are not part of a content package to the LOR. These files become assets once you publish them. SCORM compliance is not required for publishing assets.

Note  The LOR does not support publishing SCORM 2004 content directly from your PC.

Formatting metadata for publishing packages

An object’s metadata can be located under any applicable element in the manifest file, depending on the type of object and whether the object is a sub-element in the file. Manifest- and organization-level metadata is applied to the highest level object in the package. Metadata for modules can also appear at the item level, and metadata for topics or assets can appear at the item- or resource-level. A package is identified as a module if there is only one child <item> tag underneath the <organization> tag, and that <item> tag has at least one child <item> tag of its own.

Where object metadata can appear

If metadata for a single object is found under multiple elements, the LOR uses the following order of precedence: <manifest>, <organization>, <item>, <resource>.

For example, if you are uploading a content package consisting of a module with three topics, and there is metadata under the <manifest> element and under the highest <item> element, both are applicable to the module. The upload utility takes the metadata from the <manifest> element and discards the metadata from the <item> element. Say that one of the topics in the package has metadata under its <item> element and also under the associated <resource> element. In this case the LOR uses the metadata for the <item> element, while the metadata for the <resource> element is discarded.

Publish directly to the LOR

1. Do one of the following:
   • Click LOR in the navbar, then Publish in the top tool menu.
   • Click Publish to LOR in My Admin Tools on My Home.
   • Click Publish in the LOR widget.
2. Select a Destination Repository from the drop-down list.
3. Click Browse and locate the package or file that you want to publish to the LOR.
4. If you want to hide the learning object/asset, select Hide learning object. You can change this option once the object/asset is published to the LOR. Only you and users with sufficient permission can view hidden learning objects and assets.
5. If you want to make the object available publicly to users without an ID and password to Learning Environment, select the Make Learning Object publicly available for viewing check box. Only you and users with sufficient permission can view hidden learning objects and assets.
6. If you want, click Set publish process to run in the background to run the publish process in the background. Use this for large files or packages. You can check the publishing job's status later.
7. Select the Associate Creative Commons license with Learning Object check box if you want to set a license for the object.

   Creative Commons licensing enables you to retain copyright on your work while allowing different degrees of reuse to other users. You can reserve all rights to your work, some rights, or release it to the public domain. For more information go to http://creativecommons.org/.

   If you associate a license with your learning object, choose what restrictions you want to place on it.

8. Click Browse and locate the package or file that you want to publish to the LOR.
9. Click Publish.
10. If you want to add metadata to an asset, which Desire2Learn recommends, click the  metadata icon, complete the fields in the pop-up and click Save.

    Note  Associating a creative commons license automatically  populates the metadata rights fields with this information.

11. Click Continue.

See also

• About Metadata