This is a pilot project for the dynamic, automated generation of GO branches that have a completely regular structure.
Aim: All membrane component terms in GO should be specified as a table with columns for ID, design pattern, filler (in this case a membrane type), subsets, def_dbxrefs.
All terms added in this way should be visible to ontology developers. They should be flagged in some way (using a subset tag?) to make it clear that they should not be edited (any edits will be discarded when terms are generated). Editors will still be able to make relationships TO auto-generated terms (although that may not be necessary in this branch).
TODO:
[ ] Check all membrane component design patterns are fit for purpose.
[ ] Check for membrane component terms do not conform to current patterns
[ ] Script generation of spreadsheet representing current terms.
[ ] Develop pipeline/Jenkins job for term generation
[ ] Build will run nightly with an option for manual run
[ ] Terms will live in separate, imported OBO/OWL files.
This is a pilot project for the dynamic, automated generation of GO branches that have a completely regular structure.
Aim: All membrane component terms in GO should be specified as a table with columns for ID, design pattern, filler (in this case a membrane type), subsets, def_dbxrefs.
All terms added in this way should be visible to ontology developers. They should be flagged in some way (using a subset tag?) to make it clear that they should not be edited (any edits will be discarded when terms are generated). Editors will still be able to make relationships TO auto-generated terms (although that may not be necessary in this branch).
TODO: