New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some process needs to still retrieve/persist user_id and sis_name as it is used for MiVideo access events #1443
Comments
… query for UDW cron; will file a UDP request for including Canvas user login_id in UDP, so that we can retrieve the sis_name field in UDP cron, too
To clarify, can an example of the Caliper event from MiVideo be added to the description? |
@lsloan you can find the MiVideo query inside this wiki page |
…ron query (#1444) Co-authored-by: Code Hugger (Matthew Jones) <jonespm@umich.edu>
Expected outcomes: Kaltura video events will be included in Resources Accessed for users who people who exist in the UDP as students and teachers in the SIS data when they have a StudentEnrollment on a course with MyLA enabled. Kaltura video events will NOT be available for:
|
(Per Matt) There's 3 ways to improve this.
|
Testing passes in Beta. Event data is included for enrolled students. |
The fix we made for this for this release was to replace the mivideo query to do a replacement in the username. This is documented in the wiki
|
Testing passes in Test. Event data is included for enrolled students. |
Describe the bug (Tell us what happens instead of the expected behavior) :
In PR #1392, the user cron query does not pull in uniqname/sis_name from UDW. This is in preparation for UDP transition and UDP does not have non-roster user info, so that we need to get user login_name from LTI launch #1344
However, this causes problem for MiVideo resource access events:
Since MiVideo is standalone tool, the Caliper events does not have Canvas user id information, so the user_id field has value of "-1". In cron.py line 312, MiVideo events are joined with the MyLA user table based on sis_name, so that MiVideo events can be stored inside resource_access table with values in user_id field
With the above change of PR #1392, MyLA user table no longer has sis_name field populated after cron run, and instead the sis_name value is set upon individual LTI launch and will be reset to null with next cron job. Hence the merge in cron.py line 333 will always return empty dataframe for MiVideo access events, hence MiVideo events won't be shown in Resource Access View.
Steps to Reproduce :
The text was updated successfully, but these errors were encountered: