Notes on Content Groups, User Partitions, and Teams
For every X, a learner belongs to a one Y
Context | X | Y |
---|---|---|
Studio | Experiment Group Configuration
| Experiment Group
|
Studio | Content Group Configuration
| Content Group
|
LMS | (Course Feature)
| Group
|
course_groups Code (the generic framework that powers all the of the above) |
|
|
LMS: Teams (we want to connect this to Studio’s Groups) | Team Group
| Team
|
teams Code (we want to connect this to course_groups) |
|
|
Known User Partitions
These are the user partitions built into edx-platform, saved onto the user_partitions
CourseBlock dictionary setting. Each partition is scoped to a course--a learners' partition<->group mappings in one course are not affected by their mappings in other courses (...yet).
0-49: Unassigned
50: Enrollment Track Partition (if enabled)
51: Content Type Gating Partition (if enabled)
52-99: Unassigned (should Team Set Partitions go here?)
100-Infinity: These partitions are randomly assigned when first used (avoiding conflicts with existing dynamic partitions) and then saved to the course settings. The partitions include:
Content Group Configuration (exactly 1)
Experiment Group Configurations (potentially many)
… (should Team Set Partitions go here?)