Closed danich1 closed 2 years ago
I've thought about it, too. I was thinking that we'd change the autocomplete endpoint to also return an ID when a user enters a substring of the human-readable text associated with the ID. I think I have everything I need in the concept map file to do that, so if the above sounds good I can start on a first draft of the feature.
Yeah sounds good. Feel free to take a stab at the first draft!
Currently, our token searcher has users put in IDs for concepts rather than the literal concept itself. E.g. gene8128 -> ST8SIA2 Normally, I'm fine with this medium of searching; however, I received feedback that we should have it as the other way around. E.g., ST8SIA2(tagged) -> backend see this as gene_8128 and proceeds normally for searching.
Would like to hear your thoughts on this feature.