dfb80acc11
NOTE: This will require a forced backfill of course outlines to update the course content data in learning_sequences: python manage.py cms backfill_course_outlines --force Without this backfill, the learning_sequences API will continue to serve stale content data that has no user partition group data. It won't cause errors, but it won't do the exclusions properly. Commit summary: * Created EnrollmentTrackPartitionGroupsOutlineProcessor to process the enrollment_track User Partition Group, allowing Sequences and Sections to be removed based on their group_access settings. * Added user_partition_groups attribute to CourseLearningSequenceData and CourseSectionData in learning_sequences/data.py, along with backing model data. * get_outline_from_modulestore now extracts group_access settings from Sections and Sequences. It also bubbles up group_access settings from Units, meaning that if a Sequence with no group_access setting has Units that are all set to show only to the Verified enrollment track, then the Sequence will only show to the Verified enrollment track. This commit adds model-level support for all user partition groups by capturing all the content group associations (group_access), but it only implements the code checks for the enrollment track partition. It's not clear that we want to generalize, since there's only one other partition type (A/B testing) that is applicable at the outline level. It's important to note that there is no way to set the group_access for a Section or Sequence in Studio today. It's only possible by direct editing of the OLX for import. That being said, the block structures framework supports applying course groups at this level, and this commit moves learning_sequences closer to feature parity. The bubbling up from Units to the parent Sequence was done to mitigate confusion when a Sequence is entirely composed of Units that are not visible to the user because of content group restrictions. It's not clear whether this is something we want to do in the long term, since it would simplify the code to always specify group_access at the Sequence level. This first pass is done partially to collect better data about places in our courses where this kind of usage is already happening. Most of the EnrollmentTrackPartitionGroupsOutlineProcessor code and its tests were written by @schenedx.
Open edX -------- This is the root package for Open edX. The intent is that all importable code from Open edX will eventually live here, including the code in the lms, cms, and common directories. If you're adding a new Django app, place it in core/djangoapps. If you're adding utilities that require Django, place them in core/djangolib. If you're adding code that defines no Django models or views of its own but is widely useful, put it in core/lib. Note: All new code should be created in this package, and the legacy code will be moved here gradually. For now the code is not structured like this, and hence legacy code will continue to live in a number of different packages.