UCSF Cores Search 2.0: Design Strategy Overview
-
Upload
ctsi-at-ucsf -
Category
Education
-
view
615 -
download
1
description
Transcript of UCSF Cores Search 2.0: Design Strategy Overview
![Page 1: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/1.jpg)
Clinical and TranslationalScience Institute / CTSIat the University of California, San Francisco
UCSF Cores Search 2.0Design Strategy Overview
Anirvan Chatterjee, Brian Turner
![Page 2: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/2.jpg)
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.
![Page 3: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/3.jpg)
![Page 4: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/4.jpg)
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.
![Page 5: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/5.jpg)
Core directors say:
“QPCR”
We let users search under:
“QPCR”
“RT-PCR”
“Real-time PCR”
“Quantitative PCR”
“Quantitative real time RT-PCR”
![Page 6: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/6.jpg)
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
![Page 7: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/7.jpg)
![Page 8: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/8.jpg)
![Page 9: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/9.jpg)
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
![Page 10: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/10.jpg)
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)
![Page 11: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/11.jpg)
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
![Page 12: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/12.jpg)
Example: Google search results block
![Page 13: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/13.jpg)
Example: Google search results block
Page name/link
(bold, emphasized)Page URL
Search result description/snippet
(relevant text bolded)
![Page 14: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/14.jpg)
Repeated Google search results:visual rhythm aids scannability
![Page 15: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/15.jpg)
Cores Search search results block
![Page 16: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/16.jpg)
Core name/link
(bold, emphasized)
Relevant resources
Location
(easy to scan)
Core details
(deemphasized)
Cores Search search results block
![Page 17: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/17.jpg)
Repeated Cores Search search results:visual rhythm aids scannability
![Page 18: UCSF Cores Search 2.0: Design Strategy Overview](https://reader033.fdocuments.us/reader033/viewer/2022060201/559b22681a28abbc738b47f1/html5/thumbnails/18.jpg)
Cores Search 2.0
http://cores.ucsf.edu/
A collaborative effort of UCSF’sResearch Resource Program and the
Clinical and Translational Science Institute