Chapter 9

Taxonomies

Define structured workflow labels, relationships, and conditional branching pathways that drive dynamic task routing across workflow nodes.

Overview

Taxonomy is used to define structured workflow labels, such as escalation-related options, that can be used to guide task routing or workflow decisions. Taxonomy labels cannot be used for data annotation; annotation labels are defined separately within the project template.

Taxonomy Components

  • Labels (Classes): The categorisation labels (e.g. "Vehicle", "Pedestrian", "Requires Escalation").
  • Relationships: Named semantic interactions between different labels (e.g. "has-part", "associated-with").

Guide: Creating a Taxonomy

Step-by-Step Guide

1

Navigate to Taxonomies

Click Taxonomies in the left sidebar and click the blue Create Taxonomy button.

Figure 46: Create Taxonomy Page

Figure 46: Create Taxonomy Page

2

Enter Name and Description

Provide a clear taxonomy title (e.g. Escalation Required) and optional usage notes.

3

Add Labels

Under the Labels section, type a label name and click Add Label.

4

Configure Multiple Labels

After creating one label, you can add more. Enter another label name and click Add Label again to add multiple labels. For each label, set: Name, Color (hex code), optional Alias, and Default (optional).

Figure 47: Taxonomy - Add Label

Figure 47: Taxonomy - Add Label

5

Set Default Label

The first added label is automatically marked as default. You can select another radio button to make it the default, or click the selected radio button again to deselect it (leaving no default).

6

(Optional) Add Relationships

Specify a Name, Color, and optional Description for each relationship. (Note: Relationships currently do not serve a specific functional routing purpose).

7

Click Create

Click Create to finalize and publish the taxonomy.

Managing Taxonomies

View, search, filter, and paginate through all company taxonomies from the Taxonomies dashboard.

Deleting Taxonomies

From the Taxonomies list, select the taxonomy you wish to delete and click the Delete icon, then confirm in the prompt.

Figure 48: Taxonomy - Delete Action

Figure 48: Taxonomy - Delete Action

Figure 49: Taxonomy - Delete Confirmation

Figure 49: Taxonomy - Delete Confirmation

Active Project Attachment
You cannot delete a taxonomy if it is currently attached to an active project. You must remove it from the project settings first.

Viewing Taxonomy Details

When a user clicks on any taxonomy in the list, an interactive Details Panel slides open automatically on the right side of the page, displaying:

  • Taxonomy Name: Displays the name of the selected taxonomy.
  • Labels: Displays all labels that have been added to the selected taxonomy
  • Relationships: Displays any relationships configured for the selected taxonomy
  • No Relationships Found: If no relationships have been added, an appropriate message is displayed
  • Automatic Panel Opening: The details panel opens automatically as soon as the user clicks on a taxonomy from the list.
  • Close Panel: The user can close the details panel using the Close (X) button.
Figure 50: Taxonomy - Details Panel

Figure 50: Taxonomy - Details Panel

Taxonomies in the Annotation Task

  • When an annotator opens a task, the taxonomy is shown in a collapsible panel above the file viewer.
  • If a Default label is set, it is pre-selected when the task opens. Annotators can change the selection while annotating a task.
  • The taxonomy section is independent from task templates.

Workflow Routing via Taxonomies

Taxonomy values can control a task's journey through the workflow. When a task is submitted, downstream Plugin nodes receive the taxonomy selection, enabling conditional routing.

Example: A taxonomy named “Escalation Required” contains the labels “Yes” and “No.” During the annotation process, the annotator selects one of these labels based on whether the task requires escalation. Once the task moves to the downstream Plugin node, the external agent connected to that node can access the taxonomy selection made by the annotator. Based on the selected value, the external agent can route the task through the appropriate output path of the Plugin node — for example, selecting “Yes” routes the task to the escalation pathway, while selecting “No” routes it to the standard completion pathway.

Note
Currently, taxonomy labels are used only for workflow-based task routing and cannot be used for annotating data. Annotation labels are defined separately within the project template. Taxonomy selections made by users can be accessed by an external agent through a downstream Plugin node, which can then use the selected value to route the task to the appropriate workflow path.
Code copied to clipboard!