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
Change default OLS viewer to OLS4 #922
Conversation
The double percent signs are important, because this string is being run through Python string formatting, which also uses percent signs ( This line in the tests will also need to be updated: purl.obolibrary.org/tools/test.py Line 179 in d0f9167
|
IDSPACE should be CHEMINF. The tests should have caught this.☹️
@lschriml @allysonlister and Robert Thacker have confirmed, @dosumis not (but I know he wants this). @mcourtot I am also sure will agree, so I will take the blame for that. Remains the blocking OLS issue above! |
Didn't realize this was pending confirmation - all good to me, thank you! |
Ok last problem, no idea whats that about: Seems that the OLS PURL send back a HTTP 303. @serjoshua @udp - any idea why that is? If you click on the URLs they resolve, albeit a bit indirectly and slowly.. |
Don't worry about the fact that the code is "303". There was a decision many years ago to use "303 See Other" for term IRIs. The problem is that the expected and actual URLs aren't matching up. Not sure why. |
@@ -176,8 +176,7 @@ def process_product(i, product): | |||
|
|||
|
|||
ontobee = 'http://www.ontobee.org/browser/rdf.php?o=%s&iri=http://purl.obolibrary.org/obo/' | |||
ols = 'https://www.ebi.ac.uk/ols/ontologies/%s/terms?iri=http%%3A%%2F%%2Fpurl.obolibrary.org%%2Fobo%%2F' | |||
|
|||
ols = 'https://www.ebi.ac.uk/ols4/ontologies/%s/entities/http%%253A%%252F%%252Fpurl.obolibrary.org%%252Fobo%%252F' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jamesaoverton I got the tests to pass. Note that I am a bit confused why I needed to double encode the entity IRI here to get it to work, but I think its because they moved from "URL parameter" syntax (?iri=) to "URL path" syntax.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, moving from the query string into the path seems to require the extra escape. It's very ugly but it seems to work fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just reviewing some OLS4 tickets and stumbled upon this. We do support ?iri=
, ?shortForm=
and ?oboId=
(?curie=
) for /terms and /entities. What we do not support on the frontend is ?id=
. If you encounter any discrepancies, let us know. Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested locally and convinced myself that the extra escapes are required.
I'll merge this tomorrow morning when we're both at our desks.
fixes #920
Blocked by