The OMO import is bringing in duplicate annotations for IAO terms

[hoganwr]

We should see if there's a way to fix it. One thought is that if IAO itself imports OMO in its entirety, and OMRSE imports IAO in its entirety, then there's no rationale for a separate OMO import and we might consider removing it. However, if those conditions do not hold, then we would need to consider a wider range of options.

[matentzn]

In this case, its probably better to import IAO as a base file rather than the whole thing, and OMO as the whole, as this is the "official" reference for OBO metadata specification.

[hoganwr]

Discussed at OMRSE meeting, and we wish to change the IAO import to base file. If we switch to base_merging, do we then have to do all imports as base files? Or will it just do a base merging process for those imports that have a use_base: TRUE or make_base: TRUE entry?

[matentzn]

you dont need base merging for that, just set "make_base: TRUE" for IAO and you should be good.

[matentzn]

(if you want to use base_merging I am suggesting yes, all ontologies should use either use_base or make_base, apart from OMO which you leave as is)