1 / 57

Find Articles

Find Articles. Fourth Generation Design For Federated Searching at the University of Rochester Brenda Reeb, Usability David Lindahl, Digital Initiatives. Agenda. Serial Failure Metasearch User Centered Design Process Culture and Politics Generations of Design Technology. Serial Failure.

sun
Download Presentation

Find Articles

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Find Articles Fourth Generation Design For Federated Searching at the University of Rochester Brenda Reeb, Usability David Lindahl, Digital Initiatives

  2. Agenda • Serial Failure • Metasearch • 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. Serial Failure • Students cannot find articles • Students overwhelmed with database names, contents, and search protocols • Students insist on search simplicity • Eliminate the complexity of information retrieval • Technologies exist to make it simpler • Politics exist to make it complex

  5. Design responses • Don’t make undergraduates choose anything before searching • Don’t expect users to read anything before searching • Forgiving search box tolerates single words, multiple words, Boolean, “ “ phrases. • Assume relevance ranking

  6. “Serial Failure” The Charleston ADVISOR, Vol. 5., no. 3, 2004. Jennifer Bowen, Judi Briden, Vicki Burns, David Lindahl, Brenda Reeb, Melinda Stowe, Stanley Wilder.

  7. Metasearch • This is a title slide to be deleted (dave) • What is metasearch – one slide Dave – we use “metasearch” in Serial Failure, not federated search. Br

  8. Metasearch What is metasearch? • Federated Search • Single user interface to multiple databases • Simultaneous searching across resources • Merged results Metasearch technology: • Metasearch product with UI • Connectors • OpenURL Linking

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

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

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

  12. Artifacts of design process • “Issue response” document • Usability results • Key task list • Regular meetings (design = usability) • Project specific meetings (usability=content and content=design)

  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 • Began 2001 • 7 staff trained as usability testers • Over 20 projects, large and small • Testers volunteer for projects • Reading, conferences, practice • Vendor co-development

  15. Usability teams do this: • Define key tasks • Design and conduct tests • Report results • Maintain a “lab” • Maintain results for the public

  16. What is a key task? Key tasks are defined as frequently asked items, frequent actions or navigation to parent/child pages. Find a known article. Find a known journal. Find an article on a specific topic. Find articles on a multidisciplinary topic. Find a specific journal collection.

  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. Content Group • This is a title slide to be deleted(brenda) • Pivital to key task development • Select appropriate content • Apply experience and education to the iterative design process

  19. Content groups • 2 to 10 in number for a project • Reference staff, circulation staff, or ILL staff • Created and disbanded as needed • Observe some tests

  20. Content groups do this: • Define key tasks • Select appropriate content • Apply experience and education to the iterative design process • Observe some tests • Interpret usability results • Raise issues, not design solutions

  21. 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)

  22. 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

  23. “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 http://www.section508.gov/ http://webstyleguide.com/ http://usability.gov/guidelines/ http://www.library.rochester.edu/index.cfm?PAGE=623 Style Guidelines • Universal Design • Section 508 • Web Style Guide • Research-Based Web Design & Usability Guidelines • Page Editors’ Checklist

  24. Models For Finding: Google • Enter keywords • Browse results by title and snippet • View full text

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

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

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

  28. 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)

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

  30. User Pathways Find Databases By Name

  31. User Pathways Change color to green Find Databases By Subject

  32. User Pathways Change color to blue Find Articles

  33. Staff Culture versusStudent Expectations • This is a title slide to be deleted(dave)

  34. Students say: “I need an article!” Librarians say: “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.” Staff Culture versusStudent Expectations

  35. Staff Culture versusStudent Expectations • Balance user needs with librarian needs? • The user is always right! • Focus on user expectations • Focus on finding • Web pages that support “doing” not “telling” • Support beginners and experienced users

  36. Staff Culture versusStudent Expectations • Connect at courses, not at academic disciplines • 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. • Sustainability • Distributed workload (all bibliographers participate) • Dynamic, database-driven pages

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

  38. Expect these accusations! • Simple designs dumb down the site • Testing 3 users is not enough • Students are lazy • No one told me about this • Where is your report? • This is so subjective!

  39. Try these responses • 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

  40. Articles Committee • This is a title slide to be deleted

  41. Generations of Design • This is a title slide to be deleted

  42. Pre ERA design Circa 2002

  43. Pre ERA design Circa 2002

  44. Encompass UI • Enter keywords and select databases • Select databases or “SHOW ALL” • Select a result • View metadata • Select a full text source • View full text online

  45. Encompass UI • Enter keywords and select databases • Select databases or “SHOW ALL” • Select a result • View metadata • Select a full text source • View full text online

  46. Find Articles UI • Enter keywords • Select a result • View full text online

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

  48. 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

  49. 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

More Related