-
Notifications
You must be signed in to change notification settings - Fork 0
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
Expected behaviour with multiple mapped properties with different types #425
Comments
So it's more of a UI bug. When it's an object it needs to be shown as a link (for now, in the future we will fetch more data about it ) I assign @SirineMhedhbi to fix this. |
Fixed with ontoportal-lirmm/bioportal_web_ui#273 |
Penser a gèrer le cas ou les valeurs sont des objects (URI) pour les afficher comme des "boutons" |
@jonquet Done |
@SirineMhedhbi done where? you need to give a link to your commit fix or new PR and a screenshot so that we can see it. In this case, the commit is ontoportal-lirmm/bioportal_web_ui@67ff34c But for the PR, you will need to open a new one as a follow-up of this ontoportal-lirmm/bioportal_web_ui#273 (because already closed) Thanks; |
okay thanks |
@syphax-bouazzouni this is the new PR : |
We have an example of a SKOS resource in AgroPortal, which provides 2 definitons:
https://agroportal.lirmm.fr/ontologies/ANAEETHES/?p=classes
Which ends up in the API as

(the difference of types creates a non regular JSON structure)
Which ends up in the UI as

(Similar situation could happen with synonyms which are also mapped to a unique "synonym" property).
What is the expected behaviour when this situation occurs?
We can expect the display and the JSON being well structured.
The text was updated successfully, but these errors were encountered: