Instances data table error alert for DATA4CPLUS

[syphax-bouazzouni]

When accessing http://agroportal.lirmm.fr/ontologies/DATA4CPLUS/?p=classes&conceptid=root#details we get the alert below

Caused by this ajax call http://agroportal.lirmm.fr/ajax/DATA4CPLUS/classes/http%3A%2F%2Fdata4c-plus.net%2Fadmin%2Fthesaurus%2Fread%2F1/instances?page=1&pagesize=10&search=&sortby=&order=&_=1646040948579

[syphax-bouazzouni]

source error : http://agroportal.lirmm.fr/ontologies/DATA4CPLUS/?p=classes&conceptid=http%3A%2F%2Fdata4c-plus.net%2Fadmin%2Fthesaurus%2Fread%2F151
The function get_classses that calls this route http://data.agroportal.lirmm.fr/ontologies/DATA4CPLUS/classes/http%3A%2F%2Fdata4c-plus.net%2Fadmin%2Fthesaurus%2Fread%2F151/tree in the backend don't work

[syphax-bouazzouni]

I think this is a two level error :

1 - (It might be) a modelisation error (or a modelisation pattern that we didn't implement) :

In the modilisation we have 3 topConcepts that are "Annual and perennial croplands" , "Forests, forest plantations and other wooded lands" and "Forests, forest plantations and other wooded lands".

But in fact the real topConcept is "http://data4c-plus.net/admin/thesaurus/read/0" that is not instancied (is not a concept)

Like this topConcept ("http://data4c-plus.net/admin/thesaurus/read/0") it's not defined in the thesaurus, Agroportal can't find it (see screenshot below)

2- Agroportal skos concept handling

First we didn't catch the error (if having a topConcept is not concept it's really one) in the parsing step. We should have an error status to tell us that a top concept is not defined

And second we might think to handle this case of concepts that are external

[syphax-bouazzouni]

The modelization error ( top concept "http://data4c-plus.net/admin/thesaurus/read/0" not defined in the thesaurus) was fixed, by the thesaurus maintainer.