OEO does not load in protege (HTTP 500)

[MGlauer]

Description of the issue

Using the OEP IRI of the OEO yields a HTTP 500 response (Server error).

Steps to Reproduce

1. Open Protege
2. File -> Open From URL
3. Enter "https://openenergyplatform.org/ontology/oeo/"
4. Click "Ok"

Context and Environment

• Version used: Accessed on May 27th 2024
• Operating system: Linux (Ubuntu, Firefox)
• Environment setup and (python) version: -

Workflow checklist

• [ x ] I am aware of the workflow in CONTRIBUTING.md

[jh-RLI]

What is the main file that is expected here? I assume the full-oeo.owl from the oeo release? Or are all the files from the release are required (it's been a while since I used Protege ... but will use it again soon). @l-emele @adelmemariani

[l-emele]

I don't get a HTTP 500 error, but a 503 error when trying to open https://openenergyplatform.org/ontology/oeo/ in Protégé.

I also get a 503 error when trying to open https://openenergyplatform.org/ontology/oeo/releases/oeo-full.owl

And I also get a 503 error, when opening https://openenergyplatform.org/ontology/oeo/ in the browser.

Related to: https://github.com/OpenEnergyPlatform/ontology/issues/1847

[jh-RLI]

And I also get a 503 error, when opening https://openenergyplatform.org/ontology/oeo/ in the browser.

It seems like the OEP stopped working a few minutes ago! Looking into it.

[han-f]

just posted this from another viewpoint: #1692

[jh-RLI]

At the moment the Oep is down ... I'm waiting for someone with more permissions to restart the server.

There is an unexpected error.

[wingechr]

This is my fault. I am currently running some database intensive tasks in preparation for the migration. I had hoped to finish it over the weekend but hopefully will do so tonight. The platform is running again but might be a bit slow today. Sorry for the inconvenience

[jh-RLI]

@MGlauer Is it working again? At first I thought the problem was related to https://openenergyplatform.org/ontology/oeo/ not providing the files. Now I'm not sure if it's just because the oep was down yesterday.

The oeo-full.owl is currently returned via this URL: https://openenergyplatform.org/ontology/oeo/releases/oeo-full.owl

We're planning to rework the oeo pages a bit more before the end of SIROP, so I'm open to a few new feature requests or ideas for restructuring what we currently have. In particular, the URLs that provide the files should follow a common pattern and currently I don't have a good overview of how others are doing this.

[l-emele]

I can confirm that the original problem still exists. Instead of the 503 error, I now get a 500 error when trying to open OEO in Protégé via the URL.

Server returned HTTP response code: 500 for URL: https://openenergyplatform.org/ontology/oeo/

[wingechr]

Then it has nothing to do with my backup job. The error logs on the oep show something like:

ValueError: The view ontology.views.OntologyOverview didn't return an HttpResponse object. It returned None instead.

[jh-RLI]

Yes, the views for the overview page are still a bit of a mess. I've started to restructure them and possibly remove the code that returns the files. Now I understand why the page was returning it like this (It shouldn't return an http 500, but rather a 415 the way it is implemented ATM).

In the future /ontology/oeo/ will only return the file and no more html content as the html content will be added to /ontology/ instead of /ontology/oeo/. Nevertheless, there is a lot of code that provides the same functionality, e.g. /ontology/oeo/releases/oeo-full.owl also provides the owl file.