Feature/user levels upstream update content fields #245
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.
This PR has changes to two models adding the new fields content_area and topic_tags:
1.
dim_student_script_level_activity
Changes:
a. Include content_area and topic_tags
b. Filtered the CTE for dim_course_structure to only pull student-facing content: content_area like 'curriculum%' or content_area in ('hoc')
c. Change the left join from user_levels to course_structure to an inner join to actually limit the content of the model to student-facing one. This was also causing a significant number of records with nulls in the fields labeling the curriculum (course_name, script_name, etc.).
2.
dim_self_paced_pd_activity
Changes:
a. Include content_area and topic_tags
Validation
The following code was used to validate that the changes worked and there were no changes to upstream models
1.
dim_student_script_level_activity
a. No impact on
dim_user_course_activity
: difference in student counts by course and school year between prod and test schema is -1 for a CSF student in 2022-23.b. No impact on
dim_active_students
: difference in student counts by school year between prod and test schema is nullc. Impact on
dim_student_script_level_activity
: difference in student counts by course and school year between prod and test schema is nulld. Data including
content_area
andtopic_tags
displays is as expected:e. No data with null course_name:
**2. dim_self_paced_pd_activity **
a. difference in course counts between prod and test schema: difference is null
b. Data including
content_area
andtopic_tags
displays is as expected:Links
Jira ticket(s): DATAOPS-1084