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
Some obsolete classes have exact mappings to the orphanet:disorder.
We should review these obsoleted terms and check whether we still agree with this obsoletion or we should reinstate the term
@matentzn Could you please add the orphanet ID to this spreadsheet?
I am assuming that we are looking at obsoleted Mondo terms which have an x-ref to a specific orphanet, however when looking at the spreadsheet, I have seen:
Mondo obsoleted terms with no orphanet x-ref
orphanet x-ref (that, based on name, could have been the one missing) that have been removed from orphanet.
Mondo term (not obsoleted) with orphanet x-ref but the orphanet name is the same as an obsoleted Mondo term
Therefore I would like confirmation of
which orphanet x-ref is expected for these obsolete terms (ie which orphanet terms are actually mapped to Mondo obsoleted terms) based on the files used to create this spreadsheet.
where these mappings came from and how they were made (I suspect that some of them are only on term label)
If the "exact_matches" column is empty, we have only a synchronicity problem: The subset sync pipeline and the mappings are intricately linked. So the issues will solve themselves with the next update.
Based on #7681 (comment)
Some obsolete classes have exact mappings to the orphanet:disorder.
We should review these obsoleted terms and check whether we still agree with this obsoletion or we should reinstate the term
The text was updated successfully, but these errors were encountered: