Web 2.0 And The Institutional Web

1. Web 2.0 And The Institutional Web Brian Kelly UKOLN University of Bath Bath Email [email_address] UKOLN is supported by: http://www.ukoln.ac.uk/web-focus/events/meetings/scottish-web-folk-2006-08/ Acceptable Use Policy Recording/broadcasting of this talk, taking photographs, discussing the content using email, instant messaging, Blogs, SMS, etc. is permitted providing distractions to others is minimised. This work is licensed under a Attribution-NonCommercial-ShareAlike 2.0 licence (but note caveat) scottish-web-folk-2006-08 tag used in del.icio.us

2. Contents <ul><li>Web 2.0 / E-Learning 2.0 / Library 2.0 </li></ul><ul><ul><li>It's great </li></ul></ul><ul><li>Organisational barriers </li></ul><ul><ul><li>Technology is immature </li></ul></ul><ul><ul><li>Legal risks </li></ul></ul><ul><ul><li>It's too costly </li></ul></ul><ul><ul><li>… </li></ul></ul><ul><li>Addressing the barriers </li></ul><ul><ul><li>Understanding our culture </li></ul></ul><ul><ul><li>Risk assessment and risk management </li></ul></ul><ul><ul><li>Deployment strategies </li></ul></ul><ul><li>Exploiting Our Strengths </li></ul><ul><ul><li>The IWMC </li></ul></ul><ul><ul><li>The Scottish Web Folk community </li></ul></ul>

3. Web 2.0, E-Learning 2.0 & Library 2.0 <ul><li>We know how: </li></ul><ul><ul><li>Blogs allow our users to easily create content and share their views </li></ul></ul><ul><ul><li>Wikis allow communities to easily collaborate in creation of content </li></ul></ul><ul><ul><li>Social networking services (e.g. del.icio.us, Flickr, etc) allow communities to share resources (e.g. bookmarks, photographs, …) </li></ul></ul><ul><ul><li>Syndication technologies (e.g. RSS, Atom) allow communities to be easily repurposed ('mashups') </li></ul></ul><ul><ul><li>Messaging technologies (e.g. MSN, Jabber, Skype) allow people to communicate </li></ul></ul><ul><li>And this relates directly with our learning & teaching & research activities </li></ul>Web 2.0 So we will all be deploying these services within our institutions. Are we?

4. Takeup Of New Technologies <ul><li>The Gartner curve </li></ul>Developers Rising expectations Trough of despair Service plateau Enterprise software Large budgets Mainstream… Early adopters <ul><li>Chasm </li></ul><ul><li>Failure to go beyond developers & early adopters (cf Gopher) </li></ul><ul><li>Need for: </li></ul><ul><ul><li>Advocacy </li></ul></ul><ul><ul><li>Listening to users </li></ul></ul><ul><ul><li>Addressing concerns </li></ul></ul><ul><ul><li>Deployment strategies </li></ul></ul><ul><ul><li>… </li></ul></ul>This talks looks at approaches for avoiding the chasm

5. The Barriers <ul><li>There are barriers to the deployment of Web 2.0: </li></ul><ul><ul><li>It's scary: I've just mastered CSS; we've just spend a lot of money on a CMS; … </li></ul></ul><ul><ul><li>It's immature: I've heard it all before (XML, Semantic Web, …). This is just the latest hype. </li></ul></ul><ul><ul><li>There are legal risks: Copyright infringement; data protection; protection of minors; … </li></ul></ul><ul><ul><li>Infringement of guidelines: Web 2.0 infringes our AUP; accessibility legislation; e-Gov legislation; .. </li></ul></ul><ul><ul><li>Institutional inertia: We'd like to do it but we have large existing systems; reluctant colleagues; … </li></ul></ul>Web 2.0 Barriers How do we go about addressing these barriers? (And should we – what if the concerns are legitimate!)

6. Addressing The Barriers <ul><li>In order to address these barriers we need to: </li></ul><ul><ul><li>Understand our organisation's culture </li></ul></ul><ul><ul><li>Recognise the limitations of the services we're seeking to deploy </li></ul></ul><ul><ul><li>Be user-focussed in the services we seek to implement </li></ul></ul><ul><ul><li>Support safe, possibly small-scale usage </li></ul></ul><ul><ul><li>Have a deployment strategy to build on small-scale pilots and move to larger-scale usage (if appropriate) </li></ul></ul><ul><ul><li>We may also wish to: </li></ul></ul><ul><ul><ul><li>Work within our organisation's culture </li></ul></ul></ul><ul><ul><ul><li>Instigate cultural change within our organisation </li></ul></ul></ul>Web 2.0 Barriers

