a centre of expertise in digital information management let’s do it now: mainstream uses of...

A centre of expertise in digital information management

www.ukoln.ac.uk

Let’s Do It Now: Mainstream Uses Of Collaborative Technologies

Brian KellyUKOLNUniversity of [email protected]

UKOLN is supported by:

http://www.ukoln.ac.uk/web-focus/events/conferences/edinburgh-2006-11/http://www.ukoln.ac.uk/web-focus/events/conferences/edinburgh-2006-11/

Acceptable Use PolicyRecording/broadcasting of this talk, taking photographs, discussing the content using email, instant messaging, Blogs, SMS, etc. is permitted providing distractions to others is minimised.

Acceptable Use PolicyRecording/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)

ed-itfutures-2006 tag used in del.icio.us ed-itfutures-2006 tag used in del.icio.us


www.ukoln.ac.uk

2

Contents

Web 2.0 – A RecapWeb 2.0 – Let’s Use It

• Blogs• Wikis • Communications• Culture of openness• Always beta

Addressing Organisational barriers• Understanding our culture• Risk assessment and risk management• Deployment strategies


www.ukoln.ac.uk

3

Web2MemeMap, Tim O’Reilly, 2005

Characteristics Of Web 2.0

• Network as platform• Remix and mash-ups

Syndication (RSS)• Architecture of participation

Blogs & Wikis Social networking Social tagging

(folksonomies)• Trust and openness• Always beta• Clean URIs

Characteristics Of Web 2.0

• Network as platform• Remix and mash-ups

Syndication (RSS)• Architecture of participation

Blogs & Wikis Social networking Social tagging

(folksonomies)• Trust and openness• Always beta• Clean URIs

Web 2.0

What Is Web 2.0?

Marketing term (derived from observing 'patterns') rather than technical standards - “an attitude not a technology”

Web

2.0


www.ukoln.ac.uk

4

Takeup Of New TechnologiesThe Gartner curve

Developers

Rising expectations

Trough of despair

Service plateau

Enterprise softwareLarge budgets…

Early adopters

Web

2.0

ChasmFailure to go beyond developers & early adopters (cf Gopher)Need for:

• Advocacy• Listening to users• Addressing concerns• Risk management• Deployment strategies• …

This talks looks at approaches for avoiding the chasm

This talks looks at approaches for avoiding the chasm

CMSVLE…

Web 2.0PLE…


www.ukoln.ac.uk

5

Blogs – A Steer From Management

Warwick’s Blog service illustrates how an institutional Blog can provide a thriving community (and isn’t this a key part of the university experience?)

Web

2.0

http://blogs.warwick.ac.uk/http://blogs.warwick.ac.uk/http://blogs.warwick.ac.uk/...http://blogs.warwick.ac.uk/...

John Dale’s Blog shows how:

• IT Service staff can engage with their users

• A more egalitarian approach - the IT Manager know something about IT, but users may know more! (this reflects current learning orthodoxies)

Michael Webb, Newport is an example of a Blogging IT Director

Michael Webb, Newport is an example of a Blogging IT Director


www.ukoln.ac.uk

6

Blogs – Grassroots Approach

Science librarian at University of Bath has set up a Blog on Blogger

Users love it – “Why isn’t there a Blog for the rest of the library”

Q: Should I be doing this?

A: No – make a recommendation to your manager; write a proposal; if accepted then WG set up; it reports back and recommendations probably deferred!

This is a good example of Web 2.0 philosophies of “user-focus”, “always beta” and “trust”: trust your professionals do be innovative in supporting their users & to be flexible & learn from experiences

This is a good example of Web 2.0 philosophies of “user-focus”, “always beta” and “trust”: trust your professionals do be innovative in supporting their users & to be flexible & learn from experiences

http://bathsciencenews.blogspot.com/http://bathsciencenews.blogspot.com/


www.ukoln.ac.uk

7

Wikis – Grassroots Approach

Same librarian used a Wiki for a group planning production of a Podcast guide to the Library:

• User engagement in process

• Users (including students) make use of emerging technologies (Wiki, Podcasts)

Advantages:• No waiting for IT Services

evaluation of Wiki software• Can feed experiences back to

IT Services• Can address non-IT issues

Grass roots experiences can feed into process for an institutional solution, including technical; training & strategy issues

Grass roots experiences can feed into process for an institutional solution, including technical; training & strategy issues

http://bathlibpod.wetpaint.com/http://bathlibpod.wetpaint.com/


www.ukoln.ac.uk

8

Wikis – Institutional Approach

There’s an awareness of a need for institutional Wiki strategies.Addressed at UKOLN’s “Exploiting The Potential Of Wikis” workshop, Nov 2006Need for Wikis seems to be agreed. Challenges:

