Skip to content
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

Proper error message for non-existing OEO class #1806

Open
1 task
l-emele opened this issue Aug 29, 2024 · 2 comments
Open
1 task

Proper error message for non-existing OEO class #1806

l-emele opened this issue Aug 29, 2024 · 2 comments
Labels

Comments

@l-emele
Copy link
Contributor

l-emele commented Aug 29, 2024

Description of the issue

When one opens the IRI of a non-existent OEO class/individual/property, e.g. https://openenergyplatform.org/ontology/oeo/OEO_99999999/ then an almost empty page is shown:

grafik

The user does not get any feedback that she or he requested a non-existing entity.

Ideas of solution

Ontobee is a good example how to handle this: For a non-existent IRI the user gets a delievered a proper error message. For example, http://purl.obolibrary.org/obo/BFO_1234567 gets as usual1 redirected to https://ontobee.org/ontology/BFO?iri=http://purl.obolibrary.org/obo/BFO_1234567 but it has the following content:
grafik

Workflow checklist

Footnotes

  1. OBO IRIs always redirect to Ontobee

@l-emele l-emele added the bug label Aug 29, 2024
jh-RLI added a commit that referenced this issue Aug 30, 2024
@jh-RLI
Copy link
Contributor

jh-RLI commented Aug 30, 2024

A check has been added that now prevents the empty page from being displayed. It checks if the class name is available. Only the general 404 page is displayed. A more precise 404 page would be better, but I can't do it now :/

@l-emele
Copy link
Contributor Author

l-emele commented Sep 2, 2024

I think a 404 page is sufficient at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants