Course data model
A course is a distributed series of items across the network. Because of this, it’s actually tapping into a replicated model of different system types. There’s the CIS representation of a course / section, an Authority representation of course / section, and a Service representation. It’s different in each type of system due to the complexity of the data that needs modeled but utilizes machine names and UUIDs in order to keep the data model in tact.
Example of the data model utilized by the network
This visual shows how a course title being updated in one place would then be propagated across all other systems in the network.
This is a similar process for how user accounts will be propagated across as the section connotation exists everywhere it’s needed.
Implementing the data model in new systems
If an authority system, Courses as nodes called cis_course, will have the type managed primarily by the cis_course_authority module/feature. If you want to reference the course from other content in your system_and retain the course context_then you’ll want to name your entity reference
Doing so allows the function
_cis_connector_course_context()to discover the content correctly and inform the rest of the system (via rewriting of addresses and other functions that call for context) that you are indeed still in the same course context.