Designing For Content Rich Sites


Published on

Webpages, research guides from Springshare’s LibGuides, licensed content, full-text journals, subject experts, digital collections ... and books online and offline. How is a library patron to figure out what’s what in this complex environment? Using independently developed tools from various systems to build a seamless whole, the UM library rebuilt its website, bringing the information patrons want into the forefront and the byzantine path to get it in the background. Speakers share results of extensive user studies, how they iteratively designed the site, and discuss the opensource technologies (Solr, Lucene, Drupal, XML, VuFind) that make it work. Mike Creech, Karen Reiman-Sendi, and Ken Varnum of the University of Michigan Library.

Published in: Technology, Design
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Bold for titles; no italicsNot-bold for slide textKRS:We’d like to thank you for the opportunity to talk about our project to design a content-rich academic library web site.We will be presenting information about our web site redesign project for the next several minutes, and will happily take questions at the end.
  • Designing For Content Rich Sites

    1. 1. Designing for Content-Rich Sites<br />Mike Creech<br />Karen Reiman-Sendi<br />Ken Varnum<br />University of Michigan Library<br />Internet Librarian 2009<br />
    2. 2. Introduction<br />Background<br />Usability Process & Design Process<br />Technologies Used<br />Observations & Lessons<br />
    3. 3. Where We Started<br />
    4. 4.
    5. 5.
    6. 6. Re-Architecting the Site<br />Web Team charge: allow the Dean to find stuff more easily<br />“Information, not location”<br />Harness work with VuFind, LibGuides<br />
    7. 7. Seeking/Setting a Direction<br />Information Gathering<br />Surveys<br />Focus Groups <br />Advisory Groups <br />Drafting Blueprints<br />Taxonomy<br />User Interface<br />Technologies<br />
    8. 8. Typical Development Process<br />Analysis<br />Maintenance &<br />Updating<br />Spec Building<br />Design &<br />Development<br />Promotion<br />Coding<br />Testing<br />
    9. 9. Our Development Process<br />Data Collection<br />& Analysis<br />UI Design<br />Milestone<br />Release<br />User Testing & Feedback<br />Content Migration<br />SystemDevelopment<br />
    10. 10. The Foundation<br />We  open source software<br />Preference for building over buying<br />Trend toward customization of generic tool<br />We have in-house capability to customize<br />Drupal, VuFind, Solr<br />But use more than open source<br />Still live in a vendor-driven environment<br />Metalib, EZProxy, SFX, Aleph ILS<br />
    11. 11. Our Tool Box<br />
    12. 12. Today’s Gateway<br />
    13. 13. Search<br />
    14. 14.
    15. 15.
    16. 16.
    17. 17.
    18. 18.
    19. 19. Articles Search<br />
    20. 20.
    21. 21. Catalog Search<br />
    22. 22. Browse<br />
    23. 23.
    24. 24.
    25. 25.
    26. 26.
    27. 27.
    28. 28. Get Help<br />Contact a librarian<br />Find documentation and guides<br />Workshops & tutorials<br />
    29. 29. Observations<br />Ejournals list, not just search<br />QuickLinks<br />My Account<br />Being ‘green’: reusing & recycling code and taxonomy<br />
    30. 30. Lessons<br />Top-down process can work<br />Legacy content is a two-edged sword<br />Service providers can be helpful<br />
    31. 31. What’s Next?<br />Respond to outcomes from usability testing and patron feedback<br />Future tools and functionality -- i.e., article discovery<br />Building increasingly personalized services on top of new foundation<br />
    32. 32. Q&A <br />Mike Creech<br />Web Content Manager<br /><br />Karen Reiman-Sendi<br />Digital Information Services Librarian<br /><br />Ken Varnum<br />Web Systems Manager<br /><br />Slides<br /><br />