NCATSTranslator / Feedback

A repo for tracking gaps in Translator data and finding ways to fill them.
7 stars 0 forks source link

Make the ordering rank number explicit on result #403

Open TranslatorIssueCreator opened 1 year ago

TranslatorIssueCreator commented 1 year ago

Type: Bug Report

URL: https://ui.test.transltr.io/results?l=Hereditary%20Sensory%20And%20Autonomic%20Neuropathy%20Type%204&t=0&q=4cde39ed-7a43-4a3d-aa8e-96dff108edd1

ARS PK: 4cde39ed-7a43-4a3d-aa8e-96dff108edd1

Steps to reproduce:

on test UI MVP1 on Hereditary sensory and autonomic neuropathy type 4 submitted by @sandrine-m

Screenshots:

sandrine-m commented 1 year ago

This is not the first time I had that need, but here is an example: I learnt that NTRK1 is associated to Hereditary sensory and autonomic neuropathy type 4 (rare disease) (source: rarediseases.org) To assess answer quality, I am filtering for NTRK1 node and get this:

image

The score make sense only from the overall distribution of scores for the query. I would like to know until which rank value I should inspect carefully the results to "be surprised". Doing this from the score is not ideal mainly when ties are present.

sandrine-m commented 1 year ago

This issue is reproducible on CI

sstemann commented 1 year ago

is the request that the score is recalculated based on your filter?

sandrine-muller-research commented 1 year ago

The request is simply to add a rank number to the result so that

gprice1129 commented 1 year ago

We think this is better implemented as being able to share a view of a result or workspace item.

sandrine-muller-research commented 11 months ago

Reopening this issue as I found one other use-case: when I get a list of results and I am filtering by one of the available filter, I loose after how far each (now filtered) result is. Having the numbers will help me know that. Or perhaps showing the place within the whole distribution would be even better (for me at least):

image
sierra-moxon commented 4 months ago

@gprice1129 - does this have a chance of getting implemented or should we close as "won't do" ? :)

gprice1129 commented 4 months ago

@sierra-moxon we are currently discussing this issue. Will update soon.