Ontology description page shows wrong URL when using custom (non-OBO) ontologies

[ashkotin]

on the page https://monarch-initiative.github.io/monarch-ontology-dashboard/dashboard/chr/dashboard.html the URL for chr in "Dashboard Report - chr" raises 404.

[matentzn]

Thank you for the feedback.

@anitacaron (not now, obviously) I think this should be fixed by redirecting the URL from the ontology description page to mirror_from if it exists, but we should make sure that this does not break the normal "OBO" dashboard.

[ashkotin]

OK. And how to get chr description? On https://monarch-initiative.github.io/monarch-ontology-dashboard/dashboard/chr/dashboard.html owl http://purl.obolibrary.org/obo/chr/releases/2023-02-19/chr.owl looks strange for me and Protege 5.5.0.

[anitacaron]

Maybe this should be the ontology's homepage, if available?

[matentzn]

@ashkotin yes these PURLs are misleading as CHR is not in OBO (yet). Here you can find the ontology https://github.com/monarch-initiative/monochrom, you can ask your questions on the issue tracker there

[matentzn]

@anitacaron For the OBO Dashboard, I would suggest that the link to the OBO Foundry page of the ontology is more appropriate, or at least, that it is somewhere accessible on the ontology description page (if it exists). However, if this becomes to complex, I think your suggestion is an ok enough compromise.

[ashkotin]

Super!

вт, 28 мар. 2023 г. в 10:20, Nico Matentzoglu @.***>:

@ashkotin https://github.com/ashkotin yes these PURLs are misleading as CHR is not in OBO (yet). Here you can find the ontology https://github.com/monarch-initiative/monochrom, you can ask your questions on the issue tracker there

— Reply to this email directly, view it on GitHub https://github.com/OBOFoundry/OBO-Dashboard/issues/88#issuecomment-1486342323, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASCVUMTELCM4G2LVOMPYVDW6KGLBANCNFSM6AAAAAAWJDPHFI . You are receiving this because you were mentioned.Message ID: @.***>

[anitacaron]

@matentzn My comment was related to the case of it's not an OBO Foundry ontology.

[matentzn]

Then yes, I agree!

[anitacaron]

But is there a straightforward way to know that ontology is not part of OBO?

[matentzn]

I think the best hack is to check if the mirror_from field is an obo purl. Maybe there are other pieces of metadata that could be used to determine but not sure

[ashkotin]

A variant is possible when chr authors are offered to create and fill in the corresponding page since it is in the OBO catalog.

вт, 28 мар. 2023 г. в 09:45, Anita Caron @.***>:

Maybe this should be the ontology's homepage, if available?

— Reply to this email directly, view it on GitHub https://github.com/OBOFoundry/OBO-Dashboard/issues/88#issuecomment-1486303204, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASCVUNG2DOZFJ6OAXNWOTDW6KCJZANCNFSM6AAAAAAWJDPHFI . You are receiving this because you authored the thread.Message ID: @.***>

[matentzn]

No all people using the dashboard want to have their ontologies on OBO!

[ashkotin]

It is just a page about ontology, not ontology itself.

вт, 28 мар. 2023 г. в 15:27, Nico Matentzoglu @.***>:

No all people using the dashboard want to have their ontologies on OBO!

— Reply to this email directly, view it on GitHub https://github.com/OBOFoundry/OBO-Dashboard/issues/88#issuecomment-1486795723, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASCVUNGHDPS7XZJIZ4L6ETW6LKK3ANCNFSM6AAAAAAWJDPHFI . You are receiving this because you were mentioned.Message ID: @.***>

[matentzn]

Yes, but the process to get that page is extremely complex! Lots of paperwork, not everyone will want that!

[ashkotin]

OK.

вт, 28 мар. 2023 г. в 19:34, Nico Matentzoglu @.***>:

Yes, but the process to get that page is extremely complex! Lots of paperwork, not everyone will want that!

— Reply to this email directly, view it on GitHub https://github.com/OBOFoundry/OBO-Dashboard/issues/88#issuecomment-1487253312, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASCVUN4RDVNVSAWRGYYCPLW6MHJPANCNFSM6AAAAAAWJDPHFI . You are receiving this because you were mentioned.Message ID: @.***>