How task assignment works
A task is either a single image, series, or entire study that moves through the annotation workflow in a single unit. The intention is for a labeler to view and annotate a single task together; therefore, if you'd like your annotators to view & annotate an entire MRI study comprised of 4 series together, you should upload the entire study as a single task.
Task assignment helps manage the delegation of work amongst your entire team. RedBrick AI has automatic task assignment protocols, but you can override these with manual/programmatic task assignment as well.
All projects use automatic task assignment by default. The automatic task assignment protocol is a first-come-first-serve system that assigns the oldest data to the annotators that request new tasks first.
Annotators request for new tasks by keeping the labeling tool open or clicking on Label/Review on the project dashboard. If a user becomes inactive for extended periods of time, their automatically assigned tasks will be assigned to other users who are active.
You can override the automatic assignment protocol by manually assigning tasks to users from the Data page.
You can use
preAssignthe field in the items file to define which user will be assigned the task at each stage. For example, the snippet below will assign
[email protected]in the
Labelstage. Once the annotation is complete, and the task is queued in
[email protected]will be assigned as the Reviewer.
Once a task is assigned to a user, it is added to their Labeling Queue. You can view your labeling queue in two ways.
While in your Queue, the task can be in a few different states, depending on the status of the annotation:
- 1.Assigned Tasks that you have not worked on yet will be displayed as Assigned.
- 2.Saved Once you save your in-progress annotation (either manually or through auto-save), the task will show as saved.
- 3.Pending Finalization Once you are done with the annotation, you can Submit the draft. All drafts that have been submitted will still be in your labeling queue pending finalization. You must finalize the draft to complete it and send it to the next stage of the workflow.
- 4.Skipped Skipped tasks are intended to come back to in the future. If you encounter a task you don't want to complete, you can skip it, and it will be sent to the end of your labeling queue.
The diagram below is a guide to completing tasks in your labeling queue, including the actions and states of tasks.
Guide to submitting tasks in your labeling queue