Taxonomy Concepts Panel

The Taxonomy Concepts Panel displays a hierarchy with Concept Schemes as their roots and Concepts as tree nodes. The nodes of the hierarchy represent a broader-narrower relationship from top to bottom.

For users with edit permissions, the hierarchy can be rearranged using drag and drop, and, as usual, right-clicking on individual nodes offers further actions, see Context Menu, Explore Menu and Modify Menu.

The Tabular Reports Panel can be used to display a report about the usage of all terms in a taxonomy across asset collections.

Ordering of Concepts

By default the taxonomy tree nodes are ordered by their display labels. However, if the Home Asset (owl:Ontology) of the taxonomy declares a teamwork:taxonomyTreeOrderByExpr then this expression will be used for ordering. The value of this property needs to be a SPARQL expression that takes the URI (string) of the current tree node as pre-bound variable $value and produces a value such as an integer that shall be used for comparison with the other nodes.

Defining the Default Type of New Concepts

When creating new concepts, the dialog will by default use skos:Concept as the type of the new instance. If your ontology defines subclasses of skos:Concept, and you want to use those subclasses at specific levels, you can use the following mechanism in an Ontology:

g:Continent
  a owl:Class ;
  a sh:NodeShape ;
  rdfs:label "Continent"@en ;
  rdfs:subClassOf g:GeoConcept ;
  sh:property [
    sh:path [ sh:inversePath skos:broader ] ;
    sh:class g:Country ;
  ] ;
.

In the example above, the sh:property shape will tell the tool that when the user creates a sub-concept of a Continent, the dialog will use g:Country as the (default) type for the new concept.

Toolbar Buttons

  • Create Concept Scheme… opens a dialog allowing you to create a new top-level concept scheme.

  • Create Concept… opens a dialog allowing you to create a new concept at the current level of the hierarchy.

  • Quick search can be used to navigate to concepts based on the first few characters of their label.

  • Switch to full-text search activates a search mode in which not just the labels but any property can be found.

    This is usually slower than label-based quick search.

  • Expand one more level opens all currently visible but collapsed nodes one level deeper, loading their children as needed.

Settings

  • Show only locally defined concept schemes filters the hierarchy so that those concept schemes that are included from other asset collections are hidden.

  • Also show assets marked as hidden will, as the title says, also show those concepts that have dash:hidden set to true.

  • Show rich tool tips enables a detailed tooltip popup when hovering over a concept or concept scheme, showing a summary of the resource including its type, defining collection, and key properties.

  • Display IDs instead of labels toggles between human-friendly labels and machine-friendly qnames.

See Also

Further Reading on Taxonomies

Further Reading on TQ Data Foundation