The Basics of Course Relationships

Learn about the Course Relationship feature and the various configurations available to customize your relationship to fit your specific needs.

 

What is Course Relationships?

Course relationships are most often used for annual conferences involving multiple sessions or learning tracks that involve multiple courses. At its core, Course relationships are linked courses in a hierarchical tree: Courses in a course relationship have at least one parent course and one or more child courses. View the example image below.

Add-on Feature

Enabling the Course Relationship feature requires activation by a member of the EthosCE support staff before you can utilize it. Reach out to your account manager for further details on how to enable this feature on your website.

Support Services

While you are free to create multi-leveled relationships within the system, the EthosCE Support Staff can only assist with two-level relationships unless your support agreement includes advanced relationships. Our recommendation is to use only two-level relationships (parent/child). View the example image below.

Additional Information on Course Relationships

Putting courses into a course relationship allows for the creation of more complex learning activities such as curricula, conferences, multi-day-instructor-led training, etc.

Once grouped, additional features for those activities become available. View below: Configure Course Relationships with Various Requirments that Fit Your Unique Needs.


Examine the image below for an illustration showing a parent course and three linked child courses.

Screen Shot 2024-02-09 at 3.55.04 PM.png

Configure Course Relationships with Various Requirments that Fit Your Unique Needs.

Because of the many features available, make sure to fully test courses before publishing them to learners.

Course Relationships are a powerful tool for creating complex and robust courses. Such relationships can cater to various requirements, including:

 

  • Allow for a single certificate to be awarded after completing the specified required child activities.

  • Allow each child activity to have its own certificate.

  • If using a single certificate on the parent, enforce that the learner must complete the child’s activities in order or allow the learners to complete them in arbitrary order.

  • Allow users to purchase or enroll in only all the child activities together, or only individually, or provide an option for either purchasing together or individually.

  • Allow users to receive a discount for purchasing the entire group.

  • Allow users to purchase a parent and receive access to all existing and future child courses.

  • Allow users to claim immediate credit.

  • Allow for credit to be aggregated to the parent from child courses.

  • Allow users to only enroll in the specified number of children and no more. For example, to prevent learners from enrolling in concurrent activities.