Open rschalkrce opened 1 year ago
Examples:
RKD Artist: schema:Person or schema:Organization as top concepts
If types are not nicely defined in the data, we could use substrings from URI's to define them manually per term list, like this for e.g. Koloniaal Verleden:
Optional{ FILTER(REGEX(?label, "persoons") || REGEX(?label, "geografi")) BIND ( IF ( REGEX(?label, "persoons"), schema:Person, IF (REGEX(?label, "geografi"), schema:location, "" )) AS ?type) }
And then add to the Construct
:
?uri skos:hasTopConcept ?type
We decided to discuss this idea and its feasibility – can publishers differentiate between types in their SPARQL queries? – in a meeting together with publishers and users.
As discussed with @ddeboer, another option could be to add a 'terminology resource recommender' to users, or an interactive flowchart. This tool would suggest useful terminology resources based on e.g. types of terms required (people, places, materials etc.), or perhaps even popularity of a certain thesaurus within cultural heritage (if we can think of a suitable metric - perhaps the NDE knowledge graph in the future).
This would bypass the issue of having to manipulate the source data but would help users of the Termennetwerk, especially with the ongoing uptake op terminology resources.
With more term lists being added users may want to differentiate between categories of terms, i.e. only search within type person, organization, material, etc. We could experiment with manually adding
skos:hasTopConcept
to the search and lookup queries and use this to filter results, or narrow a search.This would require:
proposing a limited number of
skos:hasTopConcept
to group termstest if we can write
CONSTRUCT
queries per term list that will add theseskos:hasTopconcept
to the search results.