MetaCell / MetaCell/interlex

Search bar inconsistencies are confusing

Open
#175 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
3
Forks
4
PR merge metrics
No merged PRs in 30d

Description

when searching for a term, i was confused as to why i had to select results from the dropdown preview of the search bar.
it wasn't until today when Tom told me about "browse all" being a button, and that clicking that is how i get the full list returned for review. this seems inconsistent though. here's my steps:

  1. type "nerve" in search bar
  2. hit enter
  3. 0 results returned for nerve
  4. return to search bar.
  5. click in search bar, see there's lot of options for nerve. (see screenshot)
  6. how do i get those options?
  7. use right arrow to remove highlighting from "nerve". click enter
  8. get first(?) search result for "nerve"
  9. return to search bar, click in to see the helper window. click "browse all"
  10. still get 0 results.
Image

Desired Action:

  1. want to be able to see a list of terms that fit my search criteria with as few clicks as possible. I cannot use the "helper dropdown" reliably, because many terms names are similar - you need to be able to see the definition at a minimum (& then, i usually look to see if it is present in uberon) in order to evaluate which one is appropriate.
  2. I want to be able to get the preview results to populate the search result page reliably.
  3. browse all doesn't look like a button, or that it should have a function. All other items that have actions have highlighting on hover.
  4. I don't understand the "browse all" function, and what the usecase is to not use it?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the numbered steps in the search bar, including the preview options and the “browse all” action. Trace how preview selections and Browse all populate the search results page; done means matching terms, definitions, and relevant Uberon information can be reviewed reliably with clear interaction feedback.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.