SGP’s annotation system is built around a queuing system for human annotators or contributors.
A queuing system for annotators is designed to manage and streamline the distribution of annotation tasks among a team of annotators. A queue-based system makes sense for annotator task management because it provides organization, fairness, and efficiency in handling tasks while ensuring that the right task is assigned to the right person at the right time. Here’s a breakdown of how the system works:
Assignment: Each annotator has their own queue based on tasks that are assigned to them. If no tasks are assigned to an annotator, they will automatically be assigned the next task at the front of the centralized queue when they start another task.
Skipping Tasks: Each time an annotator skips a task, the task is returned to the centralized queue and placed at the back of the Queue.
Annotators are not allowed to randomly pick tasks from the queue, as this disrupts prioritization and fairness.
Cherry-picking easy tasks over complex ones can lead to inefficiency and inequality. In most systems are not able to see the tasks before they claim it. In SGP, annotators can view a task before claiming.
Bypassing Priority Rules
Tasks with lower priority can not be processed before high-priority tasks unless explicitly overridden by system logic.
Manual Task Deletion
Tasks can not be arbitrarily deleted from the queue to prevent data loss or missed deliverables.
Deletions can only occur through an admin-verified process.
Batch Assignments
Annotators should not be allowed to pull multiple tasks at once unless the queue system supports batch assignments (e.g., microtasks).
Infinite Locking
Tasks should not remain “locked” to an annotator indefinitely. If an annotator doesn’t complete or reject a task in a reasonable timeframe, the task should return to the queue for reassignment.