Minutes of June 23, 2008 Meeting

Present:

Ka-Neng Au, Bob Nahoury, Sam McDonald, Stephanie Bartz, Karen Hartman, Rebecca Gardner, Laura Mullen, Dave Hoover, Valeda Dent

1) WAC's Goals and Direction

Expected outcome: clarify future plans for WAC
- (See below)

2) Website Redesign

Background: review suggestions from Website usability study
Expected outcomes: consider next steps
- (See below)

3) Indexes and Databases (McDonald)

Background: determine status of database description review
Expected outcome: distribute new assignments for database description review
- No new assignments were given out. People were asked to work on the ones from the last distribution.

4) Webmaster Report (McDonald)

Expected outcome: review completed tasks and share information

• Link to IRIS Guide
  http://www.iris.rutgers.edu/uhtbin/cgisirsi/0/0/0/1/504/X
  from home page, searchcatalogs.shtml page
• Link to Faculty Emeritus page
  http://www.libraries.rutgers.edu/rul/lib_servs/faculty_emeriti.shtml
  from Faculty services page
• Link to Libx Toolbar page
  http://www.libraries.rutgers.edu/rul/tools/toolbar/toolbar.shtml
  from Research Resources, Faculty services page

5) Systems Report (Hoover)

Expected outcome: information sharing

• Drupal installation required on the main libraries web server. Gathering applications versions and module configuration used on the development machine. Installation needs to be done in July for expected content move in August.
• Still working on connect button links prompting for login. Hope to have new files in place soon. Once all new files are in place Au will send a message to RUL_EVERYONE about the change and Sam will be advised on how to implement.
• The Ask a Librarian service had to be moved to a Secure (SSL) web server to protect the submission of sensitive ID numbers when registering barcodes and having PIN's assigned. The existing reg_pin.shtml was left in place on the libraries web server, but the form submission at the bottom was moved to the secure server. Due to the dual nature of PIN and ASK a Librarian queries being processed by the same software code, the destination of AAL questions being sent was also pointed to the secure server. Finally so that people using the software to respond to questions would also by prevented from showing ID numbers in plain text the URL for staff to use was also changed to use the secure server.

6) Instructional Report (Haynes)

Expected outcome: information sharing
- No report

7) IPAC report (Bartz)

Expected outcome: information sharing

• Oracle upgrade went ok.
• Preparing for the Item type switch over
• New books list is on hold until after Item type switch

8) Other Announcements or Updates (all)

1) WAC's Goals and Direction

• How did group come into being?
  • Create menu systems to provide access to services for users. Initially done on the central info system using text menus, migrated through use of the gopher system to its current version being delivered by as web pages.
  • Terms of service for members not clear, they don't seem to lapse.
  • Was under the direction of Public Services Council, but where will it fit now with the advent of new councils?
  • Membership is taken from within the library faculty/staff only. Need student involvement, new people and ideas.

• How does the website committee function what is its role?
  • We are to advise others as to where their content should be on the web pages. We are not the actual content creators.
  • We stress the importance of having up to date Research Guides for all of our subject disciplines.
  • Due to the magnitude of the website we try to work with other faculty and staff to take ownership and to maintain their web pages. Without some group overseeing this pages would become stale with many broken links.
  • Group discussion/debate about placement of links on website keeping in mind existing structure. Try to avoid haphazard placement of links at top level.
  • Monthly meetings but ability to use email for discussion leads to minimal lag time to get important content up.
  • Work on the picky details of content placement and inclusion on the website. Look at things from a system wide and website wide perspective.

• What should we be doing?
  • Need to get better feedback on problems with the website. Complaints that things are hard to find without specifics are hard to followup on. Need solutions that work for the website as a whole, not just to address one concern.
  • Usability capabilities. Who and how do we conduct usability studies? We have in the past done limited studies conducted by members of the web committee, but they take alot of time and need to be targeted to the right population. How do we get usability testing regularized across the whole website?
  • Can we conduct regular surveys of our users through the use of online point of service questionnaires? Would a tool like MINES be helpful?
  • Should we look at the library web sites of peer institutions? It was thought that this is a Hit or Miss proposition. You will always find one good and bad. Want to define for ourselves what our needs are.
  • Users are not trained as researchers coming into college. How can we educate on the language used on the website?
  • Committee should continue. Advisory to Valeda or to new councils or as subset of User services? Needs to be determined.
  • Add a suggestion box option to the website.

2) Website Redesign (Valeda)

• Start in earnest this summer. It will take a long time. Last redesign 4yrs ago, 4th redesign in 10 years. Next redesign will be complex. Work of redesign will be contracted out. Will look for someone who will work within the confines of our Information Architecture. The contracted work will revolve around interface design issues only. Content will still come from internal sources. Feelers will be put out to firms that do library websites and have knowledge of drupal. Main goal is to enhance the end user experience.
• Integrate information provided from the SCILS student review and designs that were conducted this past semester.
• We are looking for more longevity we don't want to have to redesign in 4 years.

Questions

• Will redesign use SCILS student review?
  Yes in a small way, but many more users will be contacted for feedback and needs assessment. WAC will manage feedback from stake holders in the redesign effort.
• Will it encompass staff pages as well?
  We will talk about this as the desire is to have one look and feel for public and staff content.
• Will there be funding for a consultant?
  As the redesign is a top priority it is expected that funding will be forthcoming.
• If money is found, what is expected of consulting firm?
  Do everything. Usability testing, gathering feedback from our users and all stake holders that have a need to use our website. Using all of this information to follow through with one design that works for all. We don't won't the work to be fragmented between multiple groups.
• Should a student be added to WAC?
  Yes
• What follow through is expected of the firm when their work is completed?
  No surprises after they are gone. A team from RUL will work closely with the firm to assure they know how to support and update website content and design.
• What is the time line?
  Begin talking to firms this summer. Define what we want and look for firms that can provide it. Done redesign by end of 2009. This is the ideal, but not likely.
• How many firms?
  A number. Not traditional web design. Looking at current information architecture, user experience, human factors. Fewer firms do this holistic approach.
• Will redesign be piecemeal or rolled out as a whole?
  Check with public services. There may be a need to roll out pieces for wider user feedback.
• Level of look and feel of the website?
  Will be Level 1 University website. Not oversimplified or based on other cookie cutter work done by the firm in the past.
• Wait on the consultant or do our work first?
  We will need to start our part as it has to be done anyway, knowing that things may change over time.
• Will consultant be charged with looking a website display on new technology devices (ipods etc..) ?
  Yes that should be considered.

Next agenda will include further defining of website design and the structure of WAC.

Next meetings 7/21, 8/11, 9/15, 10/20, 11/17, 12/15