Wiki strategy options:• Centralised Wiki provision (and the

best is …)• De-centralised Wiki provision (horses

for courses)• Bundled Wiki provision (it comes with

the VLE)• Out-sourced Wiki provision

(Thatcherite or Web 2.0 network as an application provider)

Confluence and MediaWiki seemed preferred options at workshop.

Confluence and MediaWiki seemed preferred options at workshop.

http://wiki-workshop-2006-11.wetpaint.com/http://wiki-workshop-2006-11.wetpaint.com/


www.ukoln.ac.uk

9

Communications – Skype Skype:

• Evil bandwidth-stealing proprietary software – use SIP software

• Innovative, easy-to-use, immensely popular software – and all my friends & colleagues use it

Case studies: • Ban • Buy network shaper box to “remove

illegal P2P traffic in order to provide quality Skype service to users”

• Respond to user concerns in halls by banning, but allow managed use on campus, until better solution available

• Educate user: don’t use over WiFi; … (AUP at UKOLN Wiki workshop)

Just-in-time accessibility: participants missed train, but used Skype (and Gabbly) to take part in Accessibility Summit. Conclusion: have Skype ID just-in-case (and as carbon-quota plan)!

Just-in-time accessibility: participants missed train, but used Skype (and Gabbly) to take part in Accessibility Summit. Conclusion: have Skype ID just-in-case (and as carbon-quota plan)!


www.ukoln.ac.uk

10

The BarriersThere are barriers to the deployment of Web 2.0:

• It's scary: I've just mastered Dreamweaver; we've just spend a lot of money on a CMS; …

• It's immature: I've heard it all before (XML, Semantic Web, …) . This is just new hype

• There are legal risks: Copyright infringement; data protection; protection of minors; …

• Infringement of guidelines: Web 2.0 infringes our AUP; accessibility legislation; e-Gov legislation; ..

• Institutional inertia: We'd like to do it but we have large existing systems; reluctant colleagues; …

• Culture: We’ve always first evaluated & then mastered the software; how can we support multiple Web 2.0 service? And it needs to be open source so we can tweak it

Web

2.0

Bar

rier

s

How do we go about addressing these barriers? (And should we – what if the concerns are legitimate!)

How do we go about addressing these barriers? (And should we – what if the concerns are legitimate!)


www.ukoln.ac.uk

11

Addressing The Barriers

It breaks accessibility guidelines; open standards; AUPs; etc.

• There is a need to ensure existing guidelines & interpretations in these areas are flexible enough to take into account technological developments, emerging usage patterns, etc

• See UKOLN’s holistic approach to Web accessibility and contextual approach to standards

• Need for an Acceptable Use Policy Process (AUPP) to ensure that AUPs aren’t used as a control mechanisms but as a means of maximising benefits of services for IT users & providers

Note that HE is good at critiquing orthodox thinking & developing richer models,

Note that HE is good at critiquing orthodox thinking & developing richer models,


www.ukoln.ac.uk

12

Nobody Likes Us - The Users' View

IT Services – prvoding the answers or blocking the users?• Don't understand learning and teaching and think that

students only ever use the Web for messing around.• 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.)

• 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.

• Consultation usually consists of them telling you what they are going to do. If you tell them what you want they don't listen!

IT S

ervi

ces

Bar

rier

Do these comments ring any bells? If not, how can you be sure?Do these comments ring any bells? If not, how can you be sure?


www.ukoln.ac.uk

13

Beware The IT Fundamentalists

We need to avoid simplistic solutions to the complexities:• Open Standards Fundamentalist: we just need XML• Open Source Fundamentalist: we just need Linux• Vendor Fundamentalist: we must need next version of

our enterprise system (and you must fit in with this)• Accessibility Fundamentalist: must do WAI WCAG• User Fundamentalist: we must do whatever users

want• Legal Fundamentalist: it breaches copyright, …• Ownership Fundamentalist: must own everything• Perfectionist: It doesn't do everything, so we'll do

nothing• Simplistic Developer: I've developed a perfect solution

– I don't care if it doesn't run in the real world• Web 2.0 Fundamentalist: Must use latest cool stuff

IT S

ervi

ces

Bar

rier


www.ukoln.ac.uk

14

The Librarian FundamentalistsLibrarians:

• 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?)

• Think that users should be forced to learn Boolean searching & other formal search techniques because this is good for them (despite Sheffield's study).

• Don't want the users to search for themselves (cf folksonomies) because they won't get it right.

• They still want to classify the entire Web - despite the fact that users don't use their lists of Web links.

• 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).

Lib

rary

Bar

rier


www.ukoln.ac.uk

15

Addressing the Barriers

How do we address such barriers:• A change in culture• Being more open (surely what HE & public

sector is about?)• Revisiting AUPs• Developing more sophisticated models for

standards, accessibility, open sources, …• Developing key principles• Ongoing debate and discussion

Cu

ltu

ral

Ch

