Restoring an Obsolete Ontology Term: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
See [[Ontology_Editors_Daily_Workflow]] for creating branches and basic Protégé instructions. | See [[Ontology_Editors_Daily_Workflow]] for creating branches and basic Protégé instructions. | ||
==Notification== | |||
Send an email notification to <code>go-friends@mailman.stanford.edu</code> and create a ticket with the same announcement in the '''[https://github.com/geneontology/go-announcements GitHub Announcements Tracker]'''. | |||
==Protégé Process for Restoring an Obsolete Ontology Term== | ==Protégé Process for Restoring an Obsolete Ontology Term== |
Revision as of 10:20, 5 April 2019
See Ontology_Editors_Daily_Workflow for creating branches and basic Protégé instructions.
Notification
Send an email notification to go-friends@mailman.stanford.edu
and create a ticket with the same announcement in the GitHub Announcements Tracker.
Protégé Process for Restoring an Obsolete Ontology Term
- Navigate to the obsolete term
- In the annotation window:
- Modify the term label to remove 'obsolete'
- Modify the term definition to remove 'OBSOLETE.'
- Update the comment to Note that this term was reinstated from obsolete.
- Remove any replaced_by and consider tags by clicking on the (x) at the right-hand side
- Add Subclasses as appropriate
- Remove the owl:deprecated: true tag
- Run the reasoner
- Save.
See Ontology_Editors_Daily_Workflow for commit, push and merge instructions.