@LillyG901 I put some more information into the header of the PR.

What about confidence interval, which is also mentioned in the original issue?

Alright, thank you.

Since lower/upper confidence limit is a subclass of confidence interval and we import it with hierarchy confidence interval should be imported alongside the other parent classes.

I will check that this is the case, when I get to test the shell script.

I misinterpreted the hierarchy on the website I was looking at.
The terms were not related through being in a SubClass relationship, but rather a part of relationship.
That's why it didn't work as intended and I readded the term to the file.

cutoff and statistic have to have their parent classes imported, too, since they are not known by oeo.

Can you avoid importing all information of annotation properties? Most of the annotation properties are known by oeo. If we import them again, we have them twice (we had that in the past). Mentioning the IRI should be sufficient. But I am not sure how to achieve that automatically. Maybe you can find that out by reading the ROBOT documentation.

cutoff and statistic have to have their parent classes imported, too, since they are not known by oeo.

I assumed duplicates might cause problems, since we did not import e.g. the BFO parent classes of the iao classes that were imported.
I will fix this.

Can you avoid importing all information of annotation properties? Most of the annotation properties are known by oeo. If we import them again, we have them twice (we had that in the past). Mentioning the IRI should be sufficient. But I am not sure how to achieve that automatically. Maybe you can find that out by reading the ROBOT documentation.

I will look into it.

cutoff and statistic have to have their parent classes imported, too, since they are not known by oeo.

I assumed duplicates might cause problems, since we did not import e.g. the BFO parent classes of the iao classes that were imported. I will fix this.

Yes, you're right. You don't have to change that, sorry. We'll have to add the SubClassOf axiom in oeo-import-edits.owl

Alright after some research I found a way to remove the definitions of the annotation properties. If you open the stato-extracted file in Protege, you should now be able to see the IRI of the annotation property instead of the label and the term is no longer defined if you check the Annotation-Property tab.
I'm not sure, if this was the outcome you intended.
I can't remove them further, because I assume we want to keep the information they provide (e.g. the definitions of the terms).

I checked the other import files and we have never really done this before, so it would be great if someone could test this and make sure this is what I should be doing.

This looks good now, thanks.
Have you tested an import into oeo-shared?