Global search not working correctly in Skosmos 3.3

[asferreira]

URL address of the page where you encountered the problem

https://agrotermos.dados.embrapa.br/busca/

Description of the problem

Different from what happens on the vocabulary search field, when an user type something on the global search field the dropdown list does not appear. If after typing the user clicks inside the search field, the dropdown
appears, but clicking one of the listed concepts does not open the concept page. Also the list seems to be formatted incorrectly.
It's worth mentioning that if user presses ENTER or clicks on the magnifier button, the search result page opens correctly.
I also noticed that errors are reported on the browser's debugger window while user is typing on the search field.

Additional information (e.g. screenshots) about the problem

1. Error reported on the debugger window:

Uncaught (in promise) TypeError: can't access property "skos:Concept", window.SKOSMOS.types is undefined
    renderType https://agrotermos.dados.embrapa.br/busca/resource/js/global-search.js:184
    renderedType https://agrotermos.dados.embrapa.br/busca/resource/js/global-search.js:238
    VueJS 3
    renderResults https://agrotermos.dados.embrapa.br/busca/resource/js/global-search.js:238
    VueJS 3
    renderResults https://agrotermos.dados.embrapa.br/busca/resource/js/global-search.js:204
    search https://agrotermos.dados.embrapa.br/busca/resource/js/global-search.js:106
global-search.js:184:23

2. Skosmos object snipped from the page source:

<script id="skosmos-global-vars">
window.SKOSMOS = {
  "content_lang": "",
  "explicitLangCodes": false,
  "lang": "pt-BR",
  "vocab": "",
  "pageType": "landing",
  "vocab_list": { "agrotermos": "agrotermos", "agrovoc": "agrovoc", "thesagro": "thesagro"  },
  "vocab_id": [ ],
  "waypoint_results": null,
  "search_count": null,
  "search_results_size": 20,
  "baseHref": "https://agrotermos.dados.embrapa.br/busca/","contentLanguages": { "es": "espanhol", "fr": "francês", "en": "inglês", "pt": "português", "pt-BR": "português (Brasil)" }
}
</script>

The browser you used when the problem appeared

Firefox 153.0
Google Chrome 150.0.7871.186

[osma]

Thanks for the report.

For some reason the SKOSMOS object is lacking the "types" field. I think that is the root cause of the problems you see.

[osma]

I suspect this could be related to the unionDefaultGraph setting in Fuseki. My hypothesis is that when unionDefaultGraph is not enabled, Skosmos will not find the types used in the vocabularies using a SPARQL query and then it will omit the "types" field, which will then lead to issues in Vue code that expects that field to be present in the SKOSMOS object.

Could you try enabling the unionDefaultGraph setting in your Fuseki configuration? I.e. something like this:

:tdb_dataset_readwrite
    a tdb2:DatasetTDB2 ;
    tdb2:unionDefaultGraph true ;
    tdb2:location  "/etc/fuseki/databases/skosmos" .

Also check that in your Skosmos config.ttl, the global SPARQL endpoint setting (top level skosmos:sparqlEndpoint) matches the vocabulary-level sparqlEndpoint setting (void:sparqlEndpoint) if you have one set at the vocabulary level.

[asferreira]

I've checked the Fuseki configurations and the Skosmos repository already has the unionDefaultGraph setting enable. Regarding Skosmos' config.ttl, we do not use void:sparqlEndpoint at the vocabulary level, just skosmos:sparqEndpoint.

I've also tried to add the void:sparqlEndpoint to the vocabulary configuration, but the problem still happens.

[osma]

Thank you @asferreira . Then there must be another reason for the missing types field.