Closed cmungall closed 3 years ago
I am making the repo. Will need some tidying to look like a normal editfile
@TomConlin note to self figure out populating this from dipper
@cmungall, is this correct that before makeing a release, we download the turtle dump from dipper using a make goal like:
edit:
wget https://data.monarchinitiative.org/ttl/monochrom.ttl -O chr-edit.ttl
Seems that your current chr-edit.ttl differs massively (huge diff, but also things like ontology header which is not present in the dipper dump). What other processing does chr-edit.ttl need after the above download?
Yes, something like that (apologies, I should have included this in the Makefile). It looks like it was passed through the owlapi in the first place (the Error1s).
Are you sure the diff is so large? Is this ascii, rdf-level, or owl-level?
Note also this would be the point of comparison (or even the version before this). https://archive.monarchinitiative.org/201907/ttl/monochrom.ttl
I would not worry too much about replicating the original edit file. There was no manual massaging. Let's just start with the existing one and move forward. There are some oddities to deal with. Not sure if it makes sense to fix these as dipper or as post-processing.
The main oddities are in the rdf/owl conversion.
Ah I only now saw this with the OWL errors - this needs to be fixed at dipper level.. I made a separate ticket: #2
I updated the ODK to the latest version and included the monochrom dipper dump as a component in the pipeline - now its all handled correctly..
I will include monochrom now as part of Monarch OLS, but I have not dealt with the Error classes yet, nor have I looked at the labels "ensure all labels are included" -> How do I do that?
dupe w #10
minimal for release
OWL error:
things to include in future
not urgent, just good to have them tracked