diff --git a/argilla/docs/assets/images/how_to_guides/distribution/taskdistribution.svg b/argilla/docs/assets/images/how_to_guides/distribution/taskdistribution.svg new file mode 100644 index 0000000000..a40d451c61 --- /dev/null +++ b/argilla/docs/assets/images/how_to_guides/distribution/taskdistribution.svg @@ -0,0 +1,33 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/argilla/docs/how_to_guides/distribution.md b/argilla/docs/how_to_guides/distribution.md index 4037fcd208..e0685b0b93 100644 --- a/argilla/docs/how_to_guides/distribution.md +++ b/argilla/docs/how_to_guides/distribution.md @@ -10,6 +10,8 @@ Users can define the minimum number of submitted responses expected for each rec When a record has met the minimum number of submissions, the status of the record will change to `completed` and the record will be removed from the `Pending` queue of all team members, so they can focus on providing responses where they are most needed. The dataset’s annotation task will be fully completed once all records have the `completed` status. +![Task Distribution diagram](../assets/images/how_to_guides/distribution/taskdistribution.svg) + !!! note The status of a record can be either `completed`, when it has the required number of responses with `submitted` status, or `left`, when it doesn’t meet this requirement. Each record can have multiple responses and each of those can have the status `submitted`, `discarded` or `draft`.