ang

e


www.ukoln.ac.uk

16

Need To Change Catch Phrases

Computer Says No!

Time to ditch this catch phrase

Wikis? IT Services says noFolksonomies? Library says noSkype? UKERNA says no

Wikis? IT Services says noFolksonomies? Library says noSkype? UKERNA says no

Yer, but, no, but, yer

Time to embrace the ambiguities acknowledged in Vicky Pollard dialectic philosophy

Yer, like Wikis are well cool, but, OK so I copied my homework, but, like I always copy my homework

Yer, like Wikis are well cool, but, OK so I copied my homework, but, like I always copy my homework

Images from BBC Web site

Cu

ltu

re C

han

ge

X


www.ukoln.ac.uk

17

Implement An Open ApproachImplementing an open approach should not be difficult:

• We have tradition of sharing & using OSS• The HE sector is now more open to discussing open

access issues (e-prints, financial issues, …)• Creative Commons (CC) provides a legal framework

What can we do:• Make support services resources available with CC

licence: see paper on "Let's Free IT Support Materials!"• Exploit UKOLN's QA Focus briefing documents:

100+ documents available with CC licence • …

Using other's resources and service may be unpopular (job security, ideology, …). For example, should IT services host email, … when this can be outsourced?

Using other's resources and service may be unpopular (job security, ideology, …). For example, should IT services host email, … when this can be outsourced?

Cu

ltu

ral

Ch

ang

e


www.ukoln.ac.uk

18

Acceptable Use Policies (AUP)

Is Skype Permitted over JANET?"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." (now toned down)

Missing The Point?There may be (religious) debates over the interpretation of UKERNA's words. But

• Did the policy come from God? Is it infallible?

• Why do we hide behind 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.

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.

Rev

isit

ing

AU

Ps


www.ukoln.ac.uk

19

The Need For An AUPP

AUPs:• Shouldn't be cast in stone: technologies change;

usage changes; culture changes (e.g. AUPs banning social use; email; Web; messaging; …)

• Therefore need for mechanisms for changing AUPs and engagement with users

Proposal:• We need an Acceptable Use Policy Process

(AUPP) • We need mechanisms to ensure users can input

into the discussion process• We need more flexibility in our AUPs (e.g. to

reflect blended learning, pervasiveness of IT; …)

Cu

ltu

ral

Ch

ang

e


www.ukoln.ac.uk

20

Avoid Perfection!In higher education we like to investigate limitations of systems (it’s our job). But:

• Need to separate such research from deployment of good enough services

• Need to be more user-centred – if users can do it (at home; in Starbucks; from their memory stick) why can’t IT Services provide similar services (students pay enough!)

An always beta approach: the software and its use may not be perfect, but that’s not a barrier to deployment

Cu

ltu

ral

Ch

ang

e

If the Sun can provide Blogs, it’s very strange if HE can’t!

If the Sun can provide Blogs, it’s very strange if HE can’t!

http://www.thesun.co.uk/portal/site/mysun/

http://www.thesun.co.uk/portal/site/mysun/


www.ukoln.ac.uk

21

Risk ManagementIWMW 2006 has taken a risk management approach to its evaluation of Web 2.0 technologies:

• Agreements: e.g. in the case of the Chatbot.• Use of well-established services: Google &

del.icio.us are well-established & financially stable. • Notification: warnings that services could be lost. • Engagement: with the user community: users actively

engage in the evaluation of the services. • Provision of alternative services: multiple OMPL

tools. • Use in non-mission critical areas: not for bookings! • Long term experiences of services: usage stats• Availability of alternative sources of data: e.g.

standard Web server log files.• Data export and aggregation: RSS feeds, aggregated

in Suprglu, OPML viewers, etc.

Tak

ing

Ris

ks

Note that you also take risks in not providing a service! Will your users go elsewhere?

Note that you also take risks in not providing a service! Will your users go elsewhere?


www.ukoln.ac.uk

22

Safe Experimentation

How can we gain experiences of Web 2.0:• Safe environment• Which minimise risks• Which allow learning

Possibilities:• Encourage enthusiasts• Using technologies at events such as this!• Supporting the services which your users use (e.g.

Google!)• Using services which require minimal effort• Working with your peers elsewhere

Pil

oti

ng

Web

2.0


www.ukoln.ac.uk

23

Conclusions

To conclude:• Web 2.0 can provide real benefits for our users• However organisations tend to be conservative• We therefore need:

Advocacy To listen to users' concerns To address users' concerns e.g. through a risk

management approach

• We can all benefit by adopting Web 2.0 principles of openness and sharing. So let us: Share our advocacy resources, risk management

techniques, etc. Have a social network with peers based on openness,

trust, collaboration, ..

Co

ncl

usi

on

s

a centre of expertise in digital information management let’s do it now: mainstream uses of...

Documents