You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current table format for search results breaks with prevailing industry standards and it shows. It also has a number of disadvantages including:
misleading to users (conflation of results and association data)
lack of mobile responsiveness (multiple columns don't fit)
inability to alter displayed fields based on the kind of result (eg. taxon not really relevant for a chemical or publication)
If we move to more of a card / slug based format for results, it would be preferable. The matching string would be bold instead of a separate field. Note that for this to happen, a different font with an actual bold option would be necessary. I recommend Roboto. I prefer oswald font for curies.
The text was updated successfully, but these errors were encountered:
@jmcmurry curious what you mean by "conflation of results and association data", there shouldn't be any association data in our search/autocomplete index so it would be good to track down where this coming from.
We are not conflating computationally; however the table format for results makes it look more like association tables. Just trying to make them look more like search results
Sent from my iPhone
The current table format for search results breaks with prevailing industry standards and it shows. It also has a number of disadvantages including:
If we move to more of a card / slug based format for results, it would be preferable. The matching string would be bold instead of a separate field. Note that for this to happen, a different font with an actual bold option would be necessary. I recommend Roboto. I prefer oswald font for curies.
The text was updated successfully, but these errors were encountered: