Course Status
Last updated
Last updated
The mart_course_offering.status mart includes information regarding the status of a Course offering in a learning environment. The mart_course_section.status mart does the same at the course section level.
mart_course_offering
mart_course_section
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.
udp_course_offering_id
INTEGER
The UDP ID for the Course offering.
lms_course_offering_id
STRING
The LMS ID for the Course offering.
academic_term_name
STRING
The name of the academic term, i.e. Fall 2020.
academic_term_start_date
DATE
The start date for the academic term.
academic_organization_array
ARRAY<STRING>
An array of the academic organization(s).
academic_organization_display
STRING
An array of the academic organization(s) written as a comma-separated string.
course_offering_title
STRING
The title of the Course offering, i.e. Linear Algebra.
course_offering_start_date
DATE
The start date for the Course offering.
course_offering_subject
STRING
The subject of the Course offering, i.e. MATH.
course_offering_number
STRING
The number of the Course offering, i.e. 310
course_offering_code
STRING
The code of the Course offering, i.e. MATH 310.
instructor_name_array
ARRAY<STRING>
An array of all the instructor’s names for the Course offering.
instructor_lms_id_array
ARRAY<STRING>
An array of all the instructor’s LMS IDs for the Course offering.
instructor_display
STRING
An array of all the instructor’s names for the Course offering written as a string.
instructor_email_address_array
ARRAY<STRING>
An array of all the instructor email addresses for the Course offering.
instructor_email_address_display
STRING
An array of all the instructor email addresses for the Course offering written as a comma-separated string.
status
STRING
The status of the Course offering.
reported_status
STRING
The reported status of the Course offering.
publish_time
DATETIME
The time the Course offering was published.
num_students
INTEGER
The number of students enrolled in the Course offering.
published_la
INTEGER
The number of published learner activities in the Course offering.
unpublished_la
INTEGER
The number of unpublished learner activities in the Course offering.
published_quiz
INTEGER
The number of published quizzes in the Course offering.
unpublished_quiz
INTEGER
The number of unpublished quizzes in the Course offering.
active_module
INTEGER
The number of active modules in the Course offering.
unpublished_module
INTEGER
The number of unpublished modules in the Course offering.
The course section mart includes all the fields included in the course offering mart, in addition to the nine fields shown below.
udp_course_section_id
INTEGER
The UDP ID of the Course section.
lms_course_section_id
STRING
The LMS ID of the Course section.
combined_section_basis
STRING
The primary basis for combining sections together if the Course section is combined with others. Common values for this field are CrossListed, MeetTogether, and UgGrad.
combined_section_id
STRING
The ID of the combined Course section if the Course section is combined with others.
delivery_mode
STRING
The delivery for the instruction given in the Course section, i.e. FaceToFace, Online, BlendedLearning.
is_combined_section_parent
INTEGER
A binary value (0 or 1) indicating whether the Course section in a group of combined Course sections is the Parent Course section. This is only meaningful if the course section is combined with other sections.
is_default
INTEGER
A binary value (0 or 1) indicating whether the Course section is the default Course section.
is_graded
INTEGER
A binary value (0 or 1) indicating whether the Course section is the graded Course section.
is_honors
INTEGER
A binary value (0 or 1) indicating whether the Course section is a Honors Course section.
The status field defines the status of the Course offering in the learning environment. The status of the Course offering is found by looking at events from the learning environment. Specifically, we look for an event where the status of the course was modified. For example, to define the status of a course in Canvas, we look for an event with a ‘Modified’ action and an object with a non-null workflow state. These aspects of an event tell us that the status was modified. By depending on events, we are able to have the most recently updated status for the course. The status field in this mart is defined as the workflow state of the object in the event. If this field is null for a course, we then will define the status from the le_status field in the course_offering table from the context store. Overall, the status field tells us the current state of the Course offering, specifically in relation to its availability for teaching and learning. Common values for this field are presented below.
Published - the course is published.
Unpublished - the course is not published.
Active - the course is published and currently active.
Completed - the course has concluded.
Created - the course has been created but not published.
Deleted - the course has been deleted.
Available - the course has been published and is not completed.
Claimed - the course has been undeleted and is not published
The reported_status field in this mart is similar to the status field, but more generalized for reporting purposes. The reported status prioritizes the statuses that users find most relevant. The reported_status field is defined by the status field. We define four values for the reported_status field:
Not Published
Published
Deleted
Completed
The status values that map to a ‘Not Published’ reported status are ‘Created’, ‘Claimed’, and ‘Unpublished’. The status values that map to a ‘Published’ reported status are ‘Available’, ‘Published’, and ‘Active’. The ‘Deleted’ status value maps to the ‘Deleted’ reported status value, and the ‘Completed’ status value maps to the ‘Completed’ reported status value.
The publish_time field for this mart defines when the Course offering was published. This is achieved by looking through the events emitted in the course from the learning environment. Specifically, we look for the earliest event in which the status of the course was modified. If the learning environment being used is Canvas, we look for the earliest event with a ‘Modified’ action and a ‘published’ workflow state. This is a very similar process as how we define the status of a course, except in this case we look for the earliest event rather than the latest, and we only focus on events with ‘published’ workflow states.
The num_students field defines the number of enrolled students in the Course offering. This number is found from the course_section_enrollment table in UDP’s context store, which keeps track of enrollments in course sections. We count the number of enrollments with a role of ‘Student’ or ‘Observer’ and a role status that is not ‘Dropped’, ‘Withdrawn’, or ‘Not-enrolled’.
The published_la field in this mart is the number of published learner activities in the course offering. We use the learner_activity table from the context store to compute this field. Using this table, we count the number of learner activities in the course with a status of ‘published’.
The unpublished_la field is the number of unpublished learner activities in the course offering. Again, we use the learner_activity table from the context store to compute this field. For this field, we count the number of learner activities with an ‘unpublished’ status.
The published_quiz field is the number of published quizzes in the course offering. To compute this field, we use the quiz table from the context store. Using this table, we count the number of quizzes in the course with a status of ‘published’.
The unpublished_quiz field is the number of unpublished quizzes in the course offering. For this field, we use the quiz table in the context store to count the number of quizzes in the course with an ‘unpublished’ status.
The active_module field is the number of active modules in the course offering. Using the module table in the context store, we count the number of modules in a course with an ‘active’ status.
The unpublished_module field is the number of unpublished modules in a course offering. We use the module table in the context store to count the number of modules in the course with an ‘unpublished’ status.
