Follow redirect to terminology server

[KonradHoeffner]

I want to have some test data in my local copy of the framework, so I exported "BMI-Schulung" as TopJsonFormat in https://top.imise.uni-leipzig.de/. However when I import that in my local copy, I get the following error on the console and no feedback on the frontend.

backend-1   | 2024-02-14 10:06:50.384  INFO 1 --- [nio-8080-exec-9] org.reflections.Reflections              : Reflections took 211 ms to scan 4 urls, producing 137 keys and 535 values
backend-1   | 2024-02-14 10:06:55.098 ERROR 1 --- [nio-8080-exec-9] c.s.t.b.r.ols.CodeSystemRepository       : 301 Moved Permanently from GET https://www.ebi.ac.uk/ols/api/ontologies?page=0&size=1000; nested exception is org.springframework.web.reactive.function.UnsupportedMediaTypeException: Content type 'text/html' not supported for bodyType=care.smith.top.backend.service.ols.OLSOntologiesResponse

bmi-schulung.json

The page https://www.ebi.ac.uk/ols/api/ontologies?page=0&size=1000 redirects to https://www.ebi.ac.uk/ols4/api/ontologies?page=0&size=1000.

I propose the following changes:

• [x] change https://www.ebi.ac.uk/ols/api/ontologies?page=0&size=1000 to https://www.ebi.ac.uk/ols4/api/ontologies?page=0&size=1000 (I don't know where in the interface this can be changed) in the configuration of BMI-Schulung
• [x] follow 301 redirects in the backend and print a warning
• [ ] report backend errors and warnings in the frontend, because otherwise users that don't have a docker compose log window open will not notice that something went wrong

[ChristophB]

Hi, I cannot reproduce this error with the standard configuration provided in docker-compose.env.tpl, but setting TERMINOLOGY_SERVICE_ENDPOINT to "https://www.ebi.ac.uk/ols/api" shows the warning you described.

So I think your first task can be skipped, but 301 redirects really need to be handled correctly.

BTW, the error is not directly related to the phenotype import.

[KonradHoeffner]

I think I already changed it from ols to ols4, maybe that is why the error didn't occur anymore?

[ChristophB]

I think I already changed it from ols to ols4, maybe that is why the error didn't occur anymore?

Yes, but I think the changes I made are still useful.

[KonradHoeffner]

Absolutely agree! However it does not seem to work, I am investigating whether my local version still runs an old version and not the newly build one.

[KonradHoeffner]

The error is thrown in care.smith.top.backend.repository.ols.CodeSystemRepository which extends OlsRepository where your pull request handles redirects, is it possible that the error is thrown by another method? Does it not occur in your local installation?

[ChristophB]

I don't get an error and I think this is the only place where an OLS web client is built. Actually, this is not my code, so it could be that I missed something.