Website redevelopment at the State Library of Victoria

794 views

Published on

A presentation to staff at the State Library of Victoria early in the process of redeveloping our websites. Presented June 2008.

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
794
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
11
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Website redevelopment at the State Library of Victoria

  1. 1. Planning the new web order Kelly Gardiner, Web Services Manager (extension 7408) ‘ Title’on this keyline. Arial Bold 36 pts
  2. 2. SLV status quo <ul><li>SLV web site last redeveloped 2004 </li></ul><ul><li>Catalogues, databases, applications all separate </li></ul><ul><li>Vicnet redevelopment underway </li></ul><ul><li>Legacy sites: A Place Called Victoria </li></ul><ul><li>Partner sites: Victorians at War </li></ul><ul><li>User focused sites: inside a dog, Your Treasures </li></ul><ul><li>New sites: Mirror of the World, Learning zone </li></ul>
  3. 3. Issues & opportunities <ul><li>Our needs have changed </li></ul><ul><li>Users’ needs have changed – and so have their expectations ( who’s sick of hearing about Google? ) </li></ul><ul><li>The web has changed and changes every day </li></ul><ul><li>Our site structures are getting creaky </li></ul><ul><li>User experience varies across our sites and applications </li></ul><ul><li>We spend a lot of time making things to compensate </li></ul><ul><li>We’ve got a million ideas. </li></ul>
  4. 4. Web Strategy objectives <ul><li>The State Library of Victoria’s web sites will: </li></ul><ul><li>Be user-centred </li></ul><ul><li>Provide relevant, accurate, high quality, verifiable and objective information </li></ul><ul><li>Be efficient and sustainable </li></ul><ul><li>Support a sense of community </li></ul><ul><li>Reflect the Library’s slv21 vision </li></ul><ul><li>Be creative, dynamic, and content rich </li></ul><ul><li>Be reliable, secure and adaptable </li></ul><ul><li>Raise awareness of the Library’s collections and services </li></ul><ul><li>Meet Government legal requirements. </li></ul>
  5. 5. The web goes wild <ul><li>The new web can deliver content and services dynamically – free of data source or system constraints </li></ul><ul><li>It’s about real networking: drawing information from disparate sources and providing it in entirely new ways or places </li></ul><ul><li>Data flows where it’s needed </li></ul><ul><li>We can adapt to users’ workflows, rather than forcing them to work around us </li></ul>
  6. 11. What are our users’ tasks? <ul><li>Find </li></ul><ul><li>Analyse </li></ul><ul><li>Annotate </li></ul><ul><li>Publish </li></ul><ul><li>Comment </li></ul><ul><li>Cite </li></ul><ul><li>Bookmark/note </li></ul><ul><li>Learn </li></ul><ul><li>Organise </li></ul><ul><li>Visit </li></ul><ul><li>Collect/copy </li></ul><ul><li>Collaborate </li></ul><ul><li>Teach </li></ul><ul><li>Share </li></ul><ul><li>Explore </li></ul><ul><li>Register </li></ul><ul><li>Read </li></ul><ul><li>Describe/review </li></ul><ul><li>Organise </li></ul><ul><li>Compare </li></ul><ul><li>Enjoy </li></ul>
  7. 12. What can we do better than anyone else? <ul><li>We can tell the story of Victoria </li></ul><ul><li>We have sensational collections </li></ul><ul><li>We support research </li></ul><ul><li>We answer questions </li></ul><ul><li>We teach – and help others teach </li></ul><ul><li>We are part of Victoria’s cultural and community life </li></ul><ul><li>We know a lot about books, maps, pictures, manuscripts (and arts, and history, and Australiana, and newspapers, and genealogy, and…) </li></ul><ul><li>We’re digitising fantastic stuff all day every day </li></ul>
  8. 13. How do we bring tasks & web together? <ul><li>Figure out who’s in our key user groups </li></ul><ul><li>Identify their goals and tasks </li></ul><ul><li>Match our services & information to people’s tasks & interests: offer real benefits </li></ul><ul><li>Get information and services to them, when and where they need them </li></ul><ul><li>Better reflect and project our collections, events, programs and resources </li></ul><ul><li>Match our online offering to our specialist collections </li></ul><ul><li>Integrate and co-ordinate our efforts </li></ul><ul><li>Provide many pathways into the same resources </li></ul><ul><li>Engage our users and communities </li></ul>
  9. 17. But seriously… how? <ul><li>Treat content, data, catalogue records – everything – </li></ul><ul><li>as modules that can be used and re-used </li></ul><ul><li>New information architecture (SLV and Vicnet) </li></ul><ul><li>Offer a seamless and painless user experience </li></ul><ul><li>Provide engagement opportunities (simple – like tags, and complex – like research communities) </li></ul><ul><li>Provide content that’s personalised, customised, timely and dynamic </li></ul><ul><li>Solve registration, sign-in issues </li></ul><ul><li>Allow access to all SLV resources from any site </li></ul><ul><li>Focus on key content areas </li></ul><ul><li>Provide smart search across sites and catalogues </li></ul>
  10. 18. Possible content areas <ul><li>Victorian stories and history </li></ul><ul><li>Books and ideas </li></ul><ul><li>Family history </li></ul><ul><li>Schools and kids </li></ul><ul><li>Research & resources </li></ul><ul><li>Community information (Vicnet) </li></ul>
  11. 19. ‘ Body text’ on this keyline. Arial 24 pts
  12. 20. Process <ul><li>Workshops – general and specific </li></ul><ul><li>Stakeholder and specialist input </li></ul><ul><li>Training </li></ul><ul><li>Industry research </li></ul><ul><li>User research </li></ul><ul><li>Iterative development </li></ul><ul><li>Test prototypes and models with users </li></ul><ul><li>Roll out tools and content over time </li></ul>
  13. 21. Discussion <ul><li>What can we do better than anyone else? </li></ul><ul><li>Gateway concept – what do you think? </li></ul><ul><li>Which gateways? Should we look at others? </li></ul><ul><li>(Delve down into one if you want) </li></ul><ul><li>What core elements should users always see? </li></ul>

×