Discovery Interface Usability Testing
Discovery interface usability testing evaluates how well a library's discovery layer, the single search box that searches across catalog, articles, and databases, actually serves users, by watching representative people attempt realistic search tasks and measuring whether they succeed, how long they take, and where they stumble. Grounded in Jakob Nielsen's usability engineering, the method treats the interface as something to be tested empirically rather than judged by expert opinion alone. Fagan and colleagues' 2012 study of a discovery tool at an academic library exemplifies the approach: students performed authentic tasks while observers recorded success, errors, and think-aloud commentary, surfacing concrete problems with facets, result relevance, and terminology. The output is a prioritized list of usability problems and metrics that guide iterative redesign of the discovery experience.
Lees de volledige methode
Log in met een gratis account om dit onderdeel te lezen.
Methodenkaart
De omgeving van verwante methoden — selecteer een knooppunt om te verkennen.
Bronnen
- Fagan, J. C., Mandernach, M. A., Nelson, C. S., Paulo, J. R., & Saunders, G. (2012). Usability Test Results for a Discovery Tool in an Academic Library. Information Technology and Libraries, 31(1), 83-112. DOI: 10.6017/ital.v31i1.1855 ↗
- Nielsen, J. (1993). Usability Engineering. San Francisco: Morgan Kaufmann. ISBN: 9780125184069
Deze pagina citeren
ScholarGate. (2026, June 23). Discovery Interface Usability Testing (Task-Based Evaluation of Library Discovery Layers). ScholarGate. https://scholargate.app/nl/library-information-science/discovery-interface-usability-testing
Welke methode?
Plaats deze methode naast haar naaste verwanten en lees ze naast elkaar — de bibliotheek legt de boeken op tafel; de keuze is aan u.
- LibQUAL Service Quality AssessmentLibrary Information Science↔ vergelijken
- Reference Transaction AnalysisLibrary Information Science↔ vergelijken
Geciteerd door
Vergelijkbare methoden
Een fout op deze pagina gezien? Meld het of stel een correctie voor →