The Evolution of an
Interface from the User Perspective:
From End User Testing to a Usage Log Analysis
Presentation outline
|
|
|
Background of new and old systems: from
e-Reference Collection to Find Articles/Find Databases/Find e-Journals |
|
Usability testing |
|
Development responses |
|
Transaction log studies – summer, fall |
|
Next steps |
Networked Resources
Portal: History
|
|
|
Mann Library Gateway (1991) |
|
Cornell University Library Gateway
(1998) |
|
E-Reference Collection (2001) |
|
Find Articles/Find Databases/Find
e-Journals (2003- ) |
Catalysts for change
|
|
|
Enhance with new functionality |
|
Migrate to new server |
|
Development partnership with Endeavor |
|
Release 2.0 of ENCompass |
Functionality: old and
new
|
|
|
Existing Features |
|
Search gateway metadata |
|
Go to database “native interface” from
search results |
|
Browse by subject |
|
Navigate to other CUL resources |
|
Authenticate users for restricted
resources |
|
Plus |
|
Search at article level |
|
Simultaneous search across multiple
databases |
|
Reference linking |
|
Search for all e-journal titles |
Impetus for Interface
Customization
|
|
|
Standard ENCompass interface did not
meet our user needs |
|
Team members had XML/XLS expertise |
|
Collaborative relationship with
Endeavor |
Usability testing
|
|
|
Summer-Fall 2002: development team
sensed usability problems with the “out-of-the-box” ENCompass interface |
|
October 2002: “paper prototyping” with
students and faculty |
|
November 2002: computer workstation
focus groups (with students and faculty) |
Pre-October prototype
October prototype:
search/browse resources
Round 1 Recommendations
|
|
|
Simplify cluttered screen design |
|
Resolve confusing search/browse issue |
|
Rethink “e-Reference collection” name |
|
Address the “granularity issue” by
presenting article level searching separately |
|
|
|
|
Find Databases
search/browse
Find Databases browse
display
Find Databases search
results screen
Find Articles main screen
Merged search results
Find Articles object
record with OpenURL link
Find it at Cornell
display
Transaction Log Analysis
|
|
|
Initial transaction log studies were
conducted during summer prior to full-scale launch |
|
Studies revealed activity at the
database level |
|
Studies identified databases with
connection problems |
|
Ongoing studies are needed to influence
service design modifications |
Overall use of system by
Session ID
Find Articles search
activity, including connection failures
Follow-up Analysis
|
|
|
Used SPSS software |
|
Reran some of same analysis on newer
data sets (Encompass and Apache) |
|
Explored documentation of analysis
using SPSS |
Overall use of system by
Session ID
Weekly use by filename
Find Articles search
activity
Databases Searched via
Find Articles or Find Databases
Find it at Cornell usage
Lessons Learned from Log
Analysis
|
|
|
Data sources are complicated |
|
Extensive scripting and parsing are
required |
|
Documentation of analysis is necessary
for developing methodology |
|
|
Outstanding Questions and
Next Steps
|
|
|
Zero hits issue |
|
Query string analysis |
|
Search errors |
|
Find it at Cornell – further research |
|
|
|
|
Comments and Questions?
|
|
|
|
|
|
|
Sarah Chandler |
|
sy82@cornell.edu |