2.0.25
Unizin Data Platform
Last updated
Unizin Data Platform
Last updated
Release Date
October 5, 2020
Full support for all 27 SIS entities
Primary and foreign keys are indexed
Data type definition improvements and enforcement
New Canvas Data data supported
Course section enrollment keymap is changed
Bug fixes
The UDP's context store import process now imports all 27 entities of the SIS 2.0 loading schema. Additionally, all primary and foreign keys in the entity tables are indexed. This will enable efficient JOINs between views/tables in the entity schema. And finally, we are enforcing new custom data types for joint entities, such as Course section enrollment.
We've added a number of Canvas Data-sourced elements in this release. Many of these elements have cousins that are already sourced from the SIS. For example, we're now bringing in Canvas's course grade data to complement the SIS-sourced course grade data. To distinguish between these similar ideas, we're using the "le_" prefix for elements sourced from the "learning environment" where a similar element is sourced from the SIS.
We're adding a new element to Person, contributed by the LMS, that captures the account status for the student in the learning environment (i.e., the LMS). For institutions that use Canvas, the value is sourced from the workflow_state of the user_dim table. It will be represented as the Person entity's le_account_status element in the UCDM.
We've changed the way the UCDM represents Course grades from the learning environment (i.e., the LMS) so that it's distinct from Course grades contributed by an institution's official system of record (i.e., the SIS). The following UCDM elements on Course grade are renamed with an "le_" prefix. Their values are contributed by the LMS:
current_score -> le_current_score
final_score -> le_final_score
hidden_current_score -> le_hidden_current_score
hidden_final_score -> le_hidden_final_score
status -> le_final_score_status
We're adding a new element to Course section, contributed by the LMS, that captures the original Course offering parent of a Course section in case the Course section is cross-listed by the instructor. For institutions that use Canvas, the value will be sourced from the nonxlist_course_id of the course_section_dim table. It will be represented as the Course section entityt's le_original_course_offering_id element in the UCDM.
We've changed the way the UCDM represents aspects of a student's Course section enrollment status. The purpose of the change is to more clearly distinguish elements contributed by the learning environment (i.e., the LMS) and the institution's system of record (i.e., the SIS). The following elements on Course section enrollment renamed with an "le_" prefix, which stands for "learning environment." Their values are contributed by the LMS:
self_enrolled -> le_is_self_enrolled
We're adding and changing elements on the Learner activity entity.
A new "is_lockable" element will be sourced from Canvas could_be_locked value on assignment_dim
Learner activity's lock_date is now renamed to locked_date
Learner activity's unlock_date is now renamed to unlocked_date
We're adding and changing elements on the Learner activity result entity.
A new "what_if_score" element will be source from Canvas Data's what_if_score value on the submission_fact table.
The following values from the Canvas Data quiz_dim table are now modeled in the UCDM.
browser_lockdown_for_displaying_results (boolean) is modeled as Quiz "is_browser_lockdown_required_to_display_results"
browser_lockdown_monitor (boolean), is modeled as Quiz "is_browser_lockdown_monitor_required"
hide_correct_answers_at (timestamp), is modeled as Quiz "hide_correct_answers_date"
show_correct_answers (option set), is modeled as Quiz "correct_answers_display_policy." Note, this new value uses the RefLearningActivityDisplayPolicy option set.
show_correct_answers_at (timestamp), is modeled as Quiz "show_correct_answers_date"
unpublished_question_count, is modeledas Quiz "unpublished_quiz_item_count"
The prerequisite_module_id element on the Module entity is now properly imported.
The LMS Course grade created & updated date values are now properly imported into the Context store
We are deprecating the "possible_points" element on the Learner activity entity. Instead, this element is renamed to "points_possible" to be consistent with naming elsewhere in the UCDM.
None.