Build your taxonomy
After selecting a use case or template, you will then access a set of labels to build your taxonomy.
If you are using our visual editor, you will be able to add labels and attributes from the dropdown menu. You can remove labels by clicking on the trash icon next to each label. If you would rather create your task with a JSON according to our API docs, you can copy and paste the JSON directly into the JSON editor. Note that you can switch between the visual and JSON editors as you are building your taxonomy.
A common workflow customers often follow is to use our visual editor to design their task interface so that they can use the outputted JSON when creating tasks via API.
As you are building your taxonomy, you can also see what your task looks like by clicking on the Task Preview. In this preview, you will also be able to replicate the labeler’s experience when they interact with your taxonomy.
Depending on the use case, you will also be able to configure label-specific settings. For instance, you can configure the minimum height and width of all boxes in the “Label Settings” of all box labels when building an Object Detection taxonomy.
General Taxonomy Recommendations
Try to lock down your taxonomy as early as possible. Updating your taxonomy within a project after you have already launched a production batch can be complicated since you will need to update your instructions, labeled examples, and quality tasks. To learn more, you can refer to this page.
Make sure to keep your taxonomy as easy to understand as possible. For instance, label names should be straightforward and make logical sense. A box drawn around a dog should have a label name of “dog” and not “puppy.”
Make sure to keep your taxonomy as simple as possible. It is harder to achieve quality if you have a complicated annotation use case that involves over 20 different classes of labels or a large tree selection with over 20 different options. Reducing the size and complexity of your taxonomy will also reduce labeler cognitive overload. If you are unable to reduce the size of your taxonomy, we highly recommend using our taxonomy chunking pipeline.