-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add MeSH to disease file #15
Comments
…ing or by DO xrefs. Issue #15 todo - compare against tudors list
@tudorgroza not sure I understand these files why is this one in 1-n?
Mappings highlighted:
I guess this is just because mesh has dodgy synonyms? btw, not all DOIDs are zero-padded, annoyingly |
These are the meshes in the list that I didn't find DO mappings for Should see if @tudorgroza maps some I don't Then pass to DO folks for addition? |
Should all MeSH diseases (or at least the union of those from CTD file and common disease work) have an xref in DO? do we need this so as to not use MeSH directly? what if a MeSH term maps to a DC term but not a DO term? There are a lot of unmatched terms there, though I do see a few that likely didn't match due to not exact string. For example, 'adult T-cell leukemia' in DO has exact synonym 'Adult T-cell leukemia/lymphoma' which matches to MeSH 'Lymphoma, T-Cell' on your list of unmatched terms. The DO term has an xref to the NCI term 'Adult T-Cell Leukemia/Lymphoma' (Code C3184). (though DO's use of exact synonyms is perhaps a bit greedy) |
Warning: some results are kind of odd E.g. MESH:Starvation is a DOID nutrition deficiency disease Issue #15
@cmungall that mapping comes from DO (originally in the format DOID:0005566::D013724 | DOID:0005563::D013724 | DOID:0003307::D013724) and hence I assume the DO people tried to relate terms at different levels of specificity (i.e., the more specific DO terms to the more general MeSH term). W.r.t. the padding - is there something I can do to fix it? |
@cmungall I couldn't find additional mappings for the list you've compiled there. |
@tudorgroza - I see, those were the xrefs already in DO. My list should subsume these. @mellybelly the CTD list subsumes mesh_list.txt, with the exception of MESH:D012203 Rh isoimmunization, which is in DO already as an xref so we don't need an extra class |
Didn't remember to tag the commit, but mondo now has mesh classes, either as equivalents to existing mondo classes, or sometimes as their own class with subclass axioms to existing mondos. This can lead to some oddities, e.g.
because there is no generic ependymoma in mondo. But this is better than alternatives |
…y be to mondo pre mesh merge. Issue #15
…y be to mondo pre mesh merge. Issue #15
Disregard my previous comment. Was not aligning mesh to the correct target. Fixed this. PD graph now looks better (stll oddities from ordo, but at least all mesh is now tucked in with the relevant OMIM or DOID or Orphanet class). Hmm, PD3 is still a problem. But at least the others mostly are incorporated correctly. |
This issue was moved to monarch-initiative/monarch-disease-ontology-RETIRED#23 |
see required classes in directory
https://github.com/monarch-initiative/human-disease-ontology/tree/master/src/contrib/MesH.contrib
The text was updated successfully, but these errors were encountered: