Open gaurav opened 1 year ago
Now that we have a more flexible document structure, would we like to include properties fields?
We now include taxon information for all NCBIGene identifiers. I've just started work on a PR (https://github.com/TranslatorSRI/Babel/pull/349) that should include taxon information for all UniProtKB identifiers as well. NameRes now supports filtering by taxa (using NCBITaxon identifiers).
So I think the remaining tasks on this ticket are:
e.g. if you search NameRes for "fgf8", we get back several different UniProt IDs for human, zebrafish, etc. UI wants to make sure that users can clearly differentiate between the identifiers by means of the label (note that they use the canonical label from NodeNorm, NOT the label(s) from NameRes).
The ultimate fix for this is going to be the metadata service that will eventually fit into NodeNorm, but it would be good to have a short-term fix. This could be entirely on the UI's end (e.g. calling mygene.info for each UniProtKB identifier), but eventually the Node Metadata Service is the solution here.
Alternative: prioritize names with brackets to the canonical name in NodeNorm.