-
Notifications
You must be signed in to change notification settings - Fork 3
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
A few synonym representation issues based on the review of the synonym sync "added" PR #191
Comments
(2) this is not an abbreviationThis is due to a mistake where there is a missing |
(3) synonym not parsed correctlyThis is a bug in the OMIM ingest. We should be splitting on |
(1) Synonyms that still have ", formerly"I'm not actually seeing this in You can see by looking at this file from one of our recent builds: https://github.com/monarch-initiative/mondo-ingest/blob/fix-ordo-mapping-data2/src/ontology/reports/sync-synonym/synonym_sync_combined_cases.robot.tsv There are some synonyms with "formerly". They are all DOID or NCIT, but none OMIM. |
(4) Synonyms that are marked exact when they should be related@twhetzel For a lot of the examples in (1), you also mentioned in the comment in #8584 that they were showing up as exact when they should be related. But I ran the synonym sync and they are all showing up in related. Let me know if you want me to post examples. |
For (4) - that's fine, that is just how they showed up in the diff mentioned in the original comment in this issue. |
Based on this PR review for this commit diff, there were a handful of very minor items related to representation of synonyms from OMIM. This ticket lists these issues to document them.
(1) there are a handful of synonyms from OMIM in the diff that still have "..., formerly" EXACT
Examples:
synonym: "ANOP1, formerly" EXACT [OMIM:301590]
(2)
synonym: "ERYTHROCYTE ADA, ELEVATED, HEMOLYTIC ANEMIA DUE TO" EXACT ABBREVIATION [OMIM:301083]
--> this is not an abbreviation(3) synonym not parsed correctly. The OMIM content is not being parsed correctly for https://omim.org/entry/609029 so the value
22)
is incorrectly represented as a synonym in omim.owl.These are all very minor issues and may be an issue with the omim data files and/or an issue already resolved.
The text was updated successfully, but these errors were encountered: