1.0.67

UDP Marts

Week Start and End Date Fields and Replacing Postgres Calls

Version	1.0.67
Release Date	August 1, 2024

Key Features

Week Start and End Date Fields

DSS has added two new fields, week_start_date and week_end_date, to the Student Activity Score, Taskforce, and Interaction Sessions marts. These are additive changes, and no existing queries will break. No existing fields have been renamed.

week_start_date and week_end_date define the start date and end date for the current week in the academic term. These new fields allow for validation of the accuracy of the week calculations, as well as allow for analytics based on date instead of week.

Marts Affected

• mart_course_offering.interaction_sessions

• mart_taskforce.level1_aggregated

• mart_taskforce.level2_aggregated

• mart_taskforce.level2_course_week_files

• mart_taskforce.level2_course_week_metrics

• mart_taskforce.level2_course_week_tools

• mart_taskforce.level2_course_weekly_distribution_summary

• mart_student_activity_score.student_course_metrics

• mart_student_activity_score.student_course_section_metrics

• mart_student_activity_score.course_final

• mart_student_activity_score.course_section_final

• mart_student_activity_score.final

Replacing Postgres Calls

Originally, the fields in the mart_helper.context tables were populated from the Postgres database entity and keymap schemas. This was achieved using EXTERNAL_QUERY calls to the Postgres database in BigQuery. We have replaced these calls with SQL that pulls directly from the BigQuery context_store_entity and context_store_keymap datasets. This change improves the performance of the code, reducing the amount of time needed to run the marts. This does not affect the schemas of any marts, and no existing queries will break.