Skip to main content

Web 2.0, e-Science and Innovation

Last week the e-Science Institute organised a "think tank" to review the state of e-Science and suggest opportunities for research. A major emphasis of the debate was the recent trend to use Web 2.0 tools to support scientists. Dave de Roure gave several examples he saw at recent conferences, including wikis and blogs such as Open Wetware and Useful Chemistry, as well as various data mashups. Tony Hey gave a public lecture on e-Science and Digital Scholarship which presented a similar story, including the use of utility computing (which now seems to be called cloud computing - you've got to love the constantly changing buzzwords in IT). Among the discussions, people mentioned the combination of Web 2.0 tools with semantic web technology, and the combination of structured queries and semi-structured information as in DBpedia.

This growth of e-Science 2.0 (to coin a buzzword of my own) has mainly seems to have occurred largely in the life sciences, perhaps because they're not centrally organised like the physicists and astronomers. Perhaps they also have more smaller-sclae experiments. One interesting point is that the adoption of these tools has been driven by the scientists making use of commonly-available tools. It isn't the result of existing "road maps" for e-science. It's another case of innovation occurring at the boundaries between communities; where ideas meet and produce new ideas. Sometimes this sort of innovation can be planned (or at least encouraged); sometimes it happens anyway.

This suggests to me that whenever an organisation runs a roadmapping exercise, it pays to include people with a broad mix of backgrounds and some wild ideas. Many of the ideas produced won't germinate, but some of them may grow into something useful.

Comments

Popular posts from this blog

Project Leadership

When I look back over recent projects that I've been involved in, it seems that one key to making a project successful is having someone on the team who really drives it forward: someone who is invested in the project as a whole and not just their own part in it. We (by which I mean the University's Applications division) have a well-defined project process, with defined roles, required milestones, deployment standards, and so forth.    All these are useful, but if the team doesn't have a leader, it seems a project can lose its way, perhaps not responding to changing circumstances, getting stuck on a technical problem, or not securing a needed resource in time to meet some external constraint. The leader can be any member of the team - it could be a developer, a project manager, or the sponsor, or someone in another role.  A team can include several people who are this committed to the project; it doesn't have to be a single person.   As an example, one of...

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this... Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision. "I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!" The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said: "Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!" "No, no, no!", said the guru, "That's not Grid!" The guru exp...