Setting up a pool
- Has a skill value lower than the one specified in the Level required field.
- Didn't complete any tasks linked to training during this period.
- Upload the task file using Smart mixing.
studentas the correct answer to the question. Don't take other questions into account (leave the fields empty or unselected).
- Add the Control tasks rule to the pool:
if the percentage of correct control answers = 100, then set the skill value Student = 1.
Yes, you can do that. In the filters, select . Please note that the profile data is entered by the user when they register in Toloka. We recommended that you use the filters Region by phone number and Region by IP.
Yes, of course — you can use the same skill for different projects. But most often, a skill is intended for a specific project. If the performer completes a certain task well, this doesn't mean that they will complete other ones successfully. Another disadvantage is that if you filter by skills that were set long ago, you will artificially limit the number of available performers.
If you mean multiple different projects, you can't do that.
You can merge all the projects into one and use History size in the quality control rules. See examples in the Control tasks post.
You can use Aggregation by skill, but you'll need to list all the possible values, which is probably not the best choice. Perhaps you'll find another method of aggregation helpful.
Perhaps the output fields you want to aggregate don't have valid values in your project. For now, you have to specify the possible values for every type of output fields.
In the main Toloka version, you can only assign a skill to users who have completed at least one of your tasks. There is no option to assign a skill to an arbitrary user. To limit the audience of users who will see your project, use filters. For example, specify the city, date of birth, gender, or some other parameters of your target performers.
Tasks from an open pool are available to every user that matches your pool filters. You can restrict access, like by using a skill.
Your users will need to be trained again.
To make your task available in the mobile app, set up the filter:
client = mobile Toloka in your pool.
If the user mismatches your preset filter or rating level, they can't see the task. You can only remove the restricting filter from the pool. You can test the task in the Sandbox by adding the desired user to your trusted list.
You can do that. To select performers for the pool, use filters.
Client = web version or = mobile Toloka
You can assign a skill to these people based on their performance in the previous pools. Use this skill as a filter in the new pool.
Specify this skill as a filter, but leave the value field empty (this is equivalent to absence of the skill).
If the user already has a given skill, you can't add the same skill to them from the task review interface. You can open the user's profile and edit the skill value.
If it's a public or training skill, they see it and they get a message about it.
There is no such option. If the skill is public, the performer sees it in their profile.
Requesters can't see the full details about specific performers. So you can't see information like the date of birth, gender, last name, or first name. However, you can use filters by date of birth and gender (in the pool settings). This way you can select a group of performers without accessing the personal information of individual performers. This decreases the risk of user de-anonymization.
Always use one or more ways to control quality of answers.
Counting fast responses makes sense for most tasks.
If the user has to provide a response as a text or link or upload a photo, the best way to control quality is by reviewing assignments. You can outsource task acceptance to performers. Create a task with a question (for example, “Is this phrase translated correctly?”) and possible responses (for example, “yes”/“no”). Set up overlap and majority vote check.
Calculate the skill for each pool separately. The current skill value is the value of the skill in the pool the user completed last. This option is convenient if:
The pools are intended for different groups of performers (for example, there are filters by city or country).
Pools are started one by one and you don't want to take into account the responses in the previous pools to calculate the skill in the current pool.
This calculation method is used by default when adding a quality control rule to a pool. For the control tasks block, leave the Recent values to use field empty.
Calculate skill based on all tasks in a project This option is good if the pools are small and you don't need to have skill calculated for each pool.
This option is available only for skills on control tasks. To use it, fill in the Recent values to use field in quality control rules in pools.
- Don't show captchas.
- Show a captcha after every 20 task suites.
- Show a captcha after every 10 task suites.
- Don't show captchas.
- Show a captcha after every 20 task suites.
- Show a captcha after every 10 task suites.
You've stopped the main pool. This could limit the number of performers with access to the pool. Start the training pool again. There will be more performers who can access the tasks.
- The filters you set are too strict. For example, a strong restriction on a certain skill that most users don't have.
- Too many users are banned. Ease the quality control rules.
The settings for quality control rules depend on the type of tasks. General recommendations:
The Control tasks rule starts working after the performer completes the number of control tasks you specified. If your pool contains both training and control tasks, you can take into account the responses in both of them (the Number of responses parameter) or only in control tasks (the Number of control responses parameter).
As soon as the needed number of responses is collected, Toloka calculates the percentage of correct and incorrect responses and performs an action (assigns a skill, or blocks the user in the pool or in the project). Then this percentage is updated as the tasks are completed by the performer. The number of the performer's last responses used for the calculation is set in the Recent values to use field. If you leave it empty, all the responses from the performer in the pool are counted.
It is better to use one skill in a project. You can choose the way to calculate the skill:
Your training and control tasks have the same project specification. However, you can create a separate project with the tasks and assign a skill based on user responses. Then you can admit performers to the main project based on their skill.
An exam pool contains only control tasks. It's usually small and used for checking how well users learned to do your tasks after they read the instructions and completed the training. Unlike your main pool, you already know the correct responses for every task in this pool. You can set the price to zero.
Based on the results of responses to control tasks, you can assign a skill to the users and then specify it in the main pool as a filter. For example,
MySkill = 80 or = Is missing. You don't have to create an exam. For simple tasks, the training pool provides enough practice, but many requesters also use exams.
Yes, the fast response settings specify the time per task suite.
Yes. When you copy the filter and quality control settings, the settings you previously added manually are overwritten. You should see a warning about this in the copy settings window.
Indeed, this rule is probably too strict. Even the most careful user can make a mistake, so you probably want to relax the rule. Besides the requester-specific bans, we have system processes that ban users who regularly fail captcha checks in Toloka.
Yes, unfortunately, this can happen. This is why we recommend that you offer a training task or exam before the main task. In this case, only those people who showed good performance at the previous stage are selected for the main pool.
When you load tasks, use smart mixing. In this case, you'll have infinite overlap in your exam.
However, this poses the risk that you might spend a lot of money on the exam. You might want to open this pool only when the main pool opens, and close it when labeling of the main pool ends.
You can add a training pool to test your performers. Based on the test results, assign skills to the users for the tasks they do best.
Then open your pools only to the users that have a certain skill: use filters for this.
This won't lower performer ratings. Even if you ban users from your project based on the testing results, this won't affect their rating.
You can upload your main and control tasks separately using different files.
If the user already got paid for the tasks, the money can't be refunded to you.
Yes, if they can access both pools, they can do both of them. To restrict access to subsequent tasks for a performer, use the Completed tasks rule and select a ban at the project level.
No. The responses of these performers aren't automatically excluded from the final results file.
But you can do it yourself if you want. When downloading the results, select the option Exclude assignments by banned users. You can also forward all the assignments from banned users to other performers using a rule.
Yes, you can do that. In this case, create the first pool based on the training pool and the exam pool based on your main pool. If a pool contains only control and/or training tasks, the price can be set to zero.
In the exam pool, you can create a skill reflecting the exam result and granting admission to the main pool. For example,
if the number of responses is ≥ 10, set the skill value in the <exam skill> as % of correct responses. In your exam pool user requirements, specify:
<exam skill> < 80 or = Is missing>. In the main pool, set up a filter:
<exam skill> >= 80 and (<main skill> >= 70 or = Is missing). You can choose the skill values depending on how well the performers handle your task.
Captcha is usually used in simple projects with automatic acceptance, like classification, categorization, or information search. These are cases where there are few response options and users don't need to upload files or write texts. It helps you filter out bots and sloppy performers.
All responses to the task are taken into account. If one response differs from the majority vote, the whole task is counted as mismatching the responses of other performers.
No, this is incorrect. With these settings, each time a rule condition is met, the performer gets
skill = 1. To change the skill value in the process of task review, you need a “multi-step” rule, which has multiple identical rules with different values of Total reviewed responses.
Technically, if you have only one task in your training pool, you don't have this option. The skill will be either
100. We recommend that you add several tasks, or at least 2 so that the performer will practice on the first task and will be able to do the second task correctly. In this case, you can admit users to your main pool starting from the skill value of
You can also create a training pool based on the main pool. Assign a skill using the Control tasks rule: in this case, you can admit users with any skill level to your main pool, even if the value is zero. But we don't advise giving tasks to people who failed training.
No. But you can create a pool of the Training type based on your main ppol and enable non-automatic acceptance there.
No, they can't.
If you pass texts to the input data, you can load 2 different tasks in the pool. In one task, pass Text 1 in the
INPUT: <input field name> field, and in the other task, use this field to pass Text 2. But if the text is in the HTML block of the task template, you need to clone the project. To let a performer do only one task in your project, use the Submitted responses rule. You can assign a skill or ban the performer after they submit one response.
No, the users are unaware of the ban.
The tasks themselves are not exported, only the project configuration and the settings of the selected pool. However, you can download your marked up tasks from the Sandbox pool and import them to the pool you created. To download the control tasks only (if you marked them up in the interface), go to Mark up, then click Control tasks and Download.
The Recent values to use field is for the number of recent responses from the performer. If you use non-automatic acceptance for your task, then to set up your intended rule you need to specify
3 in Total reviewed responses.
To perform actions with users (assign a skill or ban them) based on the majority vote, add a relevant rule to the pool.
Don't forget to enable Keep task order in the pool parameters. Majority vote is used in the projects with preset options (radio buttons or checkboxes). This rule won't apply to the text entry or file upload fields.
Another option to select performers for this type of projects is non-automatic acceptance.
This is the total number of responses to the control questions.
You can create a task pool for all your performers and create performer skills in it. In this case, you can open your tasks only to the performers with the necessary skills. This won't affect their rating.
Even if you ban a performer from the project, this won't affect their rating either.
Overlap defines how many performers complete the same pool task.
The best overlap is an overlap that provides satisfying quality of results. For most tasks that are not reviewed, overlap from “3” to “5” is enough. If the tasks are simple, overlap of “3” is likely to be enough. For tasks that are reviewed, set overlap to “1”.
Yes. Open edit mode for the pool and set a new overlap value. You don't need to restart the pool. Updating the settings is usually fast, but if there are many tasks, it may take several minutes.
Yes, this might happen. You must set an adequate pool closing interval.
In this case, if you don't have 3 identical responses for your task (response threshold), no user would be considered a good or poor performer, because the system can't see which of the users made an error.
But if you set
response threshold = 2 with
overlap = 3, then two users with the same responses are considered good performers, but the third user, who gives a different response, is a poor performer.
Yes, you can do that. Set up incremental relabeling.
You can use overlap to let multiple performers do the same task. The overlap value is set up in the pool settings.
The progress bar shows the number of task suites including the overlap. If the overlap is greater than one, the number of task suites is different from the total number of tasks.