1. River Campus Libraries Find Articles Fourth Generation Design For Federated Searching Brenda Reeb, Usability David Lindahl, Digital Initiatives

2. Agenda  Serial Failure  Federated Search  User Centered Design Process  Culture and Politics  Generations of Design  Technology

3. Serial Failure  This is a title slide to be deleted (brenda)  Cite our article in this section

4. Find Articles: Usability Issues  Choosing a database  Using a database  Expectations  OPAC versus database  Terminology

5. Focus on results - highlights  Don’t make undergraduates choose anything before searching  Don’t expect users to read anything before searching  No consistency to how a search is typed – single words, multiple words, Boolean, “ “ phrases.  Relevance sort is assumed, so non- relevant hits at top of results list is a problem.

6. Federated Search  This is a title slide to be deleted (dave)  What is metasearch – one slide

7. Find Articles: Meta-search What is meta-search?  Federated Search  Single user interface to multiple databases  Simultaneous searching across resources  Merged results

8. What the Libraries Did  Invested in meta-search technology  Selected SFX (Linking)  Selected Encompass (XML UI, Catalog integration)  Vendor partnership  Training  User interface development  Technology integration (CF, XML, SFX, SQL)

9. User Centered Design Process  This is a title slide to be deleted (brenda)

10. Usability group Content group Design group Key tasks Test results Prototypes Issue responses Design iterations Test results User Centered Design Process

11. Artifacts of design process  Issue response document  Usability results  Key task list  Regular meetings (design = usability)  Project specific meetings. (usability=content and content=design)

12. User focus Usability group Design group Content group Highest. No other goal than to represent the user. Medium. Competes with standards, technology, time and money Medium. Competes with exhaustive content, complex tasks

13. Usability Program  This is a title slide to be deleted(Brenda)  What is a key task  Key tasks for finding articles  Key task questions

14. Usability Program @ UR  Brief history since 2001  Staffing  How we learn  How we assign projects – Project Chart  Vendor codevelopment

15. Slide of project chart goes here

16. River Campus Libraries What is a good key task and what do I do with it? Key tasks are defined as frequently asked items, frequent actions or navigation to parent/child pages. Key tasks become test questions, scenario questions, basic anchors to your design.

17. Characteristics of a task (long version) from Carolyn Snyder, Paper Prototyping Is based on a goal that matters to the user Covers questions important to the success of your product and business Has appropriate scope – not too broad, not too specific Has a finite and predictable set of possible solutions Has a clear end point that the user can recognize Elicits action, not just opinion Avoid red herrings – tasks with no solution.

18. Sample key task chart. Page 4 of handout packet.

19. Sample final key tasks. Page 5 of handout.

20. Brenda Reeb; EndUser 2004; Sample Intranet page

21. Brenda Reeb; EndUser 2004; Sample Key Task list

22. Brenda Reeb; EndUser 2004; Sample test questions

23. Test results example A/J/N testing, University of Rochester. EndUser 2004.

24. Back Up! Here comes ERA! Handout, p. 9

25. Design Group  This is a title slide to be deleted(dave)  Style guidelines  Models for finding  Design of pathways  Group that knows the technology (what’s possible)

26. Web Design Process Overall Design  “Hide the technology”  Consistency with library website  Task oriented pathways  Usability testing program Page Design  Essential components  Prioritize  Simplify  Style guidelines

27.  Universal Design  Section 508  Web Style Guide  Research-Based Web Design & Usability Guidelines  Page Editors’ Checklist “Universal design is the design of products and environments to be usable by all people, to the greatest extent possible, without the need for adaptation or specialized design.” Ron Mace Style Guidelines http://www.section508.gov/ http://webstyleguide.com/ http://usability.gov/guidelines/ http://www.library.rochester.edu/index.cfm?PAGE=623

28. Models For Finding: Google 1.Enter keywords 2.Browse results by title and snippet 3.View full text

29. Models For Finding: FRBR FRBR User Tasks  Find  Identify  Select  Acquire FRBR = Functional Requirements for Bibliographic Records More information: http://www.ifla.org

30. Web Design Process: Find Articles “Find Articles” project  Ongoing project to address usability issues  Our implementation of meta-search with Encompass