7. Nobody Likes Us - The Users' View <ul><li>IT Services: </li></ul><ul><ul><li>Don't understand learning and teaching and think that students only ever use the Web for messing around. </li></ul></ul><ul><ul><li>Have no interest in what the users actually want and generally prefer to give the users what they themselves think they want. (I've seen senior IS staff dismiss the data gathered in formal user requirements gathering exercises because it doesn't fit their own viewpoint.) </li></ul></ul><ul><ul><li>Tend to work in silos (example: student information systems team which won't talk to the VLE team), and will do anything to avoid working with others outside of their own silo. They have no concept of team working across services or with academic staff. </li></ul></ul><ul><ul><li>Consultation usually consists of them telling you what they are going to do . If you tell them what you want they don't listen! </li></ul></ul>IT Services Barrier Do these comments ring any bells? If not, how can you be sure?

8. Beware The IT Fundamentalists <ul><li>We need to avoid simplistic solutions to the complexities: </li></ul><ul><ul><li>Open Standards Fundamentalist: we just need XML </li></ul></ul><ul><ul><li>Open Source Fundamentalist: we just need Linux </li></ul></ul><ul><ul><li>Vendor Fundamentalist: we must need next version of our enterprise system (and you must fit in with this) </li></ul></ul><ul><ul><li>Accessibility Fundamentalist: we must do WAI WCAG </li></ul></ul><ul><ul><li>User Fundamentalist: we must do whatever users want </li></ul></ul><ul><ul><li>Legal Fundamentalist: it breaches copyright, … </li></ul></ul><ul><ul><li>Ownership Fundamentalist: must own everything we use </li></ul></ul><ul><ul><li>Perfectionist : it doesn't do everything, so we'll do nothing </li></ul></ul><ul><ul><li>Simplistic Developer : I've developed a perfect solution – I don't care if it doesn't run in the real world </li></ul></ul>IT Services Barrier IT Director, March 2006 " I could give names of the individuals in my department! "

9. The Librarian Fundamentalists <ul><li>Librarians: </li></ul><ul><ul><li>Think they know better than the user e.g. they don't like people using Google Scholar; they should use Web of Knowledge (who cares that users find it easier to use Google Scholar & finds references they need that way?) </li></ul></ul><ul><ul><li>Think that users should be forced to learn Boolean searching & other formal search techniques because this is good for them (despite Sheffield's study). </li></ul></ul><ul><ul><li>Don't want the users to search for themselves (cf folksonomies) because they won't get it right. </li></ul></ul><ul><ul><li>They still want to classify the entire Web - despite the fact that users don't use their lists of Web links. </li></ul></ul><ul><ul><li>Want services to be perfect before they release them to users. They are uneasy with the concept of 'forever beta' (they don't believe that users have the ability to figure things out themselves and work around the bugs). </li></ul></ul>Library Barrier

