New release

[diatomsRcool]

The new term for maternal route is not usable until there is a new ExO release that OBO Foundry can pick up.

[matentzn]

Related to OBOFoundry/OBOFoundry.github.io#1446

[matentzn]

(exo is still broken because the berkeley release system does not work)

[cjgrondin]

Do you have any further details about how we can fix this? Is this problem widespread?

[matentzn]

Basically what you need to do is set up a release SOP! you could set up and https://github.com/INCATools/ontology-development-kit based repo, but also, more simply, you could have an SOP where one of your engineers simply runs a ROBOT command (ideally something like this) to generate an OWL release.. once you have that and you commit those files (exo.obo and exo.owl) to the top level of this repo, we can change the OBO purls to point here (I can do that for you). But you will have to come up with a process for release first!

[cjgrondin]

I've uploaded an owl-formatted version of ExO, and thought I created a Pull Request to view and discuss, but I'm not seeing it now. I also tried pasting in a new release version of exo.obo and exo.owl below this comment, but file format not supported. Working on Git terminology. Happy to discuss further via a zoom chat/share screen or follow other suggestions.

[matentzn]

How did you create the OWL formatted version of ExO? With Protege?

[cjgrondin]

My coworker (one of our engineers) used the robot tool to update the exo.obo file of 2/1/21, then used the robot tool to convert the exo.obo file into owl format.

[matentzn]

OK great. You can upload both files two the top level of the ExO repo with the Add files button:

src/ontology/exo.obo is now your edit file (the place you edit exo)

exo.owl
exo.obo

on the top level of the repo are the release files.

[cjgrondin]

Ok, I uploaded the two files using the Add file button and used the option to create a new branch to propose changes (didn't want to commit directly just in case additional steps were needed)

[cjgrondin]

Compare & Pull Request next?

[matentzn]

You can commit directly - you are not actually overwriting anything that previously existed!

[cjgrondin]

How do I get back to that option (to commit directly)?

[cjgrondin]

https://user-images.githubusercontent.com/22403969/110976198-9d8e1200-832e-11eb-850a-fb57223c8b64.png

[matentzn]

Go here:

master...cjgrondin-patch-1

and create a pull request and just merge it..

[cjgrondin]

Looks like it merged successfully. Thanks for your help!

[matentzn]

@cjgrondin no problem! Can you also rename exo 1.obo to exo.obo?

[matentzn]

or just merge this: #18

[matentzn]

Ok fixed the purls as well:
OBOFoundry/purl.obolibrary.org#744

@cjgrondin FYI