Description
This might be as relevant to Prez as well as Prez-UI.
Most of our data is labeled with usual dct:title, rdfs:label or skos:prefLabel triples :
- few of these are URI resources that can be reached through custom endpoints-generated links, i.e. instances of dcat:Catalog, dcat:CatalogRecord or dcat:Dataset in our case
- most of these are blank nodes of inner resources (dcat:Distribution, dcat:DataService, vcard:Individual,...) that often have similar or identical labels
While the search engine returns all these occurrences as expected, our 4.3 UI seems unable to render results corresponding to blank node matches :
Yet other instances instances such as the IDN's seems able to return instances of resources that are not part of the endpoints hierarchy.
Should we add custom object endpoints for each and every type or resource occurring anywhere in our actual data tree, and / or equivalent profiles ? Or rather go for a quick-win solution like labeling blank nodes resources with different predicates we could keep out of the search engine's scope?
Description
This might be as relevant to Prez as well as Prez-UI.
Most of our data is labeled with usual dct:title, rdfs:label or skos:prefLabel triples :
While the search engine returns all these occurrences as expected, our 4.3 UI seems unable to render results corresponding to blank node matches :
Yet other instances instances such as the IDN's seems able to return instances of resources that are not part of the endpoints hierarchy.
Should we add custom object endpoints for each and every type or resource occurring anywhere in our actual data tree, and / or equivalent profiles ? Or rather go for a quick-win solution like labeling blank nodes resources with different predicates we could keep out of the search engine's scope?