You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use the mygene.info api to find human orthologs for a set of entrez gene IDs. However, I noticed that some genes which have ortholog mappings on pantherdb do not show crossreferences through the mygene.info api.
Here's a case study;
The mygene.info record for the mouse gene "Neurexin 3" does not show a human ortholog, but pantherdb.org does have this data (links shown below). In reverse, the mygene.info record for the human gene "Neurexin 3" does show a mouse ortholog.
why are known pantherdb LDO orthologs missing from the mygene.info record ?
can we use the mygene.info api to filter for the target species of interest in ortholog records (would be much more efficient for most use-cases) ? For instance, return only pantherdb and homologene mappings to taxid=9606
could the mygene.info _id be included with each pantherdb ortholog (so we don't have to fire a follow-up query to find the actual gene ID for each ortholog) ?
I would like to use the mygene.info api to find human orthologs for a set of entrez gene IDs. However, I noticed that some genes which have ortholog mappings on pantherdb do not show crossreferences through the mygene.info api.
Here's a case study;
The mygene.info record for the mouse gene "Neurexin 3" does not show a human ortholog, but pantherdb.org does have this data (links shown below). In reverse, the mygene.info record for the human gene "Neurexin 3" does show a mouse ortholog.
mygene.info data for gene; Nrxn3
Mouse: https://mygene.info/v3/gene/18191?fields=taxid,name,symbol,pantherdb,homologene
Human: https://mygene.info/v3/gene/9369?fields=taxid,name,symbol,pantherdb,homologene
pantherdb data for gene; Nrxn3
Mouse: http://pantherdb.org/genes/gene.do?acc=MOUSE%7CMGI%3DMGI%3D1096389%7CUniProtKB%3DQ6P9K9
Human: http://pantherdb.org/genes/gene.do?acc=HUMAN%7CHGNC%3D8010%7CUniProtKB%3DQ9Y4C0
The text was updated successfully, but these errors were encountered: