U.C. Berkeley Library Web

UC Berkeley Library Website Redesign Focus Group Study

Report on UC Berkeley Library Web Site Focus Groups
Spring 2003

Conducted for Web Advisory Group (WAG)
by and


Background

In keeping with its commitment that the new web site be grounded in user-centered design, the Web Advisory Group conducted focus groups with students, faculty, and staff members.  The results provide preliminary input on users' perceptions and preferences for WAG members to consider along with forthcoming data from surveys and usability tests, in making informed decisions as the redesign process moves forward.

This report covers the focus group goals, participants, summary results, and suggestions for next steps. Separate documents, not posted on the web, include compiled comments from all the sessions, detailed notes on each session, and information on the focus group process.

Goals

The goals of these focus groups were to get qualitative information and insights on:

Participants

We conducted three focus groups in March and April 2003, with a total of 19 participants. The first group included 11 library staff from RRC, Instructional Services, several subject specialty libraries, and Technical Services. The second group included 2 upper division undergraduates and 2 graduate students. The third group included 4 members of the Academic Senate Library Committee. Subject interests of students and faculty participants were Public Health, German, Film Studies, Political Science, Biostatistics, Spanish, and Engineering.

Summary Results

Several themes emerged from these sessions. Participants consistently expressed their desire for a site that is rich in content, that integrates multiple resources into a single search and/or menu system, and that adapts to the needs of users at different skill levels or in different disciplines. They also placed a high value on logical organization, consistent navigation, uncluttered design, and understandable terminology. Their heartfelt and oft-repeated advice to us was "simplify, simplify, simplify."

Despite our efforts to define the scope of the discussions, participants tended to conflate all Internet sources, often not making distinctions among the Library web site, catalogs, databases, etc. This is not a mistake on their part; it is how they perceive the online research process. They also envisioned some features that may be technically beyond what we can do at the present time. This report includes their comments without making judgments on relevance or feasibility.

Note: In this report, quotation marks indicate either a verbatim quote or a close paraphrase of the partcipant’s actual comment.

What web sites do participants
find most useful for research?

Comments varied based on both the subject and the library expertise of the participant.

Undergraduates tended to seek specific items identified by their professors, or absent this, often started with Google. One undergraduate, whose work is topical, often begins with SFGate.

Graduate students and professors were more likely to try to identify the experts and core materials on a topic. The latter process often involved a process to identify seminal works (on a new subject) and/or to identify resources with extensive bibliographies to provide clues. Some graduates and faculty reported heavy use of professional society web pages or other web sites developed by persons knowledgeable in the field (including the library’s subject-related page). Several mentioned the importance of listservs and newgroups for staying current with both who is working in the field and for staying apprised of new developments and thinking.

Several experienced scholars reported using Google-type web searches not so much to identify the center of discussion on a topic, but to identify "windfall apples" and "atypical responses". One professor reported routinely using Google, "to get an idea of what students may have seen."

Content
(what topics, facts, types of information need to be available)

Participants placed more emphasis on a site’s content than on its organization, navigation, functionality, and visual design. Users want sites that have breadth and depth of content with minimal link redundancy. They commented that if a site has too many pages that are out of date, they stop going there. Participants had often identified sites rich in their subject and had these pages permanently bookmarked (e.g., Harvard’s catalog, a particular subject-based site at Stanford, subject-specific encyclopedias) bypassing the UC Berkeley Library’s web site altogether. Some of our subject specialty library pages were themselves identified as rich resources, and were used as the primary entry point to library resources in preference to the library’s home page.

Some specific content items that participants look for or would find useful on the library site: open hours for buildings and services; location of various libraries; abstracts; online tables of contents, indexes, prefaces, and other tools to help them determine remotely whether an item was actually relevant to their search; databases of journal articles; location of the nearest copy machine; staff directory information; easy access to library policies; easy access from the library’s site to the campus homepage (on the other hand, one user at least uses the search box on the campus web to connect to MELVYL); help, especially context-sensitive help; and tutorial information to guide the new user through the basics (e.g., finding a book).

