ucsf cores search 2.0: design strategy overview
DESCRIPTION
Learn more about Anirvan Chatterjee's work: http://profiles.ucsf.edu/ProfileDetails.aspx?From=SE&Person=5396511 Learn more about Brian Turner's work: http://profiles.ucsf.edu/ProfileDetails.aspx?From=SE&Person=5333232TRANSCRIPT
Clinical and TranslationalScience Institute / CTSIat the University of California, San Francisco
UCSF Cores Search 2.0Design Strategy Overview
Anirvan Chatterjee, Brian Turner
1. Search engines
Problem:
– The UCSF users most in need of the system are the least likely to know that it exists.
Solution:
– We've designed the site to rank high when users search for UCSF resources.
2. Use users’ own language
Problem:
– UCSF researchers and core directors don’t always use the same words when referring to resources.
Solution:
– We make resources available under a wide variety of synonyms, so users can always find what they want.
Core directors say:
“QPCR”
We let users search under:
“QPCR”
“RT-PCR”
“Real-time PCR”
“Quantitative PCR”
“Quantitative real time RT-PCR”
3. Multiple paths to find your resource
Problem:
– There are 200+ types of resources, so it can be hard for users to find the type they need.
Solution:
– Offer two easy ways to get to the right resource:
– Google-style typeahead search
– Alphabetized list, designed for scannability
4. Simplify site to remove roadblocks
Problem:
– Busy pages can confuse new users, hampering or preventing them from completing their task
Solution:
– Once users find the resource they want, they’re immediately directed to the core website/contact
– Every irrelevant detail and roadblock removed
Search for “cell isolation”
Cores Search 1.0
• Users had to wade through 4,191 words in search result
Cores Search 2.0
• Word count cut down to 177 words (a 96% reduction)
5. Make it easy to compare options
Problem:
– There can be many cores offering a specific type of resource
Solution:
– Design a clear search results block
– Use visual rhythm to support scannability
Example: Google search results block
Example: Google search results block
Page name/link
(bold, emphasized)Page URL
Search result description/snippet
(relevant text bolded)
Repeated Google search results:visual rhythm aids scannability
Cores Search search results block
Core name/link
(bold, emphasized)
Relevant resources
Location
(easy to scan)
Core details
(deemphasized)
Cores Search search results block
Repeated Cores Search search results:visual rhythm aids scannability
Cores Search 2.0
http://cores.ucsf.edu/
A collaborative effort of UCSF’sResearch Resource Program and the
Clinical and Translational Science Institute