Voice recording
In this tutorial, you will learn how to run voice recording in Toloka. We will use a project preset designed specifically for this type of data labeling.
Voice recording is a type of data labeling task with the text block to read and the voice recorder button. Using the Toloka mobile app, Tolokers should tap the button and read the text aloud. After getting the results, you can listen to the recordings and download them.
Note
You may need additional projects for your task, such as dataset pre-check or checking Tolokers' responses. Learn more about this in Decomposition of the task.
Prerequisites
Before you begin:
-
Make sure you are registered in Toloka as a requester.
-
Top up your Toloka account. If you are unsure about the budget, you can do that later in this tutorial. Toloka will display the budget estimate for your project.
Choose a preset
We recommend starting with a project preset for easier configuration and better results.
-
Follow this link, or create a project manually:
-
Click Choose this preset in the pop-up tab.
Create a project
Set up how your tasks will look for Tolokers. Tolokers are people around the world who get paid for completing your tasks.
-
Under General information, add the project name and description.
-
Name to show Tolokers: In 2–5 words, state the general idea of the project.
-
Description for Tolokers: In a couple of sentences, explain what you expect Tolokers to do. This is just an overview. You will write instructions later.
-
-
In the Task interface section, set up what your tasks will look like. This preset has a task template with layout and validation pre-configured.
Note
This tutorial uses Template Builder, but you can use the HTML/JS/CSS editor for the same purpose.
-
In the Config section, you can edit the code to change the appearance and layout of the task elements. For a trial pool, keep the code as is.
To learn about the properties of the Config section, their possible values and the impact on the task interface, see the Template Builder Help.
-
In the Input data example section, you can change the sample text. This text is only used to display the task interface preview on the right.
-
Raw task data is stored in the XSLX, TSV, or JSON format. The labeling results are presented in a TSV file. The Data specification section determines which parameters these files might contain.
Click Show specifications and check the values:
-
Input data: Parameters in the file with raw task data.
-
Output data: Parameters in the file with labeling results.
Input data and Output data match the task interface you set up in Template Builder. Check that there are fields for all data types you use for your tasks, and for the ones you want to see in the results file.
-
-
-
Under Instructions for Tolokers, add the instructions Tolokers will see when they start doing your tasks. You can add text, tables, and images to your instructions.
Check the sample text of the instructions, and update it to fit your project.
Tip
When writing instructions, remember that most Tolokers don’t know anything about your tasks beforehand. Make sure your instructions are as clear as possible, but not too wordy. For successful data labeling, try to strike a balance between covering all the essentials and keeping it short. Learn more in our knowledge base.
-
To save your data and continue, click Create a project.
Create a pool
A pool is a set of tasks sent out to Tolokers at the same time. One project can have many pools. When creating a pool, you set up pricing, audience filters for Tolokers, and quality control.
-
Click Add a pool on the project page.
-
Set the Pool name (visible only to you) field. Only you will see this pool name on the project page.
-
Specify the pool description which will be displayed instead of the project description in the task list for Tolokers. By default, Tolokers see the description from the project settings. To use a different description, uncheck the Use project description box and set Public description. If necessary, click + Private comment to add a private project description that only you will see.
-
Click Create.
-
At the Select the audience for your task step, set up filters to select Tolokers for your pool.
-
Clear My tasks may contain shocking or pornographic content if your project has none of those.
-
To select Tolokers based on their language, location, age, gender, and other parameters, click the Add filter button.
-
Use the Speed/quality balance slider to change the number of Tolokers who can see your tasks. Move the slider to the right to exclude Tolokers with lower ratings from participating in your project.
-
-
At the Setup quality control step, set quality control rules for more accurate results:
-
Click the Review task responses manually toggle, and specify the number of days for checking the task in the Review period in days field (for example, 21).
What is manual review?The Review task responses manually option allows you to review completed assignments before accepting them and paying for them. If the Toloker didn't follow the instructions, you can reject the assignment.
-
The Voice recording preset has the pre-configured quality control rules:
-
In most cases, you can keep the Fast responses rule as is. It filters out Tolokers who complete tasks too fast. The default settings mean that Tolokers are banned from the project for 1 day if they complete tasks in 4 out of 5 task suites in less than 15 seconds.
-
Delete the pre-configured Majority vote rule.
-
-
For a trial pool, the settings you’ve just made are enough. You can get better results if you set the additional quality control rules.
The additional quality control rules-
Add the Results of assignment review quality control rule and enter the following values:
This means that if 35% or more of a Toloker's responses are rejected, the Toloker is banned and can't access your tasks for 15 days. The rule takes effect after 3 responses of the Toloker are reviewed.
-
Add the Processing rejected and accepted assignments rule:
This means that if you reject assignments during the review, they'll be sent for re-completion to another Toloker.
-
-
-
At the Set the task price and overlap step, set up how much a single task will cost for you.
-
In Price per task suite, set the amount of money to pay per task suite done by one Toloker.
A task suite is a page with a number of tasks. It can contain one or several tasks. If the tasks are simple, you can add 8–10 tasks per suite.
-
In the Overlap field, define how many Tolokers must do each task.
The value depends on how many recordings of the same phrase you want to collect. If one is enough, set
1
. -
At the bottom of the Price section, you see Price per 1 task. This is the amount of money paid per task.
-
-
At the Add optional pool settings step, specify the Time per task suite, sec.
This time should be enough to read the instructions and load the task (for example, 1,200 seconds).
-
At the Prepare and upload data step, upload your task data.
-
Create the tasks for Tolokers:
-
To download a template, click one of the buttons:
- Template in XLSX
- Template in TSV
- Template in JSON
For this type of project, the file with tasks must have one parameter. Its name equals
INPUT:text
, and the values are texts.INPUT:text Does white chocolate have cocoa? How many rings are there in the Olympic Games symbol? What is the capital of Australia?
-
Open the downloaded file, and replace the sample values with your texts.
-
Click Drop file here or select, and upload the file you’ve just made.
-
Click Continue.
-
-
Tasks are shown to Tolokers in suites. A suite is a single page with multiple tasks. Define how many tasks to include per suite:
-
General tasks: These are tasks for Tolokers to label.
-
Control tasks: These are tasks with predefined answers used to control the quality of responses. For this project, you don’t need control tasks.
-
Training tasks: These are tasks with predefined answers and explanations for Tolokers. Normally you use training tasks in separate training pools. You don’t have to include them.
For example, you can add 5 general tasks per suite:
-
-
Click Combine tasks into suites.
-
-
At the Double-check your project and try out tasks step, check how the task will look from the Toloker's point of view.
Note
This step will be enabled after you complete the previous steps. You can skip this step by clicking Do it later.
After all the steps, you'll see the Set up is finished and your pool is ready for labeling tip on the pool page.
Start labeling
-
Make sure you have topped up your account.
-
To send the tasks to Tolokers and begin the labeling process, click Start labeling.
-
In the pop-up panel, review the budget and click Launch.
See the results
Track the labeling progress on the pool page. You can start the review when the first results are received.
After the time period specified in step 4.1 of creating the pool, all responses are automatically accepted, regardless of their quality.
-
Go to the pool, and click Review assignments.
-
Choose an assignment.
-
Check the responses, and click Accept or Decline. For rejected responses, enter a comment to specify the reason.
Note
To learn about other ways of review, see the Reviewing Tolokers' responses section.
-
After checking all the assignments, click Download results.
You will get the TSV file with the labeling results.
-
To download the recordings, click the arrow next to the Download results button. Choose Download attachments from the drop-down menu.
Troubleshooting
If you pass texts to the input data, you can upload 2 different tasks to the pool: pass Text 1 in the INPUT: <input field name>
field of Task 1. In Task 2, use this field to pass Text 2.
If the text is specified in the task interface, then clone the project. To limit a Toloker to doing only one task in your project, use the Submitted responses rule. You can assign a skill or ban the Toloker after they submit one response.
The popup
property of the component view.image specifies whether opening a full-size image with a click is allowed. By default, it is true
(allowed).