-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add skos:hasTopConcept to differentiate or filter results #966
Comments
Examples:
|
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.The text was updated successfully, but these errors were encountered: