Open jakebeal opened 1 year ago
Hi @jakebeal. What if the equivalent Sequence Ontology term of the feature is not defined.
Should I not write the feature itself or just leave the SO
equivalent term?
We want to make sure that every GenBank feature has a corresponding SO term.
Given that SO has a much richer vocabulary, I suspect that every feature should map to a term. If there are features that don't appear to have a corresponding term, or that are ambiguous, however, it should be discussed on this issue. If necessary, we can also put in placeholders and ask for new SO terms.
I could not find corresponding term of old_sequence
for example.
Checked the following links :
Sequence Ontology Search
Sequence Ontology Mapping
Attaching a relevant screenshot from the (Sequence Ontology Mapping) link:
Oh, that one's interesting... I've never actually encountered it on a sequence myself, so I was not familiar with it. And the mapping link that you found is excellent: I was not familiar with that before.
So given this, here's my thought on how to proceed:
The official list of supported GenBank features may be found at: https://www.insdc.org/submitting-standards/feature-table/#7.2
Most, but not all, are in the
gb2so.csv
andso2gb.csv
translation maps with equivalent Sequence Ontology terms; make sure that all are there.