toloka.client.collectors.SkippedInRowAssignments | Source code
SkippedInRowAssignments(self, *, uuid: Optional[UUID] = None)Counts task suites skipped in a row by a Toloker.
Skipping tasks is considered an indirect indicator of quality of responses. You can block access to a pool or project if a Toloker skips multiple task suites in a row.
The collector can be used with conditions:
- SkippedInRowCount — How many tasks in a row a Toloker skipped.
The collector can be used with actions:
- RestrictionV2 blocks access to projects or pools.
- ApproveAllAssignments accepts all Toloker's assignments.
- RejectAllAssignments rejects all Toloker's assignments.
- SetSkill sets Toloker's skill value.
| Parameters | Type | Description |
|---|---|---|
uuid |
Optional[UUID] | The ID of a collector. Note that when you clone a pool, both pools start using the same collector, because it is not cloned. Usually, it is not an intended behavior. For example, in this case one collector gathers history size from both pools. |
Examples:
The example shows how to block Toloker's access to the project for 15 days if he skipped more than 3 task suites in a row.
new_pool = toloka.client.pool.Pool()
new_pool.quality_control.add_action(
collector=toloka.client.collectors.SkippedInRowAssignments(),
conditions=[toloka.client.conditions.SkippedInRowCount > 3],
action=toloka.client.actions.RestrictionV2(
scope=toloka.client.user_restriction.UserRestriction.PROJECT,
duration=15,
duration_unit='DAYS',
private_comment='Skips too many task suites in a row',
)
)