10. The Problem With The Users <ul><li>The enthusiastic users will be: </li></ul><ul><ul><li>Here, encouraged by Web 2.0 descriptions </li></ul></ul><ul><ul><li>Cheering the critiques of the service departments </li></ul></ul><ul><li>However: </li></ul><ul><ul><li>Many users are conservative & won't care </li></ul></ul><ul><ul><li>Many will feel threatened </li></ul></ul><ul><ul><li>Many won't like WiFi in libraries, lecture theatres, students chatting on IRC, Googling answers, … </li></ul></ul><ul><ul><li>Many will soon ask for WiFi to be removed, blocked from lecture theatres (including areas where it's not yet available!) </li></ul></ul>The Users Barrier

11. Addressing the Barriers <ul><li>How do we address such barriers: </li></ul><ul><ul><li>A change in culture </li></ul></ul><ul><ul><li>Being more open (surely what HE is about?) </li></ul></ul><ul><ul><li>Revisiting AUPs </li></ul></ul><ul><ul><li>Developing more sophisticated models for standards, accessibility, open sources, … </li></ul></ul><ul><ul><li>Developing key principles </li></ul></ul><ul><ul><li>Ongoing debate and discussion </li></ul></ul>Cultural Change

12. Implement An Open Approach <ul><li>Implementing an open approach should not be difficult: </li></ul><ul><ul><li>We have tradition of sharing & using OSS </li></ul></ul><ul><ul><li>The HE sector is now more open to discussing open access issues (e-prints, financial issues, …) </li></ul></ul><ul><ul><li>Creative Commons (CC) provides a legal framework </li></ul></ul><ul><li>What can we do: </li></ul><ul><ul><li>Make support services resources available with CC licence: see paper on " Let's Free IT Support Materials! " </li></ul></ul><ul><ul><li>Exploit UKOLN's QA Focus briefing documents: 100+ documents available with CC licence </li></ul></ul><ul><ul><li>… </li></ul></ul>Using other's resources and service may be unpopular (job security, ideology, …). For example, should IT services host email, … when this can be outsourced? Cultural Change

13. Acceptable Use Policies (AUP) <ul><li>Is Skype Permitted over JANET? </li></ul><ul><ul><li>"The Computing Service is frequently asked for a ruling on whether Skype may legitimately be used ... the Computing Service considers that use of Skype contravenes the JANET Acceptable Use Policy, although UKERNA does not concur with this view." (Mar 2006 - now toned down) </li></ul></ul><ul><li>Missing The Point? </li></ul><ul><li>There may be (religious) debates over the interpretation of UKERNA's words. But </li></ul><ul><ul><li>Did the policy come from God? Is it infallible? </li></ul></ul><ul><ul><li>Why do we hide behind AUPs? </li></ul></ul>Revisiting AUPs Proposal : An AUP is meant to work on behalf of an organisation, helping to ensure the effective use of IT by its users. An AUP should not be used as a control mechanism to prevent usage which IT staff may frown upon.

14. The Need For An AUPP <ul><li>AUPs: </li></ul><ul><ul><li>Shouldn't be cast in stone: technologies change; usage changes; culture changes (e.g. AUPs banning social use; email; Web; messaging; …) </li></ul></ul><ul><ul><li>Therefore need for mechanisms for changing AUPs and engagement with users </li></ul></ul><ul><li>Proposal: </li></ul><ul><ul><li>We need an Acceptable Use Policy Process (AUPP) </li></ul></ul><ul><ul><li>We need mechanisms to ensure users can input into the discussion process </li></ul></ul><ul><ul><li>We need more flexibility in our AUPs (e.g. to reflect blended learning, pervasiveness of IT; …) </li></ul></ul> Cultural Change

15. Risk Management (1) <ul><li>IWMW 2006 has taken a risk management approach to its evaluation of Web 2.0 technologies: </li></ul><ul><ul><li>Agreements : e.g. in the case of the Chatbot. </li></ul></ul><ul><ul><li>Use of well-established services : Google & del.icio.us are well-established and have financial security. </li></ul></ul><ul><ul><li>Notification : warnings that services could be lost. </li></ul></ul><ul><ul><li>Engagement : with the user community: users actively engage in the evaluation of the services. </li></ul></ul><ul><ul><li>Provision of alternative services: multiple OMPL tools. </li></ul></ul><ul><ul><li>Use in non-mission critical areas: not for bookings! </li></ul></ul><ul><ul><li>Long term experiences of services: usage stats </li></ul></ul><ul><ul><li>Availability of alternative sources of data : e.g. standard Web server log files. </li></ul></ul><ul><ul><li>Data export and aggregation: RSS feeds, aggregated in Suprglu, OPML viewers, etc. </li></ul></ul>Taking Risks

16. Risk Management (2) <ul><li>File Formats </li></ul><ul><ul><li>Microformats are a bottom-up approach </li></ul></ul><ul><ul><li>OPML is simple but ambiguous </li></ul></ul><ul><ul><li>How scalable? </li></ul></ul><ul><ul><li>Will formats change in light of experience? </li></ul></ul><ul><li>Approaches: </li></ul><ul><ul><li>Use to provide services today </li></ul></ul><ul><ul><li>Look for tools which will allow for changes </li></ul></ul><ul><li>Applications </li></ul><ul><ul><li>No longer critical in many areas! </li></ul></ul><ul><ul><li>If application is flawed, no longer available through it away and use an alterative </li></ul></ul>Taking Risks Note that you also take risks in not providing a service! Will your users go elsewhere?

17. Safe Experimentation <ul><li>How can we gain experiences of Web 2.0: </li></ul><ul><ul><li>Safe environment </li></ul></ul><ul><ul><li>Which minimise risks </li></ul></ul><ul><ul><li>Which allow learning </li></ul></ul><ul><li>Possibilities: </li></ul><ul><ul><li>Using technologies at events such as ILI! </li></ul></ul><ul><ul><li>Supporting the services which your users use (e.g. Google!) </li></ul></ul><ul><ul><li>Using services which require minimal effort </li></ul></ul>Piloting Web 2.0 Let's quickly review how Web 2.0 was used at the IWMW 2006 event, June 2006. Slides taken from " Web 2.0: Behind The Hype " panel session

18. Blogs <ul><li>Blogs: </li></ul><ul><ul><li>We link to Blogs provided by IWMW 2006 delegates </li></ul></ul><ul><ul><li>We recommend a tag (IWMW2006) to make it easier to find other Blogs, photos, bookmarks, etc. related to the event (e.g. using Technorati ) </li></ul></ul>Web 2.0 and IWMW 2006 http://www.meanboyfriend.com/overdue_ideas/ http://iwmw2006.blogspot.com/ Why? Facilitates sharing of thoughts about event. Effort : None – the Bloggers are doing the work! Risks : They say nasty things; upset people; … Blogs Users Syndication

19. Wikis <ul><li>Wikis: </li></ul><ul><ul><li>Used successfully at IWMW 2005 and UKOLN / UCISA events for note-taking in breakout groups, social use, … </li></ul></ul><ul><ul><li>Available at IWMW 2006: </li></ul></ul><ul><ul><ul><li>UKOLN Wiki (MediaWiki) </li></ul></ul></ul><ul><ul><ul><li>Other Wikis (for various parallel sessions) </li></ul></ul></ul>Web 2.0 and IWMW 2006 http://www.ukoln.ac.uk/web-focus/events/ workshops/webmaster-2005/wiki-test/ Why? Wikis have proved popular at other UKOLN events Why diversity : To allow us to gain a feel of different Wikis and their strength & weaknesses. Wikis Users Syndication http://iwmw-barriers.pbwiki.com/

20. Maps <ul><li>Google Map of University of Bath embedded on Web site </li></ul><ul><li>Provides: </li></ul><ul><ul><li>Usability (rescalable and repositioning through use of AJAX) </li></ul></ul><ul><ul><li>Can be personalised (map from my home) </li></ul></ul><ul><ul><li>Effective use of scarce resources (avoids techies duplicating existing services) </li></ul></ul>Web 2.0 and IWMW 2006 http://www.ukoln.ac.uk/web-focus/events/ workshops/webmaster-2006/maps/ Risk : What if Google go out-of-business? Response : What if local staff leave? What if other development work they should do fails to get done? Note : Northumbria have better examples APIs AJAX Mashups Syndication

21. Building A Community <ul><li>Building a community for your Web site can: </li></ul><ul><ul><li>Maximise impact by allowing interested parties to discuss their shared interests </li></ul></ul><ul><ul><li>Provide you with feedback & ideas </li></ul></ul><ul><ul><li>Allow you to provide targetted information </li></ul></ul>http://www.frappr.com/iwmw2006 Web 2.0 services such as Frappr, Blogger, MySpace, etc. allow Web communities to be easily set up (and may be particularly valuable to the 'Net Generation') Mashup AJAX Collaboration

22. Del.icio.us <ul><li>Del.icio.us social bookmarking service available for use to: </li></ul><ul><ul><li>Provide access to resources mentioned in talks & workshops </li></ul></ul><ul><ul><li>Allow others to bookmark related resources </li></ul></ul><ul><ul><li>Allow users to view others’ bookmarks </li></ul></ul><ul><ul><li>Monitor who’s bookmarked your resources </li></ul></ul>Web 2.0 and IWMW 2006 Tags AJAX Collaboration http://del.icio.us/gardnerr http://del.icio.us/url/cce31782b323dd77ab48f5ff54ead71c http://del.icio.us/lisbk/iwmw2006-web2.0-panel Tag misuse? Not needed in some areas (e.g. citation analysis, other people interests) So if, e.g., misspellings users still gain benefits.

23. Mashups <ul><li>Mashup - aggregating content from various sources </li></ul><ul><li>IWMW 2006: </li></ul><ul><ul><li>Set up IWMW 2006 Suprgru page </li></ul></ul><ul><ul><li>Mashup from: </li></ul></ul><ul><ul><ul><li>IWMW 2006 Web site </li></ul></ul></ul><ul><ul><ul><li>Third party services such as Blogs, Wikis, bookmarking services, Flickr, search engines, … </li></ul></ul></ul>Web 2.0 and IWMW 2006 Syndication Why? Simple demonstration to encourage debate about the issues. Effort : Simple (fill in a Web form) Experiences : Superglu service not always available (so what, use Netvibes.com, PLEX, …) http://iwmw2006.suprglu.com/

24. Microformats <ul><li>Pages on IWMW 2006 Web site have microformats </li></ul><ul><li>Plugins such as Tails display contact and event details & allow them to be uploaded to Outlook, Google Calendar, etc </li></ul>Further information on microformats given in " An Introduction to Microformats " QA Focus briefing document no. 100" Web 2.0 http://www.ukoln.ac.uk/web-focus/events/ workshops/webmaster-2006/sessions/kelly/ Tags Collaboration

25. Podcasts <ul><li>Podcasts: </li></ul><ul><ul><li>Used at IWMW 2005 (prior to general public interest) </li></ul></ul><ul><ul><li>Podcasting session at IWMW 2006 </li></ul></ul>http://www.ukoln.ac.uk/web-focus/events/ workshops/webmaster-2005/podcasts/podcast.xml Why? Gain experiences at popular technology; explore difference usages and technical and non-technical issues Effort : Non – work being led by workshop facilitator. RSS Users Syndication

26. Communications: Chat <ul><li>IRC chat facility was popular at IWMW 2005/6. </li></ul><ul><li>Gabbly being evaluated: </li></ul><ul><ul><li>If no systems effort available </li></ul></ul><ul><ul><li>On-the-fly chatting </li></ul></ul><ul><li>How long to set up: </li></ul><ul><ul><li>Go to < http://gabbly.com/ > </li></ul></ul><ul><ul><li>Create chat on your institution’s home page </li></ul></ul><ul><ul><li>How long? </li></ul></ul><ul><li>This provides on-the-fly creation of chat facilities  </li></ul>Web 2.0 and IWMW 2006 Too good to be true? Suspicious of anything this simple? See risk assessment page Users Collaboration AJAX Syndication

27. Wikipedia <ul><li>Summary of IWMW series available in Wikipedia: </li></ul><ul><ul><li>High profile location </li></ul></ul><ul><ul><li>Google friendly </li></ul></ul><ul><ul><li>Maximise impact </li></ul></ul><ul><ul><li>Community can update </li></ul></ul><ul><ul><li>Good guys seem to win (and I’ve now a Wikipedia track record) </li></ul></ul><ul><ul><li>CC rights assigned </li></ul></ul><ul><ul><li>Clean URI </li></ul></ul><ul><ul><li>May provide stable URI </li></ul></ul>http://en.wikipedia.org/wiki/IWMW Clean, stable URIs? Mashups, integration, annotation, etc. helped by use of clean (e.g. application independent) and stable URIs URIs Wikis Collaboration

28. IWMC <ul><li>Institutional Web Management Workshop (IWMW): </li></ul><ul><ul><li>Highly successful event for community </li></ul></ul><ul><ul><li>10 workshops held since 1997 </li></ul></ul><ul><ul><li>IMWM 2006 and website-info-mgt email discussion: we're a community; let's do more  </li></ul></ul><ul><li>Suggestions: </li></ul><ul><ul><li>Let's build on IWMW success </li></ul></ul><ul><ul><li>Let's support a IWMC (IWM Community) </li></ul></ul><ul><ul><li>Based on Web 2.0 principles: </li></ul></ul><ul><ul><ul><li>User-focussed  Trust </li></ul></ul></ul><ul><ul><ul><li>User responsibility </li></ul></ul></ul><ul><ul><ul><li>Lightweight centralised coordination, but not control </li></ul></ul></ul><ul><ul><ul><li>Benefits of social networking </li></ul></ul></ul><ul><ul><ul><li>… </li></ul></ul></ul>Next Steps

29. Next Steps <ul><li>What can you do? </li></ul><ul><ul><li>Contribute to Wikis </li></ul></ul><ul><ul><li>Blog and share your experiences </li></ul></ul><ul><ul><li>Set up community Blogs </li></ul></ul><ul><ul><li>Use Creative Commons </li></ul></ul><ul><ul><li>Map your buildings, create appropriate metadata; integrate with Google Maps </li></ul></ul><ul><ul><li>Use microformats for events; … </li></ul></ul><ul><ul><li>… </li></ul></ul><ul><li>You can also think locally and act globally: </li></ul><ul><ul><li>Address your local and regional needs </li></ul></ul><ul><ul><li>And share with the wider community </li></ul></ul>What do you suggest? Next Steps

30. Summary <ul><li>We have seen: </li></ul><ul><ul><li>Several lightweight example of how Web 2.0 technologies can be used </li></ul></ul><ul><ul><li>Examples of the benefits of Web 2.0 attitudes (user-focus; benefits of collaborative approaches; trust) </li></ul></ul><ul><ul><li>Ways of minimising risks and costs </li></ul></ul><ul><ul><li>Use of Web 2.0 in our institutions can be helped by a IWMC with a Web 2.0 ethos </li></ul></ul>Conclusions " Do not ask what the community can do for you, ask what you can do for the community "