Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

JISC-PoWR Project: Web 1.0 Preservation


Published on

Presentation given at second JISC-PoWR Workshop run as part of the Institutional Web Management Workshop (22-24th July 2008).

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

JISC-PoWR Project: Web 1.0 Preservation

  1. 1. UKOLN is supported by: The JISC PoWR Project Preserving Web 1.0 Resources Marieke Guy, UKOLN IWMW 2008 23 rd July 2008
  2. 2. The JISC-PoWR Project <ul><li>JISC Preservation of Web Resources project </li></ul><ul><li>Focus on digital preservation issues of relevance to UK HE/FE Web management community </li></ul><ul><li>5 months (May – September 2008) </li></ul><ul><li>2 partners: UKOLN and ULCC + friendly lawyer </li></ul><ul><li>Aim is to raise awareness amongst the Web manager community of the need to incorporate preservation strategy into key stages of the web management process </li></ul><ul><li>Identify, share and seek to embed best practices! </li></ul><ul><li>3 Workshops: London, Aberdeen, Manchester, </li></ul><ul><li>Key resources: briefing papers, case studies and handbook </li></ul><ul><li>Blog - </li></ul>
  3. 3. Why Bother Preserving? <ul><li>Preservation challenge </li></ul><ul><li>Preservation has never been easy, people tend to live in the now </li></ul><ul><li>Web resources present additional challenges </li></ul><ul><li>Why bother? </li></ul><ul><ul><li>Uniqueness </li></ul></ul><ul><ul><li>Audit </li></ul></ul><ul><ul><li>Authenticity </li></ul></ul><ul><ul><li>Money </li></ul></ul><ul><ul><li>Heritage </li></ul></ul><ul><ul><li>Embarrassment! </li></ul></ul>
  4. 4. The Challenges <ul><li>Low priority </li></ul><ul><li>Unsure on whose responsibility it is </li></ul><ul><li>Complicated – Web is big, transient, dynamic </li></ul><ul><li>Gap of understanding between different communities </li></ul><ul><li>What do we preserve? Selection decisions </li></ul><ul><li>What makes a Web site (bits or essence)? </li></ul><ul><li>Technical issues and dependencies </li></ul><ul><li>Legal issues </li></ul><ul><li>Is it worth preserving anyway? </li></ul><ul><li>Web 2.0 </li></ul>
  5. 5. Scenario 1: Your Home Page <ul><li>It is your institution’s anniversary… </li></ul><ul><li>Would like an example of how the institution’s Web site has developed since launch </li></ul><ul><li>Currently only anecdotal evidence/tacit knowledge </li></ul><ul><ul><li>CMS brought in, search added </li></ul></ul><ul><ul><li>Changes in navigation, branding </li></ul></ul><ul><ul><li>Accessibility, language, content </li></ul></ul><ul><ul><li>Interactive elements, multimedia </li></ul></ul><ul><li>Use the Internet Archive’s Way Back machine </li></ul><ul><li>PicLens plugin, automated rolling display </li></ul>
  6. 6. <ul><li> </li></ul>
  7. 7. Scenario 2: Losing Content <ul><li>The funding finishes </li></ul><ul><li>Project staff leave, partnership dissolves </li></ul><ul><li>Hosting agency upgrades operating system, resulting in scripts to access resources from backend database are broken </li></ul><ul><li>User finds page with invitation to project launch and travels to meeting. Event took place in 2002! </li></ul><ul><li>Invoice for domain name is not paid, as administrator has left </li></ul><ul><li>Web site domain taken over by porn company </li></ul><ul><li>Prime Minister picks up pen containing project URL and visits pornographic Web site </li></ul>
  8. 8. It Has Happened: Webtechs <ul><li>Software company which hosted early HTML validation service </li></ul><ul><li>In 1998/99 confusion over payment of domain name </li></ul><ul><li>March 1999 company receives many messages saying validation service is now a porn site </li></ul><ul><li>Over 30,000 links to Web site! </li></ul><ul><li>Sept 1999 porn company agrees to sell domain name back to Webtech </li></ul>See <>
  9. 9. Facing the Challenges <ul><li>1) Protect Web site short to medium term </li></ul><ul><ul><li>Mothball your Web site </li></ul></ul><ul><ul><li>Get senior management on board </li></ul></ul><ul><li>2) Manage Web site content as part of an RM programme </li></ul><ul><ul><li>Identify your resources </li></ul></ul><ul><ul><li>Collaborate – University of Bath RM and WS Director </li></ul></ul><ul><ul><li>Choose the appropriate approach (or approaches) </li></ul></ul><ul><ul><li>You may not need to keep everything </li></ul></ul><ul><li>3) Preserve Web sites and Web resources permanently </li></ul><ul><ul><li>Something for the future </li></ul></ul>
  10. 10. Mothballing Your Web Site (1) <ul><li>Run a link check across the Web site. </li></ul><ul><li>Fix broken internal links and external links </li></ul><ul><li>Run HTML (and CSS) validation checks across the Web site. </li></ul><ul><li>Run an accessibility check across the Web site. . </li></ul><ul><li>You should also address technical areas: </li></ul><ul><ul><li>Remove any backend scripts which are no longer needed (e.g. online booking forms for old events). </li></ul></ul><ul><ul><li>Remember that scripts, etc. are liable to go wrong. Ensure that applications are configured to break gracefully and provide meaningful errors </li></ul></ul>See < documents/briefings/briefing-04/>
  11. 11. Mothballing Your Web Site (2) <ul><li>You should also address the content of your Web site </li></ul><ul><li>Clarify the status of the Web site on the home page. </li></ul><ul><li>Ensure the tense of the content reflects the position i.e. don't say &quot; This project will … &quot; </li></ul><ul><li>Ensure that contact details will remain valid i.e. provide generic email addresses not an individuals </li></ul><ul><li>Remember that many users will arrive deep in your Web site (e.g. using Google). </li></ul><ul><li>If necessary use CSS to flag all pages with a watermark </li></ul>This Web site is no longer maintained. See home page for details Web 1.0
  12. 12. Mothballing Toolkit <ul><li>UKOLN developed a QA methodology by QA Focus work which was funded by JISC </li></ul><ul><li>We developed a lightweight self-assessment toolkit </li></ul> toolkit/mothballing-01/ Web 1.0
  13. 13. Any Questions?
  14. 14. Breakout Session 1 <ul><li>Reflecting on some of the issues mentioned, in groups think </li></ul><ul><li>about Embedding Best Practices. </li></ul><ul><li>What are the barriers to implementing a Web Resource Preservation Strategy in your Institution? </li></ul><ul><li>How can you address these barriers? </li></ul><ul><li>How can you take some of the techniques mentioned and apply them within your institution? </li></ul>