IST Site Navigation:
Mike Ellis, frequent presenter at Museums and the Web, recently published a note on the MCN list describing a Mashed Museum day that was recently held in the UK.
————–
Dear MCN
I thought you might be interested to see a brief(ish) video I hacked
together following the MCG “Mashed Museum” day which happened on the
18th June, the day before the UK Museums on the Web Conference.
See http://blip.tv/file/1029060
Further coverage continues at www.mashedmuseum.org.uk
Cheers!
Mike
————
They’ve also set up a Google Group at http://groups.google.com/group/mashedmuseum. From here, there are several other links that might take you in some interesting directions! For instance, check out the hoard.it prototype at http://feeds.boxuk.com/museums/.
At Educause’s “Advanced CAMP” (Campus Architecture and Middleware Planning) this week the sharpest lesson I learned is how little is solved in the problem space addressed by this year’s CAMP meeting: “Registering, Discovering, and Using Distributed Services in Academia.” Bob Morgan from Univ. of Washington put this in context right up front: though the organizers of the conference like to call the group “Advanced CAMP” Bob thought a more fitting name would be “Advance CAMP” — a group of IT architects seeking solutions at the edge of what is known and/or possible in EDU-space. I presented on what we’ve been hearing at Project Bamboo workshops (my presentation will be coming to the conference wiki soon).
For me the most interesting topic was service discovery, and the take-away from Thursday’s break-out discussion on that topic is that it’s more natural for central-IT providers to think about mechanics of finding a URI for and method of engagement with a known-to-exist service in a defined domain than the broader discovery question, “I want to do X, is there a service out there that’ll do it for me so I don’t have to code it up myself?” (That last is closer to the question a scholar of the type engaged with Project Bamboo might ask, and so is the question in which I’m most immediately interested.) Despite the scattered focus there were interesting suggestions in this space. A few of them: visualizations of services mapped from RDF graphs describing service relationships to each other (Loretta Auvil of SEASR showed some examples); a “bring back gopher” suggestion (with tongue only gently implanted in cheek, from Ken Klingenstein of U. Colorado @ Boulder), with a scholarly-domain flavored partitioning to replace the geographic / institutional partitions that characterized gopher back in the day; the idea (from Mark Morgan of University of Virginia) that assertion of identity might provide an appropriate context for discovery in a bounded space (leading me to think that maybe that’s one way PB can begin to understand the “Facebook for Scholars” types of suggestions we’re hearing at our workshops). The question of how to provide incentive to digital resource providers (be they providers of source material or of applications that find, analyze, manipulate, organize, or annotate it) to attach useful metadata to their contributions to the digital commons remains a cultural question that is central to success of discovery across ‘the usual borders’ but can’t be solved wholly by technologists.
Other thoughts worth sharing:
On the “juicy news” front, we learned from Jens Haeusser of University of British Columbia that USC has joined the Kuali Student Systems effort at the founder level. And Nigel Watling of Microsoft provided some guarded pre-announcements about a plot brewing in Redmond to offer outsourced ESB (cf. biztalk.net) … your services (and the data they carry) linked together on a Microsoft-run bus … and you thought Google Apps was scary! Nigel was a nice fellow, but there was plenty of nervous laughter when he told us that “Microsoft is absolutely committed to open standards” and that the company now understands that if its products are not based on open standards they’re “not relevant.” In response to skepticism about the advisability of putting confidential information out in the cloud, Nigel was less than convincing — assertions like “it’s out in the cloud already … people are now more tolerant of personal information out in the cloud” weren’t the kind of responses likely to satisfy this audience.