Kili Technology manage a queue for each project, which can be customized and redefined all along a project. This is helpful for advanced annotation processes: business expectations, priorities, active learning, production supervision, real time annotation.
3 strategies are possible:
- First In First Out
- Assign assets to identified labelers
- Assets prioritization
First In First Out (FiFo)
This is the default queue orchestration. Assets are loaded with a time stamp (creation date). First assets will be distributed to be annotated first.
Assign assets to identified labelers
The queue can be customised in order to assign a specific list of assets to specific labelers. Assignation can be done for the whole queue or a specific subset of the complete dataset
toBeLabeledBy. See here on Kili Playground.
To unset the attribution,
update_properties_in_asset with an empty list.
The 3rd approach allows to set a specific priority at asset level. You can either set a priority to each asset or set a priority to a limited number of assets within the dataset. The higher the number the higher the priority is. If 2 assets have the same priority, Fifo will apply.
In other terms:
- If asset 1 as priority N_1 and asset 2 as priority N_2, and N_1 > N_2, then asset 1 has a higher priority than asset 2.
- If N_1 = N_2, priority follow the default strategy (FiFo)