Open stuchalk opened 4 months ago
The above example and others I have now found indicate the issue is if a field is empty. Could literal string fields be setup as optionally none?
Hi @stuchalk , do you know if the tib.eu
OLS server is using OLS3 or OLS4? I'm not sure if this is a difference arising due to that, I'm only trying to support OLS4 at this point (but ideally they should be compatible).
It's always possible I've misspecified the schema based on limited examples, I'll have a look and see if this can be fixed.
Hi @stuchalk & @marius-mather, we're still using OLS3 as the switch to the OSL4 API needs more work than expected with our setup, so that might be the reason.
I am trying the following two API calls for the same ontology (other ontologies give the same difference) on different OLS servers:
The outputs (JSON) are the same (in structure) from the two servers so I think this is an issue with ols-py. Here are the outputs I am getting: