-
Notifications
You must be signed in to change notification settings - Fork 51
IdenticalDefinition
Nicole Vasilevsky edited this page Mar 15, 2019
·
3 revisions
- If the two classes are "highly similar" (read text-def) and one of them just needs another qualifier like progressive, localised, pathologic,... just add the qualifier. If the qualifier is not in PATO, but is a candidate for PATO, then let's discuss. You can add a new term request to the PATO tracker.
- If the two terms are highly similar, but one of them has a text-def that clearly separates them from the other term, and we don't have way to express this difference in OWL, remove the logical def of the more specific class. (Check set of ancestor classes)
- If the two classes are really equivalent, check the set of ancestors. If one of them has ancestors that should apply to the other class, then file an HPO ticket on the HPO tracker.
- If the two classes are really equivalent, check the set of ancestors. If one of them INCORRECTLY has ancestors that the other does not have, then file an HPO-ticket on the HPO tracker.
- If the two classes are really equivalent (i.e. also have the 'same' set of ancestors) then merge them. (Please be very cautious with term merging as this has consequences for annotation data all over the world. Ask @pnrobinson, @cmungall, or @drseb for merge-instructions if you need a reminder)