Collect data on businesses
Run the project in the Sandbox first. This helps you avoid making mistakes and spending money on a task that isn't working right.
You may need additional projects for your task, such as dataset pre-check or checking performers' responses. Learn more about this in Designing the solution architecture.
Let's say you need to check whether the equipment is installed in an organization.
To do this, create the following task: the performer needs to come to the point, take a picture of the outside of the organization, and photograph the equipment inside from different angles. If there is no equipment installed, photos are needed as proof. If there is no organization at the address, the performer needs to take a photo of the building where it should be located.
To run tasks and get responses:
Create a project
The project defines what the task will look like for a performer.
Click + Create a project and choose the Monitoring objects in organizations template in the field task block.
Enter a clear name and a short description for the project. Performers will see this in the task list.
Write a brief instruction or edit an existing one (see the recommendations). Use HTML tags to insert links, pictures, and so on. Field task instructions should be easy to read even on a mobile phone screen.
In the template, the Map option is enabled automatically. So a user will see tasks as points on the map and be able to choose any.
Address and Coordinates will be displayed when the performer chooses a point on the map. These fields contain an input field It will be changed later.
- To show the name and description of the point in the task, edit the fields:
- Note. This tutorial shows how to create a task interface in the HTML/JS/CSS editor. You can also try creating a task interface in the Template Builder.Define which objects you are going to pass to the performers and receive from them in response. To do this, add input and output fields in the Data specification section.
Input data is types of objects that are passed to the performer for completing the task. For example, this could be a text, an image, or geographic coordinates.
Output data is types of objects that you receive after the task is completed. For example, this could be one of several response options, typed text, or an uploaded file.
Learn more about input and output data fields.The template includes the fields:
- Input data field:
name— A string with the name of the organization.
image— A string with the link to the product photo.
address— The task address.
product— A string with the object description.
coordinates— Coordinates of the point where the performer should come.
- Output data fields:
address— The task address.
coordinates— The task coordinates.
verdict— The task status.
imgs_facade— Array of files: photos of the store uploaded by the performer.
imgs_obj— Array of files, photos of the object uploaded by the performer.
imgs_around_org— Array of files: photos of the area around the building uploaded by the performer.
imgs_around_obj— Array of files: photos of the object surroundings uploaded by the performer.
imgs_plate_or_address— Array of files: photos of the address plate uploaded by the performer.
comment— Text field: performer's comment.
worker_coordinates— The performer coordinates at the moment of task completion, with the Current location option turned on.
- The task interface describes how the task elements should be arranged, what they should look like, and what logic they should follow.
You can use standard HTML tags and special expressions in double curly brackets in input and output data fields in the HTML block. HTML describes how the elements should be arranged in the task.
JS is used to describe the task logic. Also, the main content of the task is embedded in JS for ease of editing.
The template logic specifies a minimum number of photos of the organization's front, object, surroundings, address plate, and, if there is no object, of the area around the building. If you want to change these values, find all strings and change the minimum number of photos for each task completion option:
if (solution.output_values.imgs_facade.length < 2) if (solution.output_values.imgs_obj.length < 2) if (solution.output_values.imgs_around_obj.length < 4) if (solution.output_values.imgs_around_org.length < 4)
In this project, the
textsvariable stores the texts for the information block and three task completion options:I found the object; I found the organization, but there is no object; Organization closed or missing.
MAX_DISTANCEvariable specifies the maximum distance from the designated point (in kilometers by default) that the performer must stay within during task completion. You can specify a value that suits you.
- The template already contains CSS styles, you don't need to change them.
- Click the Preview button to see the performer's view of the task.
- Save the project.
Add a task pool
A pool is a set of paid tasks sent out for completion at the same time.
- Open the project and click Add pool.
- Give the pool any convenient name and description. The pool info is only available to you. Performers can view only the project name and description.
- Set the price per task, for example $0.2. For field surveys, always add one task per page.
A page can contain one or several tasks. If the tasks are simple, you can add 10-20 tasks per page. Don't make pages too long because it slows down loading speed for performers.
Performers get paid for completing the whole page.
The number of tasks on the page is set when uploading tasks.
The general rule of pricing is the more time the performer spends to complete the task, the higher the price is.
You can register in Toloka as a performer and find out how much other requesters pay for tasks, or see examples of cost for different types of tasks.
- Set the Time allowed for completing a task suite. It should be enough to get to the place, find the specified point and upload photos. For field surveys, we recommend allocating a day — 86,400 seconds.
- Set Overlap, which is the number of performers to complete the same task. For field surveys, it is usually 1.
- Turn on the Non-automatic acceptance option and enter the number of days for checking the task in the Deadline field (for example, 7).
- Add Filters to select performers. To make your tasks available in the Toloka mobile app to English-speaking performers located in Moscow, set the language and region.
- Save the pool.
- Click Upload. In the window that opens, you can also download a sample TSV file by clicking Sample file for uploading tasks.A TSV file presents a table as a text file in which columns are separated by tabs.
You can work with it both in a table editor and a text editor, and then save it to the desired format. More about working with a TSV file. There is a CSV format that is similar to TSV, but you should use a TSV file for uploading.
- Add input data in it. The header of the input data column contains the word
INPUT. For field surveys, you also need to specify the latitude
AI:longitudeof the point. You can use a service like Yandex.Maps to get the coordinates.
- Upload the tasks by choosing Set manually and set 1 task per page.
Start the pool and get the results
- Start the pool by clicking .
- Track the completion of tasks in the Pool statistics section.
- When the first results come in, you can start reviewing.
To review assignments, go to the pool and click Download results. To download attachments, click the button next to and choose Download attachments.Note. After the specified time period, all responses are automatically accepted, regardless of their quality.