Before you start creating a project, consider dividing it into several smaller projects. This is called decomposition.
Project 1. Does the photo contain a particular item? — This is data preparation (filtering).
Project 2. Find a similar item in the online store — This is the original task.
Project 4. Which of the found items is most similar to the original? — Choosing the best task response.
We recommend that you think through the architecture of a solution consisting of several projects in advance, since projects can be linked:
The result from one project can be the input for another project.
You can assign a skill to Tolokers in one project and filter Tolokers by this skill in another project.
After you decompose your project:
Tasks become easier and faster to perform.
Tasks require fewer skills.
Task instructions will be shorter, clearer, and more Toloker-friendly.
You can make tasks cheaper for the reasons above.
The quality of results is higher and easier to control.
It may be easier to design a few simple tasks than a single large task. You'll have less difficulty creating the interface and writing instructions.
It is easier to set up shortcuts in the task interface, which also speeds up the work of Tolokers.
Usually, you can make a separate project with tasks to prepare data and check Tolokers' responses. Sometimes you can also divide the main part of a task into several projects.
Before creating a project, answer the questions:
Do I have data to be used as the basis for completing my task?
You can entrust the collection of data for analysis to Tolokers as part of a separate project.
Do I need to filter my data?
Let's say you want to create a task titled “Select road signs in an image”, but you aren't sure that all images contain road signs. Create a separate project with a task titled “Are there road signs in an image?” to filter out unnecessary images.
A data filtering task is usually cheap and can help you save on the most important task and simplify the task instructions and interface.
You can set up a separate project where other Tolokers check responses in submitted assignments. For example, if you want to create a project titled “Find similar products”, enable manual review in this project and create a separate project with the “Are these items similar?” task to review responses, reject incorrect responses, and avoid paying for them.
If the responses cannot be combined automatically, you can set up a separate project where you ask Tolokers to choose the most appropriate response. An example is if the responses are images of similar items and you only need one image like that.
Assign a skill to Tolokers who completed tasks in the main project. For checking responses, you can assign the review task only to Tolokers who don't have this skill.
The easier the task, the better the results. If your task contains more than one question, it may be worth dividing it into several projects. Here are some examples of when decomposition is necessary:
If some questions in the task need additional filtering.
If different Toloker skills are required to answer different questions of the task.
If a Toloker must provide a general answer based on multiple criteria.
Some tasks consist of several questions, but they don't need any decomposition. For example:
Surveys: It's important that all questions are answered by the same Toloker.
Field tasks: If you need to verify various data about the same organization, it doesn't make sense to ask one Toloker to check whether the organization is open and another one to take a look at its business hours on the door.
Examples where decomposition is used:
Last updated: May 10, 2023