Participants were very interested in a site that could provide them with integrated subject access to materials in their fields, including "key sources," survey papers, and specialized encyclopedias. Participants want access to applicable resources whether or not they are traditional library materials, e.g., wondering why the library site doesn’t connect to the "statistics data resources on campus?" One student expressed a desire for more electronic reserve materials, to "eliminate need to buy readers."

 

Features
(what can a user do within the site;
what tasks are technically supported)

Participants both described features that they found useful on existing web sites, and also brainstormed those features that would make the library’s site a really excellent tool. Some of these suggestions might be addressed with content, while some of them require underlying technology – hence the term used here, features.

Logon
Several participants wanted to be able to self-identify at sign-on, brainstorming a number of benefits:

Search
Participants want to be able to do quick searches as well as highly sophisticated searches (using syntax standards, boolean logic, etc.) There is a desire for having a search box fairly prominent on all screens, with some obvious explanation of what domains the search will address.

Search by Subject
As stated above, participants were very interested in a site that could provide them with subject access to materials. They also wanted value-added information to help segregate core resources from more specialized resources, and clues as to related resources/fields that might help them to enrich a search. Some wanted to be able to input their area of interest at logon, and have their next and subsequent options be based on this original subject-area preference.

"Others who searched…"
Related to the idea of "search by subject" was the desire for a feature akin to Amazon’s "others who bought this also bought…" A graduate student thought this might be very helpful if she knew it was a professor or other knowledgeable person who had been doing the searching. One participant described how the City of Singapore web site asks for every incoming user’s profession, e.g. "architect", after which "others can see how architects looked up information and what they searched." Participants were also intrigued with Amazon.com’s ability to answer questions such as "What books are popular at Cornell?"

Search by type
Several participants make considerable use of images, both as the subject of research and as a vehicle for instruction. They expressed a desire to be able to search for and sort images based on characteristics contained within the image.

Integrated search results
Participants would prefer to run one search and get results back from a variety of sources. The implication was that there are too many possibly relevant sources, and that the library could help considerably by providing an infrastructure that would search the most relevant sources for a given topic automatically. Participants were also interested in having responses grouped in useful ways; one recommended the Vivisimo search engine <http://vivisimo.com/> for its clustering feature. Some participants did not understand why a Google search results in different hits than does, for example, a library catalog search. Others questioned differences between Pathfinder and GLADIS search results. The more seasoned library users had fewer expectations for integrated search results, but no less desire for same.

Browse
Participants who like to browse the stacks would like to be able to do this, somehow, from home as well. They expressed an interest in having the web "mimic that serendipity" by having a "virtual browsing" or "relationship browsing" feature.

Help
Participants would like more help, both context-sensitive help (such as imbedded definition of unusual terms) and tutorial kinds of help (e.g., how to find a book). Generally users didn’t want to be sent to a large index of all help pages, but preferred having the help options either

 

Organization
(how are links grouped and labelled)

The general characteristics attributed to desirable sites included: well-organized; clear; limited set of options; not repetitive; organized as a user rather than a librarian would; same organizational principles consistent throughout the site.

Comments indicated that participants find the organization of the library’s home page as it now stands to be confusing. Participants asked about the grouping of links, suggesting that we consider a more logical arrangement, even alphabetical order. The apparent duplication between the two menus, "Libraries and Collections" and "Internet Resources by Academic Discipline" also drew criticism. Participants suggested reducing the number of links on the home page by grouping them behind labels that made sense to the user. Three suggestions were made for top-level organizational schemes:

Each focus group surfaced the idea of offering "views" that sifted and reduced all possible links into those links most relevant to an individual user. Some wanted several rather generic views (e.g., based on a user’s affiliation with the campus or subject area of interest). Some wanted a very specific view (e.g., based on a more complicated sign-on to identify the user exactly, perhaps remembering a profile of prior search strategies and found resources).

Participants commented that the site should be clearly organized and should "give progressively more detailed information as the user drills down."

Navigation
(how a user moves through the site,
and knows his/her current location within the site)

Users expressed the following opinions and preferences with regard to navigability:

Functionality
(how well does the system respond)

