Earlier this year the JISC launched a debate of Libraries of the Future. UKOLN recently contributed to this debate by sponsoring the Mashed Library event which was facilitated by Owen Stephens, Imperial College.  My contribution has been in exploring best practices for exploiting the potential of Library 2.0. I presented a paper on “Library 2.0: Balancing the Risks and Benefits to Maximise the Dividends” at the Bridging Worlds 2008 conference on “Libraries in the 2.0 Age and Beyond” held at the National Library of Singapore and gave an updated version of the talk at the Nordlib 2.0 conference on “Nordlib 2.0 – Get Inspired by Web 2.0 for Libraries” held at Aula Magna, Stockholm University, Stockholm, Sweden on 21st November 2008.

It was a privilege to be asked to give the final talk at the conference, and to have a full hour to describe my thoughts on how libraries should go about “Realising The Potential of Web 2.0“.

The conference blog provides more information about the conference and the talks which were given. The talks were streamed live and the videos are currently being edited and will be uploaded shortly. In addition I used a Flip camera to record my own talk and this is available on Google Video (and Blip.tv) and embedded below.


In addition I have used Zentation to synch the video with the PowerPoint slides, as illustrated below. The slides are also available on Slideshare.

Realising The Potential of Web 2.0
Talk on Realising The Potential of Web 2.0

I hope these different versions of the talk are useful. But if I was to provide only one version of the talk what, I wonder, should it be. The PowerPoint file on the UKOLN Web site, the HTML equivalent, the Slideshare manifestation (with the ability to be embedded elsewhere), the original .AVI file (warning, large file), the Google Video or Blip.TV video of the talk or the synched version of the talk and the slides on Zentation? And is the provision of a variety of versions a sensible precaution at a time when the sustainability of Web 2.0 may be questionable or confusing to the end user?