jamesamcl

Just to note this needs to be compared with OLS3 as we don't want to make breaking changes to the backwards compatible API.

The IDs used to be simple numbers in OLS3 but in OLS4 they are base64 strings. See: https://www.ebi.ac.uk/ols4/api/ontologies/agro/terms/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FPCO_0000031/jstree ```json [ { "id" : "aHR0cDovL3B1cmwub2JvbGlicmFyeS5vcmcvb2JvL1BDT18wMDAwMDMx", "parent" : "#", "iri" : "http://purl.obolibrary.org/obo/PCO_0000031",...

The "parent" field indeed contains a base64 string of a concatenated list of ancestors, because that's the only way to uniquely identify the parent node (as the same class can...

@henrietteharmse Are these use cases being tracked somewhere since the issues are being closed? EDIT: I just realised this sounded critical, sorry it really wasn't, I just worry about losing...

We do actually have a widget for the current tree view, it's just not being published anywhere at the moment. You can build it from the OLS4 repo like this...

(Reopening because it would be nice if the docs I wrote above didn't get lost, but up to @henrietteharmse what to do with them)

Thanks, @haideriqbal lets look at this next Thursday when we are in the office

I chatted with @dosumis about this over lunch and he said that not every combination of URI format/ID would produce a valid link. I am not sure the OLS dataload...

> I've spent the past few years discouraging full URLs in xrefs as an extra burden on ontology users - who need to distinguish CURIE prefixes from protocol prefixes when...

Yes or use robot to convert them on the command line http://robot.obolibrary.org/