MAU 2 - Add Monthly Active Enrollment Model #446
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Adds new model, figures.models.MonehtlyActiveEnrollment
* This model exists to capture user activity in a course in a month
* This forms a foundation from which per-user or per-course or
per-site monthly active users can be derived
* Added model unit tests and updated test infra for support
Baseline Course MAU model and test
* Add admin interface for MonthlyActiveEnrollment and update admin test
johnbaldwin
requested review from
OmarIthawi,
melvinsoft,
shadinaif,
estherjsuh and
bryanlandia
as code owners
OmarIthawi
approved these changes
Mar 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's this PR about?
This is the first part of revamping how Figures captures monthly active users. At the core of this is a new model,
MonthlyActiveEnrollmentthat says if a given user was active in a course for a given month, a unique user + course aka 'enrollment', so we simply call it 'monthly active enrollment'. This model then forms a foundation to quickly query for such things asWe're generally following this design: https://appsembler.atlassian.net/wiki/spaces/RT/pages/350552808
What's in this PR?
What's next?
After this PR is merged, the models won't update right away. We're adding Django signals to trigger the check and creating of a
MonthlyActiveEnrollmentif it doesn't exist. The signals will be configurable, at least at the deployment level viaserver-varswith the option to toggle on/off at the site level