It’s half way through week three of #oldsmooc, and once again I have been distracted from the actual course by the possiblities (and opportunities) that a bit of tweaking to Cloudworks could offer. One of the comments Tony Hirst made last week about the practicalities of including some of the network visualisation experiments he had been working on was that of caching and time for real-time diagrams to appear on a user page. Good point, well made, as they say – I don’t think this is insurmountable but it’s not going to be the focus of this week’s post, I’ll come back to it again. But I do think that this is exactly the type of user centred feature that any “new and exciting” (cos of course none of them are “as dull and boring” as the platforms we already have) mooc platform” should be trying to incorporate.
This week’s data challenge was much simplier really and you can see the twitter chain of events in this storify.
[View the story “#oldsmooc_w3 Cloudworks challenge” on Storify]
Once again Tony came up trumps and created a lovely visualisation, but as my last tweet said, was this maybe a bit too much? And as Tony himself asked earlier -what does another view “buy you”? In this case, where there is a essentially a growing list of four different types of “things” maybe just an simpler alternative view (without all the connections) would be more helpful? As the list grows it would be helpful to be able to quickly search for example the tools. This page is undoubtedly a useful resource and as such a bit of time in ensuring that is displayed in ways that help people use/contribute and sustain it is surely worth while. I’d be interested in any other suggestions people may have.
I’m now going to do some more of the actual course work and try to respond to this.
I wonder if we could get a detailed Cloudworks vis scenario out of @sheilmcn to inform designs for me & @psychemedia #oldsmooc_vis @yishaym
— Chris Teplovs (@cteplovs) January 26, 2013