Follow up for JIRA ticket

[zoependlington]

I have been exchanging emails with Jason Hilton regarding the Webulous submission process now we have migrated to GitHub. During this exchange, Jason brought up an old JIRA ticket that was unresolved. Pasting the question and linking the ticket to look into.

Hi Zoe,

Thanks for confirming the submission process.

The outstanding question on the JIRA ticket ((https://www.ebi.ac.uk/panda/jira/browse/FGPTO-1193) was regarding Jurkat E-6.1 cell.
ENCODE restricts our submitters to using EFO terms (specifically, with EFO namespace), so a BTO term would not suffice.
The ticket was left with an unanswered question to Simon.

Perhaps I could further understand this situation if I knew better the relationship between BTO and EFO.
For example, I see EFO:0001086 is for A549, but Brenda also has this term as BTO:0000018. So there are at least some cases of overlap between the two ontologies, and I’m not understanding when that is acceptable.

Cheers,
Jason

[zoependlington]

In reply from Jason:

We will include a search of BTO & CLO for terms before submitting to EFO for term creation.

We are also initializing a review of the cell line coverage in BTO & CLO to decide if we should incorporate those ontologies.

If these ontologies are able to be incorporated, then we will be able to close this ticket. If not, we may have to create a new term to replace the BTO term. This is also applicable in #242, where we may be able to import terms if this is acceptable.