Learning objects are database objects that represent the physical content residing on a content server. Learning objects facilitate the management and delivery of online content. The Content page displays the content hierarchy comprising folders, learning objects, and tests. From here you can create and manage your learning objects.
You can either manually create learning objects or import them into your application from another application or learning management system. You can also copy learning objects from one location to another within your content hierarchy. The import and export utilities in OLM enable the transfer of learning objects, content hierarchies, and tests across applications. For details see: Content Import and Export
A learning object identifies the physical content with which the object is associated. Some learning object properties and their definitions are listed in the table below:
| Property | Definition |
| Duration | The time taken to play the content represented by the learning object |
| Audience | The target learning audience |
| Hardware Software Requirements | System requirements required to run the content |
| Mastery Score | The score that the learner should attain to master the content represented by the learning object |
| Mime Type | The format of the content; this information is used when exporting learning object using the IMS specification |
| Author | The author or publisher of the content |
| Catalog | The entry specified in the catalog |
| Catalog Number | Catalog ID or number for use within an external cataloging system |
| Version | The ID or number that identifies the content version |
| Open in New Window | Opens the player incompatible content in a new window from within the player.
Note: This option is different from the Open in New Window check box on the Offering Properties page. For more information, see the Player Preferences section in Offerings |
You must define the content properties to associate a learning object with the physical content. If your content is located on an external content server that is not managed by OLM, select URL Access in the Type field and specify the URL to access the content. Alternatively, if an OLM content server hosts your content, select Content Server Access and provide the content location details. To identify the content location, you must specify the content server name, the directory where the content resides, and the file name. To know about setting up a content server, see: Content Servers
You can also associate a learning object with a recorded web conference, by specifying the recorded conference details such as conference server and the meeting ID in the Content section. You use this association to deliver online asynchronous classes as recorded web conferences. For details see: Web Conferences
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 you can associate a file on the OWCC content server with OLM learning objects. This feature can be used where the file that must be associated with a learning object is already stored in the OWCC server. In such cases, when you specify the starting file on the OWCC server, the connection is made. When you create or update a learning object, the OWCC server associated with OLM is visible in the Content Server field. Click the Preview icon next to the Type field to check whether the correct file is selected. Access the OWCC server. Select the appropriate directory in the OWCC server and the initial file.
A player prerequisite is a learning object that a learner must complete before beginning or continuing a sequence of learning. For example, learners may need to complete an introductory sequence of learning before attempting the advanced material. You can make the introductory learning object a player prerequisite to the advanced learning object. You can assign multiple prerequisites to a learning object, and learners must complete all prerequisites before they can launch the learning object.
By default, all learning objects are initially unpublished. You publish learning objects to visually indicate that the content is available, and to enable Catalog Administrators to assign the learning object to an offering. When you publish a learning object that contains nested objects, the system publishes all learning objects and tests currently contained within the parent object. Learners cannot see a nested object that remains unpublished. You unpublish a learning object when you need to make changes, and do not want learners to access the object while the changes are being made.