# 1.0.58 ## Cumulative Fields and New Coalescing in Student Activity Score | Version | 1.0.58 | | ------------ | ------------- | | Release Date | June 14, 2024 | ## Key Features DSS has added a handful of new fields and metrics in the Student Activity Score marts. These are all additive changes, and no existing queries will break. No existing fields have been renamed. The purpose for the new fields are to support both in-week score calculations and cumulative score calculations. Currently, the metrics for `submissions` and `assignments_due` for a row in the marts are just for the week in scope. We now introduce `submssions_cumulative` and `assignments_due_cumulative` to the metrics tables so that activity scores can be calculated from a start-of-term to now perspective. | Mart Table | New Field Name | Datatype | Description | | ------------------------------ | -------------------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Student Course Metrics | assignments\_due\_cumulative | INTEGER | The number of assignments due in the course from the first day of the term to the current week, inclusive. | | Student Course Metrics | submissions\_cumulative | INTEGER | The number of assignments submitted by the student from the first day of the term to the current week, inclusive. | | Student Course Section Metrics | assignments\_due\_cumulative | INTEGER | The number of assignments due in the course from the first day of the term to the current week, inclusive. | | Student Course Section Metrics | submissions\_cumulative | INTEGER | The number of assignments submitted by the student from the first day of the term to the current week, inclusive. | | Course Final | student\_activity\_score\_cumulative | FLOAT | The student activity score for the student in the course for the given week using cumulative assignment and submission metrics. | | Course Final | student\_activity\_score\_z\_cumulative | FLOAT | The z-score of the student activity score for the student in the course for the given week using cumulative assignment and submission metrics. | | Course Final | student\_activity\_score\_octile\_cumlative | FLOAT | The octile of the student's average student activity z-score in comparison to the average student activity score for the course using cumulative assignment and submission metrics. | | Course Section Final | student\_activity\_score\_cumulative | FLOAT | The student activity score for the student in the course for the given week using cumulative assignment and submission metrics. | | Course Section Final | student\_activity\_score\_z\_cumulative | FLOAT | The z-score of the student activity score for the student in the course for the given week using cumulative assignment and submission metrics. | | Course Section Final | student\_activity\_score\_octile\_cumlative | FLOAT | The octile of the student's average student activity z-score in comparison to the average student activity score for the course using cumulative assignment and submission metrics. | | Final | avg\_student\_activity\_score\_cumulative | FLOAT | The average student activity z-score for the given week in the academic term using cumulative assignment and submission metrics. | | Final | student\_activity\_score\_octile\_cumulative | FLOAT | The octile of the student's average student activity z-score in comparison to the average student activity score for a cohort of students based on their academic program. Based on cumulative assignment and submission metrics | ### New Coalescing We altered some logic in the student activity score tables that limited score calculations only for weeks with non-zero numbers of assignments due. We had this limitation in place to avoid division by 0 since `assignments_due` is in the denominator for part of the score. However, we now use `SAFE_DIVIDE` and coalesce to `0` for metrics with missing data. This allows for score calculations for all weeks in a term. This should make a more consistent timeline of how scores change throughout a term for students. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/release-notes/udp-marts-release-notes/1.0.58.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.