Participants were keen on two points regarding web system functionality: it has to be fast and work well for dial-up access, and it has to be free of ongoing, irritating glitches (e.g. fly-overs that stick; opening too many new windows that then need to be closed; linking to sites that disable the browser’s Back button). Participants expressed the need to print (pages from the web, citations from the catalogs, content from databases) and reported frustration in this regard. Other kinds of functional requirements are implied above, under Features, Organization, and Navigation.

Terminology
(how are resources labeled and described)

Participants agreed that terminology used should be as consistent as possible throughout the entire site, and stressed repeatedly that the site should use normal language rather than library in-speak. Terms mentioned as potentially confusing included CDL Directory, GLADIS, telnet, CD-ROMs, and Sunsite. Addressing Jill Garland who was attending as an observer, one faculty participant commented "You are new [to the library], but in even a few hours, you learn a lot of jargon -- but it's meaningless to me."

Visual Design
(how does the site look and feel)

Participants want a site that is uncluttered, attractive, and professional looking. Many were attracted by the simplicity of Google, even while admitting that the library’s site would need to be more complex. Participants commented that the current library home page is "way too busy", even "overwhelming." One professor reported, "I’ve never used the library site – took one look and said ‘no’."

Participants suggested that a better use of font, color, reducing the number of links, and not underlining links, might each contribute to a site that was easier to read (less cluttered) and easier to understand (information architecture made clear via use of visual cues and more informative buckets.) One suggested that we use graphics in an "intelligent and sparing" way (i.e., only if they carry either information or are themselves functioning icons.) Another underlined the importance of his being able to change the font size. Some participants find long pages that require scrolling to be troublesome.

Other concerns
(related to the library catalog and database systems)

As mentioned above, participants tended not to make distinctions between the library web site and the online systems accessible through it. For example, several expressed desires for features that we think of as related to the library catalog, such as better access to the tables of contents and indexes of books, and perhaps prefaces and introductions ("like Amazon," as one student put it). One student wanted the catalog to "just list the copies that are available to be checked out now," or simplify the results display with details given under each location for an item. Another student wanted to "check out books online, then go pick them up [at the circulation desk]."

Likewise, participants felt that a search that works in Google should produce similar, or at least some, results in the library catalog. One reported with some frustration that Google gave 47,000 hits on his search term, while Pathfinder gave zero. Some participants voiced concern about whether Pathfinder gives results consistent with, or as complete as, what one would get from GLADIS; others commented on confusing search choices and "back button" behavior in Pathfinder.

It was evident from these discussions that abnormalities and frustrations that users encounter with display, downloading, or printing of records in the catalog or full text items in article databases are closely associated with, if not actually attributed to the library web site. This underlines the importance of negotiating with vendors to provide services at a level of excellence that we ourselves would want to provide.

The web development process
Several suggestions were made about how we should proceed in developing the web site. One professor recommended that we tap into the talents of the many computer system experts on campus. Staff participants suggested that we hire (or find in-house) a good graphic designer, provide for orderly growth of the site by using templates and guidelines, and move to a rapid prototyping environment.

 

Next Steps for WAG

The focus groups offered a number of ideas that could be accomplished with existing resources as part of the planned redesign project. We recommend that WAG evaluate participants’ comments and suggestions carefully and supplement them with data to be gathered from user surveys, card sorting exercises, terminology tests, and usability tests.

In order to share this report with library staff and other libraries that may find it useful, we recommend that this document (without appendixes) be posted on the WAG web site and made known within the UC System, and that participant comments related to the library systems and services other than the web site be brought to the attention of staff in charge of those areas.

In the longer term, we also recommend that WAG address the question of how the library might deal with the expressed needs and preferences that focus on the catalog, require technology or resources not currently available, or otherwise fall outside this group’s current purview. Examples include participants’ desires for enriched catalog records, a radically improved search engine with the ability to integrate results from a variety of sources, and the ability to log onto the site once per session and see options and resources tailored to their individual profiles. This situation invites "out-of-the-box" thinking so that the next phase of development can move farther toward the web site that many users desire, and some already expect.

 

Submitted to WAG – May 30, 2003
Discussed and accepted by WAG – June 16, 2003


[ HELP/FAQ ] [ CATALOGS ] [ COMMENTS ] [ HOME ]
Copyright © 1996-2003 The Regents of the University of California.
All rights reserved. Last updated 6/30/03.
Contact