-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operation to auto-add curation status #2
Comments
The OBI build tool has an ugly class that checks our minimal metadata rules and updates terms: SPARQL Update would be much better for expressing the rules. I think we'd have to switch from OWLAPI to Jena then back to OWLAPI. Is there an efficient way to do this? |
I'm not aware of a bridge layer. |
I'm using this SPARQL for OBI and it's working fine: https://github.com/obi-ontology/obi/blob/master/src/sparql/add-curation-status-construct.rq |
excluding SubsetProperty
At NCEAS meeting. Seems would be very useful to have better population of IAO curation status field. This could be partly automated (e.g. no def means not approved). If the TBN tool could generate these (by a configuration that is configurable on a per-ontology basis) that would be useful. May be as simple as a SPARQL UPDATE
The text was updated successfully, but these errors were encountered: