PAINT database update pipeline: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 20: | Line 20: | ||
b) does not have a 'replaced_by' tag -> output message xxx | b) does not have a 'replaced_by' tag -> output message xxx | ||
** etc ? | ** etc ? | ||
| Line 28: | Line 26: | ||
* 'View omitted annotation information' -> generated on the fly ??? | * 'View omitted annotation information' -> generated on the fly ??? | ||
** What types of messages ? tree changes information (missing nodes) - what else ? | ** What types of messages ? tree changes information (missing nodes) - what else ? | ||
==Managing new PTHR versions== | ==Managing new PTHR versions== | ||
Revision as of 12:50, 24 August 2018
Import EXP files
- File location:
Import ontology
- File location:
Integration with existing PAINT annotations
- Managing differences:
- Missing EXP evidence
- New exp evidence
(see for ex https://github.com/pantherdb/fullgo_paint_update/issues/10)
- Handling obsolete and merged terms
- obsolete terms: a) has a 'replaced_by' tag -> replace to the new term b) does not have a 'replaced_by' tag -> output message xxx
- etc ?
- List of messages for automatic changed: 'Comment' ('Update comment' in PAINT interface)
- What types of messages ? obsoletes, missing EXP... what else ?
- 'View omitted annotation information' -> generated on the fly ???
- What types of messages ? tree changes information (missing nodes) - what else ?