Notes

Slide Show

Outline

1	The Evolution of an Interface from the User Perspective: From End User Testing to a Usage Log Analysis Sarah Chandler
2	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
3	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- )
4	Catalysts for change Enhance with new functionality Migrate to new server Development partnership with Endeavor Release 2.0 of ENCompass
5	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
6	Impetus for Interface Customization Standard ENCompass interface did not meet our user needs Team members had XML/XLS expertise Collaborative relationship with Endeavor
7	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)
8	Pre-October prototype
9	October prototype: search/browse resources
10	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
11	Find Databases search/browse
12	Find Databases browse display
13	Find Databases search results screen
14	Find Articles main screen
15	Merged search results
16	Find Articles object record with OpenURL link
17	Find it at Cornell display
18	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
19	Overall use of system by Session ID
20	Find Articles search activity, including connection failures
21	Follow-up Analysis Used SPSS software Reran some of same analysis on newer data sets (Encompass and Apache) Explored documentation of analysis using SPSS
22	Overall use of system by Session ID
23	Weekly use by filename
24	Find Articles search activity
25	Databases Searched via Find Articles or Find Databases
26	Find it at Cornell usage
27	Lessons Learned from Log Analysis Data sources are complicated Extensive scripting and parsing are required Documentation of analysis is necessary for developing methodology
28	Outstanding Questions and Next Steps Zero hits issue Query string analysis Search errors Find it at Cornell – further research
29	Comments and Questions? Sarah Chandler sy82@cornell.edu