Level 2 Aggregated
The mart_taskforce.level2_aggregated mart aggregates data about a student’s performance and activities in a course on a weekly basis relative to average course and peer behaviors. This table exists alongside mart_taskforce.level2_course_weekly_distribution_summary
BQ Prod Dataset Locations
mart_taskforce
Interactive Mart Dependency Diagram
The following visualization shows the construction of this data mart defined in the UDP marts repository. More information on the repository and diagram can be found on this marts page.
Schema
mart/taskforce/level2_aggregated
Field Structure and Subcategories
This level 2 table has many fields, so we’ve grouped them together in the following subcategories
Assignments
Submissions
Assignments
Missing Assignments
Late Submissions
Submission Time Buffer
Published Scores
Discussions
Discussion Threads
Discussion Entries
Learning Environment Activity
View days
Sessions
Tool Launches
File Views
Dependencies
The only dependency for this mart is the mart_taskforce.level1_aggregated. All calculations and fields are based on that mart, and there are no direct dependencies to the UDP itself. As long as the mart_taskforce.level1_aggregated is successfully created, this mart can also be created.
Assignment Weight Groupings
Many fields have names that include tiny, small, medium, large, and major. These classifications are based on the group_weight field in the ‘learner_activity_group’ entity. The cases are as follows:
If the group_weight is null or equal to 0%, the submission is ‘unweighted’.
If the group_weight is less than or equal to 2%, the submission is ‘tiny’.
If the group_weight is greater than 2% and less than or equal to 5%, the submission is ‘small’.
If the group_weight is greater than 5% and less than or equal to 10%, the submission is ‘medium’.
If the group_weight is greater than 10% and less than or equal to 25%, the submission is ‘large’.
If the group_weight is greater than 25%, the submission is ‘major’.
If the group_weight is not null and greater than 0%, the submission is 'weighted'.
These assignment weight groupings are consistent with the groupings for the Level 1 mart.
Z-Score Fields
The majority of the schema for mart_taskforce.level2_aggregated are z-score fields based on the distribution of corresponding fields per-course, per-week in mart_taskforce.level1_aggregated. The corresponding table mart_taskforce.level2_course_weekly_distribution_summary surfaces the averages and standard deviations (per-course, per-week) needed to calculate the z-scores for this table. We use the standard normalization formula to compute the z-scores.
Assignments
Number of Submissions
Fields
num_tiny_submissions_z
num_small_submissions_z
num_medium_submissions_z
num_large_submissions_z
num_major_submissions_z
num_unweighted_submissions_z
num_weighted_submissions_z
num_submissions_without_due_date_z
num_submissions_with_due_date_z
num_submissions_z
Description
These fields present the Z-scores for the number of submissions by a student in a course for each week in the term. More detailed descriptions of the original submission fields exist in the documentation for mart_taskforce.level1_aggregated.
Number of Assignments
Fields
num_tiny_assignments_z
num_small_assignments_z
num_medium_assignments_z
num_large_assignments_z
num_major_assignments_z
num_unweighted_assignments_z
num_weighted_assignments_z
num_assignments_z_without_due_date
num_assignments_z_with_due_date
num_assignments_z
Description
These fields present Z-scores for the number of assignments for a student in a course for each week in the term. The more detailed descriptions of the original assignment fields can be found in the documentation for mart_taskforce.level1_aggregated.
Number of Missing Submissions
Fields
num_tiny_missing_submissions_z
num_small_missing_submissions_z
num_medium_missing_submissions_z
num_large_missing_submissions_z
num_major_missing_submissions_z
num_unweighted_missing_submissions_z
num_weighted_missing_submissions_z
num_missing_submissions_z
Description
These fields present Z-scores for the number of missing student submissions in a course for each week in the term. The definitions of the original missing submissions fields exist in the documentation for mart_taskforce.level1_aggregated.
Number of Late Submissions
Fields
num_tiny_late_submissions_z
num_small_late_submissions_z
num_medium_late_submissions_z
num_large_late_submissions_z
num_major_late_submissions_z
num_unweighted_late_submissions_z
num_weighted_late_submissions_z
num_late_submissions_z
Description
These fields present the Z-scores for the number of late submissions by a student in a course for each week in the term. The definitions of the original late submissions fields exist in the documentation for mart_taskforce.level1_aggregated.
Average Time Buffer in Hours
Fields
avg_time_buffer_hrs_tiny_z
avg_time_buffer_hrs_small_z
avg_time_buffer_hrs_medium_z
avg_time_buffer_hrs_large_z
avg_time_buffer_hrs_major_z
avg_time_buffer_hrs_unweighted_z
avg_time_buffer_hrs_weighted_z
avg_time_buffer_hrs_z
Description
These fields present the Z-scores for the average time buffer in hours for submissions by a student in a course for each week in the term. The definitions of the original time buffer fields exist in the documentation for mart_taskforce.level1_aggregated.
Average Published Score Percentage
Fields
avg_published_score_pct_tiny_z
avg_published_score_pct_small_z
avg_published_score_pct_medium_z
avg_published_score_pct_large_z
avg_published_score_pct_major_z
avg_score_pct_unweighted_z
avg_published_score_pct_weighted_z
avg_published_score_pct_without_due_date_z
avg_published_score_pct_with_due_date_z
avg_published_score_z
Description
These fields show the Z-scores for the average published score percentage of submissions by a student in a course for each week in the term. The description of the average published score fields exist in the documentation for mart_taskforce.level1_aggregated.
Discussions
Discussion Entry Counts
Fields
discussion_entry_count _z
discussion_post_count_z
discussion_reply_count_z
Description
These fields present the Z-scores for the number of discussion entries posted by a student in a course for each week in the term. The definitions of the original discussion entry count fields exist in the documentation for mart_taskforce.level1_aggregated.
Discussion Counts
Fields
discussion_count_z
assignment_discussion_count_z
threaded_discussion_count_z
side_comment_discussion_count_z
Description
These fields present the Z-scores for the number of discussions a student has interacted with in a course for each week in the term. The discussion count fields used to compute these Z-scores are defined in the documentation for mart_taskforce.level1_aggregated.
Total Discussion Counts
Fields
total_discussion_count_z
total_assignment_discussion_count_z
total_threaded_discussion_count_z
total_side_comment_discussion_count_z
Description
These fields present the Z-scores for the total number of discussions in a course for a given week in the term. The definitions of the original total discussion count fields exist in the documentation for mart_taskforce.level1_aggregated.
Average Discussion Entry Length
Fields
avg_discussion_entry_length_z
avg_discussion_post_length_z
avg_discussion_reply_length_z
Description
These fields present the Z-scores for the average length of the discussion entry messages for a student in a course for a given week in the term. More detailed descriptions of the average discussion entry lengths can be found in the documentation for mart_taskforce.level1_aggregated.
Learning Environment Activity
View Days
Fields
view_days
Description
The view_days field shows the Z-score for the number of days a student viewed the learning environment for a course in a given week. The definition of the view days field exist in the documentation for mart_taskforce.level1_aggregated.
Sessions with 10, 20, and 30 Minute Cutoffs
Fields
num_sessions_10min_z
total_time_seconds_10min_z
total_actions_10min_z
avg_time_seconds_10min_z
avg_actions_10min_z
num_sessions_20min_z
total_time_seconds_20min_z
total_actions_20min_z
avg_time_seconds_20min_z
avg_actions_20min_z
num_sessions_30min_z
total_time_seconds_30min_z
total_actions_30min_z
avg_time_seconds_30min_z
avg_actions_30min_z
Description
For this mart, we define sessions using three different time cutoffs: 10 minutes, 20 minutes, and 30 minutes. We define the time spent in a session by adding up the duration of events in the session. These fields present the Z-scores for the number of sessions, total time spent, total number of actions, average time spent, and average number of actions for all three time cutoffs for a student in a course for a given week in the term. The definitions of the base session, time, and action fields exist in the documentation for mart_taskforce.level1_aggregated.
Please visit our separate interaction session mart documentation page here for a visual example and more information about interaction sessions too.
Tool Launches
Fields
num_tool_launches_z
num_tools_launched_z
course_tools_launched
course_tools_not_launched
Description
These fields focus on the LTI tools launched by a student in the learning environment of a course for each week in the term. More detailed definitions of LTI launches exist in the documentation for mart_taskforce.level1_aggregated.
The course_tools_launched and course_tools_not_launched are unique to this table. Both of these fields are of type ARRAY<STRING>. The course_tools_launched array field is a concatenated list of all launch app names seen for the course, week pair for a student. The course_tools_not_launched array field is inferred based on all the launch app names launched for the course for that week across all students. The results in the course_tools_not_launched field are the launch app names that at least one other student in the class launched but the student in scope for the row did not launch.
File Views
Fields
file_views_z
num_files_viewed_z
course_files_viewed
course_files_not_viewed
Description
These fields focus on the files viewed by a student in the learning environment of a course for each week in the term. More detailed definitions of files and file views exist in the documentation for mart_taskforce.level1_aggregated.
The course_files_viewed and course_files_not_viewed are unique to this table. Both of these fields are of type ARRAY<INTEGER>. The course_files_launched array field is a concatenated list of all file IDs seen for the course and week pair for a student. The course_files_not_viewed array field is inferred based on all the file IDs viewed for the course and week across all students. The results in the course_files_not_viewed field are the file IDs that at least one other student in the class viewed but the student in scope for the row did not view.
Last updated