You've had an opportunity to review our development phases for this priority, as well as review greater design detail. Let us know if you think we're on the right track.
One possible improvement to support event sequencing is to include milliseconds in the event time. That would be a useful improvement. An additional improvement that might support more precise sequencing would be to include an identifier of the previous event. Personally, I'm primarily interested the sequence of navigation events, and it would be a helpful feature to include something that could be interpreted as something like a "NavigatedFrom" field.
Including client_ip would be a great improvement, which might allow us to estimate a user's local time. But this would require us to maintain IP-to-geoLocation and geoLocation-to-timeZone lookup tables, which would be a pretty difficult effort. I wonder whether it would be possible to just include the user's local time zone in the event structure? It would be optimal if Canvas were able to record the user's local system time directly from the browser. (And while I'm asking: could the browser also return geolocation data for the user that could be included in the event?)
Not sure if this thread is still open or active and if this is even the correct thread to post to.
You should add a dark mode.
At night the massive white portion of the screen can be quite blinding.
Also as a side note, make it easier for users to offer feedback within Canvas.
Keep up the good work.
Are you going to scope the Live Events returned to the User?
I've built an applicaiton that pulls unread discussion entries through your current API to process through a Natural Language Processor to assign sentiment values to catch confrontational/aggressive posts that need immediate moderation by a faculty. The ideal solution would use AWS SQS and Lambda so that evaluation and notification would be as soon as possible. Currently the Live Events are only scoped to the root level so any subscriptions will send ALL events for every course in the entire account. So me, a simple faculty, would be receiving every discussion entry from all 23 community colleges in my system. Which is why I had to go with the pulling from the already scoped API with my own user key.
We do indeed have plans to enable event feeds at the course level thru the Canvas Course UI, it is not a first priority feature at the moment, so it is probably something we will do at the end of this year.
Awesome thank you Oxana Jurosevic! If you need any testers I am happy to run it on my courses.
Retrieving data ...