On Borrowed Time ReInventing a University Library Website

1
On Borrowed Time Re-Inventing a
UniversityLibrary Website
University of Melbourne Library Website Working
Group
2
Once upon a time there was a University Library
website that needed a bit of a make-over . . .
3
. . . and everyone knew, deep in their hearts,
that more than just a touch of lippy would be
required
4
Cosmetics or Surgery required?

• review assumptions about target audiences
• review the information that can and should be
  supplied on the website
• identify redundancies and illogicalities
• consider policies and procedures for updating and
  maintaining the site
• consider quality control issues

5
Make-over consultants

• So far . . .
• LWWG - Terry Brennan (Melbourne Branches), Amanda
  Finnis (TeLaRS), Eve Young (IRA)
• From now on . . .
• Representatives from Law Library, Collections,
  Special Collections, Archives, Regional Branches,
  Information Access

6
Why?
7
Why?
8
Seriously, why?

• the Library website does not optimally achieve
  its purpose
• The purpose of the Library website is to act as a
  gateway to
• Information about the library
• Access the library services
• Instructional material

9
So just how bad is it?

• difficult to locate services and information
• Go to library front page
• services which could be provided are not e.g.
  more online request forms, email reference
  services, etc.
• duplicate information
• inconsistency of presentation
• content is often out of date and/or inaccurate
• not always accessible

10
How has this come to pass?

• No published standards
• No clear procedures or guidelines
• No ongoing management
• Lack of resources (read dedicated web staff)
• Lack of knowledge/skills
• No dedicated system/server administrator
• Low security
• Not just end-users who have difficulties

11
Whats the plan Stan?

• Interim Re-Build (why interim?)
• Training for all web maintainers
• Total User-Centred Restructure

12
Interim Re-Build

• New site structure
• New templates
• Add metadata
• Fix code (ensure compliance, accessibility,
  convert from HTML 4 to XHTML 1.0)
• Write and apply new CSS
• Liaise with current maintainers

13
The Big Picture

• Ask the users
• Re-Invent

14

• And the issues to be considered are . . .

15
Useability

• Develop methodology and tools for testing
  useability, and conduct useability testing of
  interim site

16
Evaluation

• Develop a comprehensive ongoing evaluation
  framework for the Library website, incorporating
• an online system for feedback
• analysis of data gathered and modification of
  site as appropriate
• review current statistics gathered and decide on
  optimal statistics for the future
• development of a set of Key Performance
  Indicators against which to evaluate the site

17
Standards

• Adopt recommendations of World Wide Web
  Consortium (W3C)
• Accessibility
• All library web pages to conform to Web Content
  Accessibility Guidelines (WCAG) Version 1.0
• HTML
• XHTML 1.0 Transitional to be the standard for all
  library web pages

18
Standards (cont.)

• CSS
• Cascading Style Sheets (CSS) 1.0 to be used for
  the entire library website
• Metadata
• All library web pages to contain metadata as set
  out by the University Metadata Working Group

19
Standards (cont.)

• Software and Tools
• Latest version of Macromedia Dreamweaver
• W3C HTML checker, http//validator.w3.org/
• Bobby, http//www.cast.org/bobby/
• Templates
• Standard library website templates to be
  established

20
Content and Architecture

• Re-think current content design and introduce
  new architecture for an interim website
• Add a site index
• Add a search facility
• Replace all mailto links with a standard mail
  form
• Revamp graphic design of website

21
People

• Authorisers
• Maintainers
• Area Administrators
• Library Web Group
• Troubleshooters

22
Network, darling, network

• Make and maintain links with appropriate other
  bodies within the University, eg. University Web
  Centre, and participate in resource and knowledge
  sharing

23
Quality Assurance

• Recency (dates)
• Develop and introduce an automated system for
  checking expiry dates of web pages.
• Accurate Links
• Develop and introduce an automated system for
  checking links.
• Compliant Code validity
• Develop and introduce an automated system for
  checking for valid code.

24
Quality Assurance (cont.)

• Compliant Code Accessibility
• Develop and promote a user-friendly checklist for
  compliance with WCAG 1.0
• Introduce a system of annual code audits
• Content
• Develop quality content guidelines

25
Quality Assurance (cont.)

• Training
• Site Structure
• XHTML 1.0
• Dreamweaver
• Library Templates
• File Transfer
• Compliant Code
• Writing for the Web

26
Quality Assurance (cont.)

• Workflow
• Introduce regular and emergency workflow
  procedures.

27
Server Issues

• Which server?
• Administrator
• Assign role of server administrator to a
  particular staff member/position.
• Security
• Develop a system of unique usernames and passwords

28
Policy

• Develop and produce a formal policy for the
  updating and maintenance of the University of
  Melbourne Library website.

29
Documentation

• Develop and maintain both electronic and print
  versions of documents covering
• Policy
• Standards
• Procedures
• Training
• Personnel

30
Its all in the timing

• First meeting of library web group April 2002
• Interim site relaunched for Semester 2, 2002
• New user-centred library website launched
  beginning of 2003

31
And they all lived happilyever after . . .
32
(No Transcript)