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=5333232

1. Clinical and Translational
Science Institute / CTSI
at the University of California, San Francisco
UCSF Cores Search 2.0
Design Strategy Overview
Anirvan Chatterjee, Brian Turner

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

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

5. Core directors say:
“QPCR”
We let users search under:
“QPCR”
“RT-PCR”
“Real-time PCR”
“Quantitative PCR”
“Quantitative real time RT-PCR”

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

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

10. Search for “cell isolation”
Cores Search 1.0 Cores Search 2.0
• Users had to wade through • Word count cut down to
4,191 words in search result 177 words (a 96%
reduction)

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

12. Example: Google search results block

13. Example: Google search results block
Page name/link
(bold, emphasized)
Page URL
Search result description/snippet
(relevant text bolded)

14. Repeated Google search results:
visual rhythm aids scannability

15. Cores Search search results block

16. Cores Search search results block
Location Core name/link
(easy to scan) (bold, emphasized)
Core details
Relevant resources (deemphasized)

17. Repeated Cores Search search results:
visual rhythm aids scannability

18. Cores Search 2.0
http://cores.ucsf.edu/
A collaborative effort of UCSF’s
Research Resource Program and the
Clinical and Translational Science Institute