Principles for merging terms: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Merge Procedure==
[[Merging Ontology Terms]]
==What is a GO term merge?==
==What is a GO term merge?==
Term merges result from two or more terms being subsumed into a single term.
Term merges result from two or more terms being subsumed into a single term.
Line 7: Line 10:
* The meaning is too close to support consistent, distinct annotations
* The meaning is too close to support consistent, distinct annotations
* The distinction between a parent and a child is not useful or necessary in the scope of GO
* The distinction between a parent and a child is not useful or necessary in the scope of GO
Care should be taken when merging terms that may be used elsewhere, because it may create false assertions (annotations), in particular NOT. Also if terms are used for logical definitions, then that may create incorrect assertions.
TO PROPOSE AT AN ANNOTATION CALL: '''Whenever possible, obsolete term with 'REPLACED BY' rather than merging terms'''.


==What happens when GO terms are merged?==
==What happens when GO terms are merged?==
When terms are merged, e.g. term A and term B are merged into term A, the GO ID of term B is made an alternative (secondary) GO ID, and the term string is made a synonym. Secondary GO IDs remain in GO with the 'alt_id' tag.
When terms are merged, e.g. term A and term B are merged into term A, the GO ID of term B is made an alternative (secondary) GO ID, and the term string is made a synonym. Secondary GO IDs remain in GO with the 'alt_id' tag.


++ Add example
  ++ Add example
 
 
== Review Status ==


Last reviewed:


[[Ontology_Development#Editing_the_Ontology |Back to: Editing the Ontology]]


[[Category:Curator_Guides]][[Category:Ontology]]
[[Category:GO Editors]][[Category:Ontology]][[Category:Editor_Guide_2018]][[Category:To be reviewed]]

Revision as of 12:49, 26 October 2020

Merge Procedure

Merging Ontology Terms

What is a GO term merge?

Term merges result from two or more terms being subsumed into a single term.

When are GO terms merged?

Common reasons to merge terms include:

  • Terms have exactly the same meaning
  • The meaning is too close to support consistent, distinct annotations
  • The distinction between a parent and a child is not useful or necessary in the scope of GO


Care should be taken when merging terms that may be used elsewhere, because it may create false assertions (annotations), in particular NOT. Also if terms are used for logical definitions, then that may create incorrect assertions.

TO PROPOSE AT AN ANNOTATION CALL: Whenever possible, obsolete term with 'REPLACED BY' rather than merging terms.

What happens when GO terms are merged?

When terms are merged, e.g. term A and term B are merged into term A, the GO ID of term B is made an alternative (secondary) GO ID, and the term string is made a synonym. Secondary GO IDs remain in GO with the 'alt_id' tag.

  ++ Add example


Review Status

Last reviewed:

Back to: Editing the Ontology