Closed ahwagner closed 6 years ago
@ahwagner
Yes, in short, this is intended behavior. The 'heirarchy' field would show the id number you expect, as well as the rest of the tree to the root feature classification. The 'parent_soid' refers to the highest level of the tree, or the 'root' classification.
In general the behavior of the mutation classifier needs some cleaning in terms of now traversing the tree all the way to the root in all cases, because root classifications of 'sequence_feature' don't really help.
Also, the name 'parent_soid' could be changed to something better descriptive, if desired.
Thank you for clarifying @mayfielg. We should change the field name to root
or something similar then. I think that the atypical use of the term parent
may be misleading here. Also, I agree that we will need to reconsider our strategy on comparing within and between ontologies. If there is time, I will bring the topic up in our VICC call tomorrow.
SOID terms contain sequence ontology root concept as "parent". Is this the intended behavior?
It looks like this was implemented by @mayfielg here.
Example association below (
'soid': 'SO:0001019', 'parent_soid': 'SO:0000110'
. Expected'parent_soid': 'SO:0000248'
)