You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: This model contains various aggregations on the teacher/script/year level to measure student progress by particular scripts YoY for a given global trained teacher.
6
7
columns:
@@ -116,92 +117,6 @@ models:
116
117
config:
117
118
tags: ['released']
118
119
119
-
- name: dim_active_teachers
120
-
description: |
121
-
This model serves as a prototype for a comprehensive view of daily teacher activities that roll into the 'active teacher' metric.
122
-
123
-
A teacher is 'active' on a day if they sign-in or perform any one of the set of core teacher actions that we capture via Amplitude.
124
-
(for more details see - placeholder for doc - or the RED team).
125
-
126
-
The model merges platform sign-in data with event data from Amplitude. For both sign-ins and various event interactions
127
-
captured via Amplitude, it captures both occurrence of these events (multiple events aggregated to a day), as well
128
-
as geographical and user type information. Amplitude data can be joined to platform data via a Code.org user_id which
129
-
Amplitude tracks once it learns that a user is a Code.org user.
130
-
131
-
In cases where we have data about a user from both Amplitude and Code.org, for example which country the user is from, we merge
132
-
it together giving preference to the Code.org version of that data.
133
-
134
-
columns:
135
-
- name: event_date
136
-
description: "The date on which either a sign-in or an Amplitude event was recorded (or both). This field merges dates from sign-ins and Amplitude events to align activities across sources."
137
-
data_type: "date"
138
-
data_tests:
139
-
- not_null
140
-
141
-
- name: merged_user_id
142
-
description: "A unified identifier for the user that merges user IDs from Code.org platform sign-ins and Amplitude events, ensuring consistent tracking across sources. This user_id will be the user's Code.org user_id if it is known or the amplitude_id if not."
143
-
data_type: "varchar"
144
-
data_tests:
145
-
- not_null
146
-
147
-
- name: user_type
148
-
description: "The type of the user, which can be 'teacher', 'anon', or other user types from Code.org or Amplitude data. If the user is of type = 'teacher' then the user is a *known code.org teacher user* User_type can occasionally be null for brand new user accounts, when amplitude data has a user_id recorded, but it hasn't been migrated into dim_users yet."
149
-
data_type: "varchar"
150
-
151
-
- name: country
152
-
description: "Country information for the user, merges Code.org geolocation and Amplitude geolocation data. Preference is given to the Code.org data in the case of a conflict between sources."
153
-
data_type: "varchar"
154
-
155
-
- name: us_intl
156
-
description: "Values are `us` or `intl`. Indicates whether the user's country (see: country) is in the US or non-us."
157
-
data_type: "varchar"
158
-
159
-
- name: cdo_user_id
160
-
description: "The Code.org user ID from the sign-in data."
161
-
data_type: "varchar"
162
-
163
-
- name: amplitude_id
164
-
description: "Amplitude's unique identifier for a user, used in tracking event data."
165
-
data_type: "varchar"
166
-
167
-
- name: num_cdo_records
168
-
description: "Count of sign-ins from Code.org data for the user."
169
-
data_type: "integer"
170
-
171
-
- name: num_amp_records
172
-
description: "The number of records from Amplitude for the user for this date."
173
-
data_type: "integer"
174
-
175
-
- name: num_records
176
-
description: "The total number of records from both Code.org sign-ins and Amplitude events for the user on this date."
177
-
data_type: "integer"
178
-
179
-
- name: event_sources
180
-
description: "Possible values: (`cdo`, 'amp,cdo`, `amp`). Comma-separated list indicating the sources of the events ('cdo' for Code.org and 'amp' for Amplitude)."
181
-
data_type: "varchar"
182
-
183
-
- name: events_list
184
-
description: |
185
-
Comma-separated list of event names for activities teachers engaged in. This list aggregates events from both Code.org sign-ins and Amplitude data.
186
-
Code.org sign-in is listed as `cdo_sign_in`.
187
-
Amplitude events have had their names shortened according to the following
- 'Section Progress Unit Changed' --> 'Change unit'
195
-
data_type: "text"
196
-
197
-
data_tests:
198
-
- dbt_utils.unique_combination_of_columns:
199
-
combination_of_columns:
200
-
- merged_user_id
201
-
- event_date
202
-
- user_type
203
-
- us_intl
204
-
205
120
- name: dim_teachers
206
121
description: |
207
122
One row per teacher account ever created, with geographic information and current school association
@@ -256,5 +171,61 @@ models:
256
171
combination_of_columns:
257
172
- school_year
258
173
- teacher_id
174
+
config:
175
+
tags: ['released']
176
+
177
+
- name: dim_daily_teacher_activity
178
+
description: |
179
+
One row per teacher / activity date for every date a teacher had activity, where "activity" is defined by the following events tracked in Statsig (and their activity type classifications):
180
+
curriculum catalog visited (light)
181
+
level activity (light)
182
+
lesson overview page visited (moderate)
183
+
unit overview page visited by teacher (moderate)
184
+
lesson resource link visited (moderate)
185
+
teacher viewing student work (moderate)
186
+
section setup completed (moderate)
187
+
section curriculum assigned (moderate)
188
+
section progress viewed (moderate)
189
+
teacher viewing student work (heavy)
190
+
level feedback submitted (heavy)
191
+
rubric activity (heavy)
192
+
columns:
193
+
- name: teacher_id
194
+
description: unique ID for the teacher with the activity
195
+
data_tests:
196
+
- not_null
197
+
198
+
- name: activity_date
199
+
description: the date on which the teacher had activity
200
+
data_tests:
201
+
- not_null
202
+
203
+
- name: school_year
204
+
description: the school year associated with the activity date, used for aggregation
205
+
data_tests:
206
+
- not_null
207
+
208
+
- name: cal_year
209
+
description: the calendar year associated with the activity date, used for aggregation
210
+
data_tests:
211
+
- not_null
212
+
213
+
- name: has_light_activity
214
+
description: 1 if the teacher did any event considered "light" on the activity date, 0 otherwise
215
+
216
+
- name: has_moderate_activity
217
+
description: 1 if the teacher did any event considered "moderate" on the activity date, 0 otherwise
218
+
219
+
- name: has_heavy_activity
220
+
description: 1 if the teacher did any event considered "heavy" on the activity date, 0 otherwise
221
+
222
+
- name: events_touched
223
+
description: comma separated list of events the teacher did on the activity date
0 commit comments