@kevinschaper from the Monarch Initiative told me that he was extracting MESH-to-CHEBI mappings in SSSOM format, and wondered if Babel or NodeNorm could help with that. I think the easiest way would be to add two new endpoints in NodeNorm:
The first would allow someone to request all the identifiers that have a particular prefix, e.g. CHEBI: or PANTHER.FAMILY:PTHR12824:. Among other things, this would allow someone to check how many mappings we have -- they could then compare this to UMLS or MeSH. Once they have that list, they could use the standard NodeNorm lookup endpoints to translate those identifiers, or:
We could add a simple mappings interface that only displays the mappings from one identifier to others. This endpoint could be called by sending it a list of identifiers to retrieve mappings, or possibly we could support source and destination prefixes directly.
I don't think we have a real use-case for this in Translator, so I'm just writing this down as an idea to consider in the future if it becomes relevant.
@kevinschaper from the Monarch Initiative told me that he was extracting MESH-to-CHEBI mappings in SSSOM format, and wondered if Babel or NodeNorm could help with that. I think the easiest way would be to add two new endpoints in NodeNorm:
CHEBI:orPANTHER.FAMILY:PTHR12824:. Among other things, this would allow someone to check how many mappings we have -- they could then compare this to UMLS or MeSH. Once they have that list, they could use the standard NodeNorm lookup endpoints to translate those identifiers, or:I don't think we have a real use-case for this in Translator, so I'm just writing this down as an idea to consider in the future if it becomes relevant.