You can import and export learning objects using IMS, SCORM (SCORM 1.2 and SCORM 2004 Edition 4), or AICC (import only) specifications. If your application has a content server set up, you can use the SCORM specification to import the content files along with the learning objects.
Note: You cannot import or export values in descriptive flexfields. The import and export utilities ignore descriptive flexfields.
To import learning objects, you use XML files stored in a zip or jar file, that adhere to the IMS, SCORM, or AICC specifications. You can specify during import if the application should create new objects or update existing learning objects. You can use one of the following specifications for importing learning objects:
Import Content and Assessment Hierarchy: Imports all learning objects and tests contained within the selected hierarchy or folder
Note: Use this option for importing into an OLM application only.
SCORM 1.2 or SCORM 2004 Content Aggregation: Imports both learning objects and content files. Ensure that you have access to an OLM content server before attempting to load content files using this option.
AICC Metadata: Imports an AICC specification file
OLM provides default content tracking at the learning object level, for example the application tracks the usage, time spent, and completion status for a learning object. AICC content contains CMI objectives that enable greater level of content tracking such as resetting the topic completion status based on logical conditions defined within the content. When importing learning objects using the AICC specification, you also can import the CMI objectives contained in the learning object. After importing, you can view the CMI objectives for the learning object and verify that the content was correctly imported.
If integration is set up between OLM and Oracle WebCenter Content (OWCC) to use OWCC, formerly Oracle Universal Content Management, as a content server for OLM content, then an administrator has the option to select the OWCC server to store the content that is imported.
See: Importing Objects
During import, the application creates learning objects from the information available in the XML files. Imported learning objects appear in the content hierarchy, just as any other learning object that you create directly in the application. The XML file must include the required information to create a learning object, specifically Identifier and Title. Your XML file can also include the Starting URL, Description, Audience, and other optional attributes for a learning object.
The application updates existing learning objects during import, by matching the identifier values (External ID and the External Src tags) found in the XML import file. The "Attempt to Update the Matching Object" box specifies whether the import always creates a new object, or first attempts to update an existing object. To ensure that the import utility always creates a new object, even when the identifier is the same, deselect this box. In this case, the import process creates duplicate objects.
You can export an individual learning object, a folder comprising learning objects or a hierarchy of learning objects. The Export function supports the same specifications as the Import function with the exception of AICC, which is valid only for import. When you export learning objects, the utility creates and stores the information in XML files, zipped in a zip or jar file. If your application has a content server, you can also export the content files associated with the learning objects that are exported. The "Download physical content files with metadata" box is visible on the Export: Specifications page only if you have a content server set up.