Acknowledgements
• Lots of others• Who have tested results• Provided feedback on indexing• Ideas about results formatting• As Sounding boards• Etc.
Discovery TestBed
• URL: http://library.osu.edu/discover
• TestBed• Provides a method to test results when
passing queries• Demonstrates potential results
behavior• Is not the interface the user will be
presented with• These pages will be integrated into
the web site design• Users will be starting from a search
box somewhere (like the homepage)
What’s completed today
Subject Guides Libguides are made available via the Springshare API
Digital Collections Currently indexing all public items from the Libraries Digital Collections System
Library CatalogAll Bibliographic data has been indexedReal-time holdings data is being extracted on viewWe’ve created an initial search profile and weighting profile (though this will change soon, as we will be implementing proximity logic to improve relevancy of phrases)
EBSCO integration is completeSearch scope is likely too broad [in my opinion], this is specifically a discussion for testingIntegration with Proxy and Find It has been completedInitial knowledge-base work has been completed.
Production StackURL: http://library.osu.edu/discoverSeparate Indexes (so work on staging will not impact testing)
What’s completed today
• Integration of with the new finding aid/collections resources
Special Collections
Web site/Blogs
• Creation of two “views”, a focused view and bento view
• A library lexicon (API) which can (and will) be shared with campus to enable novel integration efforts
Additionally
In process work
Fleshing out the focused view to enable facets, greater user control over result sets.
Continuing to look at what data we extract for indexing purposes from the catalog
Adding Journal/Database Suggestions
Adding direct links to articles from the bento/focused view for articles
Indexing the Knowledge Bank
Development of “Escape Hatches” [ways to get to source content when discovery isn’t refined enough
Scoping content searched via Ebsco
Documentation
General UI Work
*Discovery Timelines
Dec. 4, 2017 – All Library meeting introducing the
discovery project
Will do this at Thompson and the Tech Center (and, with luck, maybe will be
able to record or make the Thompson meeting
available online)
Dec. 4 – Jan. 2018
Michelle, Russell, and I will be meeting with Units to
get their feedback
Spring 2018
Public Beta (on the website)
Discovery Timelines
Summer 2018
Replaces WorldCat Local, WorldCat Local still available via the Home page as a legacy tool
Fall 2018
Work with faculty to ensure that they transition learning objects away from legacy discovery to
new tool
Jan. 2019
WorldCat Local Removed (and no longer available)
Discovery Timelines
Throughout this period, we will be taking feedback and
iterating the service
Will be highlighting changes to the service as we move
forward, and providing updates as we add
features/content and update relevancy
Developing documentation to provide targeted
feedback regarding content that can be searched versus
not searched
Testing/Feedback
• Areas of feedback:• Results – are they relevant?• Scoping EDS content stream?• Is this intuitive?• Is this meeting your expectations?• How can we be better?• UX Cohort will begin testing• Outside faculty (DELIT, etc.)
User Experience: So far
Working Principles for Discovery
Proposal with Mockups
Interaction Design
UX Cohort
Alpha Testers
Working Principles for Discovery
Working Principles for Discovery
Discovery shouldn’t be about what is found, but what is learned
…should lead to access, not dead ends
…is about creating bridges and preserving the context of the information
…must be accessible: fewer initial decisions
…is not neutral: must be aware of the audience
…promotes library resources through many channels
Proposal Resources
Research of other discovery platform options
2015 LibQUAL survey
Analysis of OSUL tools used, types of search, etc.
Faculty survey
Proposal Outcomes
Proposed alternative to current OSUL discovery model
Illustrated mockups
Timeline for usability testing
Ongoing care & maintenance
Alpha Testers
Minimum viable product Logically group
results
Explain how results are found
Eliminate dead ends