Web 2.0 and Social Web Challenges


Published on

This talk looked at the possible obstacles to using social web services in a cultural heritage institutional environment. Possible solutions were suggested for a number of potential obstacles.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Web 2.0 and Social Web Challenges

  1. 1. Web 2.0 and Social Web Challenges Ann Chapman UKOLN University of Bath Bath, UK UKOLN is supported by: This work is licensed under a Attribution-NonCommercial-ShareAlike 2.0 licence (but note caveat) About this Talk This talk will focus on problems you may encounter and how you may be able to overcome them. http://www.ukoln.ac.uk/cultural-heritage/events/social-web-birmingham-2010-10/ Twitter: http://twitter.com/ukolnculture/ Email: [email_address]
  2. 2. Locked Door or Country Stile? Lack of Resources Technical Issues Legal issues Understanding
  3. 3. Lack of Money <ul><li>Web 2.0 </li></ul><ul><ul><li>Generally free to use </li></ul></ul><ul><ul><li>Sometimes extra level means fees </li></ul></ul><ul><ul><ul><li>LibraryThing – 200 items free, over that small fee </li></ul></ul></ul><ul><ul><li>Doesn’t require extra equipment </li></ul></ul><ul><ul><li>Opportunity for low cost staff development </li></ul></ul><ul><li>Not completely cost free </li></ul><ul><ul><li>Staff time to set up </li></ul></ul><ul><ul><li>Staff time to run </li></ul></ul>
  4. 4. Lack of Time <ul><li>Plan ahead </li></ul><ul><ul><li>Blogs </li></ul></ul><ul><ul><ul><li>Guest posts (remember contact time) </li></ul></ul></ul><ul><ul><ul><li>Staff or service features </li></ul></ul></ul><ul><ul><li>Use one service to update another </li></ul></ul><ul><ul><ul><li>Either put Twitter feed on Facebook page </li></ul></ul></ul><ul><ul><ul><li>Or send Facebook updates to Twitter </li></ul></ul></ul><ul><ul><ul><li>NB – don’t do both the above </li></ul></ul></ul><ul><ul><li>Keep things simple </li></ul></ul>
  5. 5. Lack of Skills <ul><li>Treat as opportunity for staff development </li></ul><ul><ul><li>Use an existing 23 Things resource? Don’t forget how quickly the Web changes </li></ul></ul><ul><ul><li>Develop your own? </li></ul></ul><ul><ul><li>Listen to podcasts </li></ul></ul><ul><li>Build on skills learnt </li></ul><ul><ul><li>Use wiki for staff manual </li></ul></ul><ul><ul><li>Use blog for project team communication </li></ul></ul><ul><ul><li>Make podcasts (e.g. oral history talks) </li></ul></ul>
  6. 6. Council Firewall <ul><li>The reality </li></ul><ul><ul><li>Useful Webs services do get blocked </li></ul></ul><ul><ul><li>There is dodgy/illegal/dangerous material on the Web </li></ul></ul><ul><ul><li>It may be simple to have a blanket ban </li></ul></ul><ul><ul><li>The good news – councils are re-thinking policy </li></ul></ul><ul><li>Suggested approaches </li></ul><ul><ul><li>We can accept certain levels of risk </li></ul></ul><ul><ul><li>More sophisticated responses are needed </li></ul></ul><ul><ul><li>We should share the approaches we’ve taken </li></ul></ul>
  7. 7. Sustainability Concerns <ul><li>What happens if Web services: </li></ul><ul><ul><li>Are unreliable </li></ul></ul><ul><ul><li>Change their terms & conditions (e.g. Ning was free then started charging in 2010) </li></ul></ul><ul><ul><li>Become bankrupt </li></ul></ul><ul><li>Things to remember </li></ul><ul><ul><li>Services may be unreliable (e.g. Twitter) </li></ul></ul><ul><ul><li>Market pressure can change things (e.g. Friends Reunited became free) </li></ul></ul><ul><ul><li>Banks can go bankrupt too – but we still use them </li></ul></ul><ul><ul><li>Need for risk assessment and risk management </li></ul></ul>
  8. 8. Interoperability Concerns <ul><li>What happens if Social Web services host your data and: </li></ul><ul><ul><li>You can’t get the data back out? </li></ul></ul><ul><ul><li>You only get unstructured or poor quality data back out? </li></ul></ul><ul><ul><li>You can’t get the comments, annotations, tags out? </li></ul></ul><ul><li>There’s a need to: </li></ul><ul><ul><li>Ensure data export capabilities or </li></ul></ul><ul><ul><li>Upload data from an alternative managed source </li></ul></ul><ul><ul><li>Understand limitations of data export / import and make plans around limitations </li></ul></ul>
  9. 9. Accessibility Concerns <ul><li>Social Web services: </li></ul><ul><ul><li>Inaccessible to people with disabilities? People with disabilities and disability activists are using social web services </li></ul></ul><ul><ul><li>Break accessibility guidelines (WCAG)? They are guidelines </li></ul></ul><ul><ul><li>Leave us liable to be taken to court? DDA: Institutions must take ‘reasonable measures’ to ensure people with disabilities are not discriminated against. Is it discriminatory to fail to provide access to services? </li></ul></ul>
  10. 10. Privacy Concerns <ul><li>Think about </li></ul><ul><ul><li>What needs to be private </li></ul></ul><ul><ul><li>How to keep things private </li></ul></ul><ul><ul><li>Use settings provided </li></ul></ul><ul><li>Facebook </li></ul><ul><ul><li>Read the Help pages </li></ul></ul><ul><ul><li>Learn how to manage privacy settings </li></ul></ul><ul><ul><li>Choose what you want to share </li></ul></ul>
  11. 11. Legal Concerns <ul><li>Factors to bear in mind: </li></ul><ul><ul><li>Commercial use : a rights owner who later becomes aware of the use of their work may be more likely to pursue an action for infringement of copyright than if the work is being purely used for educational purposes. </li></ul></ul><ul><ul><li>Particularly sensitive subject areas : music, geographic data, literary works by eminent authors and artistic works including photographs and drawings. </li></ul></ul><ul><ul><li>Is there any track record of the contributor ignoring legal niceties in the past? </li></ul></ul><ul><ul><li>Is there any track record of a particular third party having complained before? </li></ul></ul>
  12. 12. Copyright Concerns <ul><li>R = A x B x C x D </li></ul><ul><li>where </li></ul><ul><ul><li>R is the financial risk; </li></ul></ul><ul><ul><li>A is the chances that what has been done is infringement; </li></ul></ul><ul><ul><li>B is the chances that the copyright owner becomes aware of such infringement; </li></ul></ul><ul><ul><li>C is the chances that having become aware, the owner sues; </li></ul></ul><ul><ul><li>D is the financial cost (damages, legal fees, opportunity costs in defending the action, plus loss of reputation) for such a legal action. </li></ul></ul><ul><li>Prof Charles Oppenheim, Emeritus Professor of Information Science, Loughborough University </li></ul>
  13. 13. Reducing the Legal Risks <ul><li>Approaches </li></ul><ul><ul><li>Have clear and robust notice and take down policies </li></ul></ul><ul><ul><li>Have procedures with a clear address given for complaints </li></ul></ul><ul><li>Example </li></ul><ul><li>JORUM http://www.jorum.ac.uk/policies.html </li></ul>
  14. 14. Develop a Business Case <ul><li>Some tips </li></ul><ul><ul><li>Use a template (West Dumbartonshire) http://www.slainte.org.uk/files/pdf/web2/westdunbartonweb2.pdf </li></ul></ul><ul><ul><li>Be clear about what you hope to achieve </li></ul></ul><ul><ul><li>Background is very important </li></ul></ul><ul><ul><li>Contextualise </li></ul></ul><ul><ul><li>Beef up the business need </li></ul></ul><ul><ul><li>Find great examples </li></ul></ul><ul><ul><li>Aim high – if you don’t ask, you don’t get! </li></ul></ul><ul><ul><li>Use a social media strategy framework </li></ul></ul>
  15. 16. Risks & Opportunities Framework <ul><li>Be specific and document </li></ul><ul><ul><li>Details of specific planned use </li></ul></ul><ul><ul><li>Perceived benefits </li></ul></ul><ul><ul><li>Perceived risks </li></ul></ul><ul><ul><li>Missed opportunities if fail to use social web </li></ul></ul><ul><ul><li>Costs and other resource implications </li></ul></ul><ul><ul><li>Approaches to minimise risks </li></ul></ul><ul><ul><li>Provide evidence for assertions </li></ul></ul>
  16. 17. Think about a Policy Mosman Council (Australia) provides a good example of a lightweight policy
  17. 18. Risk Management <ul><li>What to do: </li></ul><ul><li>Establish Agreements </li></ul><ul><li>Use well-established services (e.g. Twitter, Facebook, Wordpress) </li></ul><ul><li>Notifications: warnings that services could be lost </li></ul><ul><li>User engagement in evaluation </li></ul><ul><li>Provision of alternative services </li></ul><ul><li>Use in non-critical areas (not for bookings) </li></ul><ul><li>Measure – usage stats </li></ul>
  18. 19. Watch, Evaluate and Act <ul><li>IAVE (International Association of Volunteer Effort) was “ founded in 1970 by people who saw volunteering as a means to make connections across cultures ” </li></ul><ul><ul><li>Only has 4 members </li></ul></ul><ul><ul><li>And no discussions </li></ul></ul><ul><ul><li>Worth continuing? </li></ul></ul>
  19. 20. Be Well Informed <ul><li>UKOLN provide briefing papers on Web 2.0 of specific relevance to the Cultural Heritage sector </li></ul><ul><li>Many are introductory – may be useful to pass on to your management team </li></ul><ul><li>Some are on addressing barriers </li></ul><ul><li>Cultural heritage covers areas of concern </li></ul><ul><li>Stay well informed! </li></ul>UKOLN briefing papers available with Creative Commons licence (over 80 docs published)
  20. 21. More from UKOLN <ul><li>Brian Kelly has posted a number of podcasts on Web 2.0 topics on YouTube </li></ul><ul><li>On YouTube search for ‘brian kelly ukoln’ </li></ul>
  21. 22. Questions <ul><li>Any questions? </li></ul>Name : Ann Chapman Address : UKOLN, University of Bath, BATH, UK Email : a.d.chapman@ukoln.ac.uk Web site : http://www.ukoln.ac.uk/ Blog : http://blogs.ukoln.ac.uk/cultural-heritage/