# 1.0.80

## New Fields in LMS Tool Mart; Updated Logic in Taskforce, File Interaction, and Interaction Sessions Marts

| Version      | 1.0.80           |
| ------------ | ---------------- |
| Release Date | January 30, 2025 |

## Key Features

### [LMS Tool Mart](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/lms-tool-use)

The following fields have been added to the LMS tool mart:

* udp\_discussion\_id
* udp\_quiz\_id
* udp\_module\_item\_id
* udp\_file\_id
* udp\_wiki\_page\_id
* udp\_learner\_activity\_id

These fields are populated when a user interacts with a specific object that is defined in the UDP context store. For example, if a user interacts with a specific quiz that is defined in the UDP `quiz`entity, the UDP ID of that quiz populates the *udp\_quiz\_id* field in the mart. These new fields allow for easier joining between the mart and the UDP context store entities, which makes it easier for users to get contextual data about LMS tool interactions.&#x20;

### [Taskforce Marts](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/taskforce)

Originally, the taskforce marts only included activity that occurred between the start and end date of a course. This threshold could be leaving out activity that occurred in the "finals week" for a course, or the week after the course officially ends. To include this activity in the marts, the threshold for activity is now between the start date of the course and the week after the official end date of the course.&#x20;

This threshold has also been updated to compare the date associated with an assignment to the mentioned dates of the course, instead of the date and time associated with an assignment. When the time is considered for the threshold, it is possible to drop activity that occurred on the first or last day of the given timeframe. By only comparing the dates for assignments, this is no longer a possibility.&#x20;

### [File Interaction](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/file-interaction)

The `file_interaction` mart now populates *udp\_course\_offering\_id* from the `course_offering`keymap table when it exists. Before, *udp\_course\_offering\_id* was only populated from the *course\_offering.udp\_id* field in the `event_store.expanded`table. Since the records in the `expanded`table are not updated after the records are stored, any changes to the relationships between keys is not reflected. The UDP keymap does reflect these relationship changes however. By populating *udp\_course\_offering\_id* from the keymap instead of the event, the `file_interaction`mart presents the most up-to-date data.&#x20;

### [Interaction Sessions](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/interaction-sessions)

There was a slight typo in the starter SQL used to create the `event__course_offering__interaction_sessions` helper table that populates the `interaction_sessions`mart. Instead of filtering for events between the start and end date of the academic session (when these dates are populated), we were filtering for events that occurred on the start date of the course. This only affected events for courses that were associated with an academic session; otherwise the filter worked as intended. The issue has been fixed, and the `interaction_sessions`mart now includes all of the events in scope for the mart.&#x20;