Shared Lessons

This article discusses the concept of a Shared Lesson which refers to a Learning Object that is referenced between two, or more Online Courses. A Shared Lesson is created when the Use Existing option is selected while creating a Learning Object to use an existing Third Party Lesson (such as SCORM).

Lessons Report

The Lessons Report contains information related to Lessons in your Portal. It will list Third Party Lessons that can become Shared Lessons or are already.

For more information about the Lessons Report review the following article:

• The Lessons Report

Actions

The Actions presented when a Lesson from the report is selected depends on whether or not the selected item is a Shared Lesson or not. If the selected item is not a Shared Lesson only the Deselect Action will appear on the right-hand side of the LMS.

If the selected item is a Shared Lesson three Actions will appear:

Each action is defined in this table:

Action	Description
View Courses	View all Courses which use this Lesson. The Courses Report will be opened with a Filter that targets the selected Lesson.
Replace Lesson	Open the Replace Lesson tool. Use this tool to begin the workflow to update/replace the Shared Lesson content.
Deselect	The selected item from the Lessons Report is no longer selected.

Replacing a Shared Lesson

A Shared Lesson can be replaced using the Replace Lesson tool, this way instead of manually making multiple changes, you can make one singular update.

Follow these steps to Replace a Shared Lesson:

1. Access the Admin Experience.
2. Navigate to the Lessons Report.
   
    
3. Select the Shared Lesson you want to Replace and then click Replace Lesson from the right-hand side. The Replace Lesson tool will open.
   
    
4. From the Replace Lesson tool, select Choose File.
   
    
5. Navigate the File Browser to upload the new file that is replacing this Shared Lesson.
6. Select Continue. The Replace Lesson warning will appear.
   
    
7. Select Publish from the Replace Lesson warning.
   
    
8. A flag will appear in the top-right corner of the screen confirming the replacement has succeeded.
   

Shared Lesson Restrictions

When referencing a Shared Lesson it is important to keep in mind the following restrictions:

• A Lesson can't be shared across the private/public boundary.
  • If the Lesson is private, when it is shared it remains private, requiring an authenticated User with an Enrollment in the Course to access.
  • If the Lesson is public, when it is shared it remains public and could be accessed from the public dashboard, or by anyone who happens to have the direct link to the content.
• Create LI Lessons are not supported currently.
• When using Replace Lesson, the two files must be the same type.
  • Scorm 1.2 to Scorm 1.2, AICC to AICC, etc.
• When selecting a Lesson to reuse the Admin will see all Lessons in all Courses that they have access to. If the Lesson is also contained in a Course that isn't visible due to Locked Department or being otherwise outside their visibility, the Lesson is still available for reuse.
  • The same convention exists for replacing a Lesson. Even if the Lesson is being used in a Course the Admin can't see, the content will change for that Course too.
• The same way as having Modify but not View Courses, an Admin role could be created that has Modify but not View Lesson. This means the Admin wont see any Lessons on the Lessons Report to be able to modify them.
• For Shared Lessons we show the most recent name given to the Lesson on any Course.
• When a Lesson is reused/shared for the first time, there is a conversion process and some delay is expected before the Lesson Report updates to reflect the new shared state.

Duplicate Courses & Shared Lessons

When Duplicating Courses, the system handles Lessons differently based on their sharing status:

• Standard Lessons: Non-shared Lessons are fully duplicated with unique identifiers, creating independent copies within the new Course.
• Shared Lessons: Lessons that have been shared across multiple Courses maintain their shared status and reference the same content library. These Lessons are not duplicated but continue to reference the original shared resource.

Once a Lesson becomes shared (identifiable by its Last Shared Date), it permanently retains its shared status regardless of how many Courses utilize it.

This approach ensures content consistency across Courses while optimizing storage efficiency. The system creates new copies of Course specific content while preserving shared resources that multiple Courses depend upon.

This design maintains data integrity and prevents unnecessary duplication.