diff options
Diffstat (limited to 'issues')
| -rw-r--r-- | issues/improve-presentation-of-search-results.gmi | 15 | ||||
| -rw-r--r-- | issues/report-invalid-search-queries-over-api.gmi | 6 | ||||
| -rw-r--r-- | issues/search-results-presentation-designs.gmi | 26 |
3 files changed, 46 insertions, 1 deletions
diff --git a/issues/improve-presentation-of-search-results.gmi b/issues/improve-presentation-of-search-results.gmi index 36b7c85..982654d 100644 --- a/issues/improve-presentation-of-search-results.gmi +++ b/issues/improve-presentation-of-search-results.gmi @@ -1,9 +1,22 @@ # Improve presentation of search results -* assigned: arun, alex + +## Tags +* assigned: arun, alexm + +* status: stalled,closed + +* keywords: xapian,search,UI At the moment, we present search results in tabular form. See, for example, => https://cd.genenetwork.org/gsearch?type=gene&terms=cytochrome+NOT+P450 This is hardly the best way to present search results. Less important columns like species, group and tissue take up so much of the screen real estate. The user is not able to interact meaningfully with the search results. Sure, the user can sort the search results. But, the utility of sorting is questionable since the results are already sorted by search relevance. This is intentionally a very open ended and vaguely worded issue. I request Alex to experiment with different UX ideas, mockup those ideas, and seek feedback. + +## Notes 3/4/23 + +splitting this to multiple issues + +=> issues/search-results-presentation-designs.gmi + diff --git a/issues/report-invalid-search-queries-over-api.gmi b/issues/report-invalid-search-queries-over-api.gmi index f61fbfe..1efa0ab 100644 --- a/issues/report-invalid-search-queries-over-api.gmi +++ b/issues/report-invalid-search-queries-over-api.gmi @@ -1,8 +1,14 @@ + + # Report invalid search queries passed to the search API * assigned: alex, arun * tags: enhancement +* status: in progress + + + genenetwork2 offloads search to the genenetwork3 search API. When there is an error in the genenetwork3 API call, genenetwork2 has no idea what went wrong and cannot produce a good stacktrace. The genenetwork3 API should do a better job of communicating errors. In particular, for the search API, we should start with correctly reporting invalid search queries so that genenetwork2 can present it appropriately in its web UI. diff --git a/issues/search-results-presentation-designs.gmi b/issues/search-results-presentation-designs.gmi new file mode 100644 index 0000000..2bbf0f2 --- /dev/null +++ b/issues/search-results-presentation-designs.gmi @@ -0,0 +1,26 @@ +# Search results presentation + +## Tags + +* assigned: alex + +* status:in progress + +* keywords: UI,search + + + +## Notes + + +The idea is to research and find good design for search results in global search +Currently the results are displayed in tabular form and too many columns are presented to user overlapping the page + +Design should be simple and eye catching to user +links to suggesetd designs: + +=> https://www.ncbi.nlm.nih.gov/genome/?term=gene + + + + |