We’re now in the third week of the Fall 2013 Desire2Learn pilot, and I find myself using the Users > Statistics page to monitor the status of the environment. It’s an extremely coarse way to see if people are having problems (if there’s a problem, I’d assume the user count drops to near 0).
![D2L User Statistics.png D2L User Statistics](https://ancient.darcynorman.net/darcynorman.net/2016/wp-content/uploads/2013/09/D2L-User-Statistics.png)
It’s not exactly ideal, though. What I’d love is something closer to what WordPress gives for recent activity, but for active users in the environment. Something kind of like:
![D2L User Activity Report Mockup.png D2L User Activity Report Mockup](https://ancient.darcynorman.net/darcynorman.net/2016/wp-content/uploads/2013/09/D2L-User-Activity-Report-Mockup.png)
Bonus points for some content activity reports as well (# of courses active, # of discussion posts per hour, # of quizzes submitted per hour, video notes published/viewed, etc…)
Extra-special bonus points for something that could be set to run on an iPad display to monitor the environment throughout the day…
Naturally, the first thing I'd try to do with Pipes is to mock up something like Eduglu – taking feeds associated with a group of individuals and merging them into one place. The concept, from an educational standpoint, would theoretically make it feasible for students and/or teachers to monitor relevant online activities for an entire class, without having to hunt out each person's various feeds.
It's not quite there yet, though. Currently, the concept of Filters is rather borked in Pipes. If you're dealing with a homogeneous set of feeds in a Fetch, it works fine, but as you add different kinds of feeds, the parameters for filtering go all wonky (is it filtering based on Category? dc:topic? Title? Description? Something else?)
I've mocked up a too-simple version of what Pipes can do with a set of 5 individuals' various feeds (blogs, Flickr, del.icio.us, Twitter). It's essentially unusable as an Eduglu, since there is no way to properly (and effectively) filter and/or prioritize items that are aggregated. And the display seems to be rather simple (title + one line of teaser).
Here's what the Pipe looks like from the inside:
And the output looks like this:
I'm going to be putting some more thought into what an interface might look like for defining groups, pulling in an individual's feeds, and displaying the aggregation. This is starting to feel like it's going to need some pretty high-end UI work on top of some pretty flexible plumbing to be able to do this effectively.
Naturally, the first thing I'd try to do with Pipes is to mock up something like Eduglu – taking feeds associated with a group of individuals and merging them into one place. The concept, from an educational standpoint, would theoretically make it feasible for students and/or teachers to monitor relevant online activities for an entire class, without having to hunt out each person's various feeds.
It's not quite there yet, though. Currently, the concept of Filters is rather borked in Pipes. If you're dealing with a homogeneous set of feeds in a Fetch, it works fine, but as you add different kinds of feeds, the parameters for filtering go all wonky (is it filtering based on Category? dc:topic? Title? Description? Something else?)
I've mocked up a too-simple version of what Pipes can do with a set of 5 individuals' various feeds (blogs, Flickr, del.icio.us, Twitter). It's essentially unusable as an Eduglu, since there is no way to properly (and effectively) filter and/or prioritize items that are aggregated. And the display seems to be rather simple (title + one line of teaser).
Here's what the Pipe looks like from the inside:
And the output looks like this:
I'm going to be putting some more thought into what an interface might look like for defining groups, pulling in an individual's feeds, and displaying the aggregation. This is starting to feel like it's going to need some pretty high-end UI work on top of some pretty flexible plumbing to be able to do this effectively.