31. Knowledge Partial knowledge No knowledge Subject clusters Mapping your search to a subject Takes you away from your natural path User Databases by Subject Find Articles Clusters (courses) Google Databases A-Z User Pathways

32. User Pathways To Finding Articles  Knowledge of specific databases and how to use them (Databases A-Z)  Partial knowledge (Databases by Subject)  No knowledge (Find Articles, Google)

33. User Pathways To Finding Articles Scholarly and comprehensive results (more) (less) Knowledge and Training

34. Insert Database A-Z graphic

35. Databases A-Z Change color to green Insert Databases by subject graphic

36. Databases A-Z Change color to blue Insert Find Articles

37. Content Group  This is a title slide to be deleted(brenda)  Help develop key tasks  Select appropriate content  Apply experience and education to the iterative design process

38. Staff Culture versus Student Expectations  This is a title slide to be deleted(dave)

39. Do, not tell I need an article!  Select a database  This database has 435 journals in it.  These journals are peer reviewed.  Choose basic or advanced.  These journals predate the Civil War. We say this:

40. Balance user needs with librarian needs The user is always right.

41. Staff culture  focus on Finding  Web pages should “do” not “tell”  Willing to try new skills without being experts.  Administrative support  Small success = TA DA SUCCESS  Leadership 101

42. Meet them where they are. Students attend POL250 – “Conflict in Democracies” They do not relate to Political Science. They do not envision themselves as political scientists. Courses, not academic discipline.

43. How to sustain “Meet them where they are”  Distributed workload (all skill level bibliographers participate)  Automated system; automated work space  Database driven

44. Politics of doing User Centered Design  This is a title slide to be deleted(brenda)  You will encounter x, y, and z in your organization

45. Politics  Inform  Page design process document  Don’t leave home without the toolkit  Neilson’s Alert Boxes  Pages from Don’t Make Me Think  Engage  Observe tests  Publish results

46. Articles Committee  This is a title slide to be deleted

47. Generations of Design  This is a title slide to be deleted

48. Pre ERA design Circa 2002

49. Pre ERA design Circa 2002

50. Encompass UI 1.Enter keywords and select databases 2.Select databases or “SHOW ALL” 3.Select a result 4.View metadata 5.Select a full text source 6.View full text online

51. Encompass UI 1.Enter keywords and select databases 2.Select databases or “SHOW ALL” 3.Select a result 4.View metadata 5.Select a full text source 6.View full text online

52. Find Articles UI 1.Enter keywords 2.Select a result 3.View full text online

53. Mapping the Find Articles UI to FRBR Search Select Article Full Text (Gather) FRBR Tasks: Find Identify Select Acquire

54. Find Articles: Subject Clusters  Subject Clusters  Pre-selected databases  Search boxes anywhere  Course Pages  Connects undergrads to library resources  Top-5 resource  Usability success  Add Subject Clusters to Course Pages

55. Find Articles: What’s Next  Subject clusters  Testing across range of users  Direct to full text  Abstracts on selection screen  Results navigator  Shared knowledge base  Integration with catalog

56. Technology  This is a title slide to be deleted (dave)

57. Find Articles: How It Works Search Select Article Full Text (Gather) Library Web Server ERA Server Subscription Database XSLT User Page with Full Text XSLT XML HTML

58. Meta-search Issues  Speed and Reliability  Connectors  Index vs. Meta-search  Ease of use  Database selection  Abstracts on selection screen  Full text availability  One click to full text  Quality of results  How search terms are applied  Database selection  Relevance sorted results and de-duping

59. Meta-search Standards  Z39.50  SRW/SRU and CQL  OpenURL  NISO MetaSearch Initiative  OAI

60. Linking To Full Text  Use RE to test input variables  Determine full-text available  Based on item type and database  Create canned URL  Double dip  Requires published or discovered syntax

61. Standards Matter  Z39.50  SRW/SRU and CQL  OpenURL  NISO MetaSearch Initiative  OAI

62. OpenURL Fields  GENRE  ISSN or ISBN  ATITLE (journal-article title)  TITLE (book title)  JTITLE (journal title)  AUFIRST (author first name)  AULAST  VOLUME  ISSUE  DATE  SPAGE (start page)