We understand everyone has their own way of describing the labeling workflow.
We want to introduce you to the terminology we've developed.
Scale is an API-first platform, meaning every workflow and concept can be accessed with an API endpoint.
A task represents an individual unit of work to be done. There's a 1:1 mapping between a task and the data to be labeled. For example, there'd be 1 task for each image, video, or lidar sequence needing to be labeled.
Using our API, you would specify how the labeling should be done for a given task.
Tasks can only be created via our API. To learn more, please visit our API docs.
Projects allow you to organize similar tasks based on instructions and task types. All projects will share the same instructions and annotation rules.
A project is tied to one specific task type. You can have multiple projects per task type.
As an example, you could have one project for categorizing scenes, and another for annotating images.
We highly recommend every task submitted to be tied to an explicit project to keep things organized. In addition, we have provided more documentation about projects in our API Docs.
For high-volume projects, batches can optionally be used to further divide work inside a project. Batches can tie to specific datasets you use internally, or can be used to note which tasks were part of a weekly submission for example.
Note: You can only create batches via our API. To learn more about using this feature, please see our API docs.
Updated about a month ago
Now that you got the basics, learn about the Task Creation, Labeling, and Completion process.
|Scale 101: Workflow|