|
You are browsing the documentation for a deprecated version ('2014-08-15') of the Amazon Mechanical Turk Requester API. This version of the API will be deprecated and will be rendered unusable as of June 1st, 2019. If you request against a legacy API version (https://docs.aws.amazon.com/AWSMechTurk/latest/AWSMturkAPI-legacy/Welcome.html) on or after June 1, 2019, you will receive the following response:
The latest version of our API ('2017-01-17') provides you with additional tool choices and enables you to select from nine AWS Software Development Kits This version also updates naming conventions used in the API and adopts the AWS standard of Signature Version 4 to authenticate requests securely. The API uses REST requests and no longer requires that developers be familiar with SOAP protocol. These changes make the MTurk API consistent with AWS APIs, simplifying the on-boarding process for both new and existing AWS developers. The legacy MTurk Command Line Tools and .NET, Java, Ruby, and Perl SDKs were marked as deprecated in January 2018. We will be deprecating the legacy APIs as of June 1, 2019. If you are on a legacy API, you must migrate to the latest
version of our API. You can find documentation for the latest API here and the AWS SDKs here For support, contact requestor-apilegacydeprecation-support@amazon.com |
How Review Policies Work
You specify the Review Policy(s) that you want Mechanical Turk to apply when you call the CreateHIT operation. You must specify Review Policies when you create a HIT. You cannot apply a Review Policy to an existing HIT.
As assignments are submitted, Mechanical Turk applies the Review Policy(s) that you specify. You call the GetReviewResultsForHIT operation to gather the results from the application of the Review Policy.
There are two types of Review Policies, Assignment-level Review Policies that are applied as soon as a Worker submits an assignment and HIT-level Review Policies that are applied when a HIT becomes reviewable. For more information, see Assignment Review Policies and HIT Review Policies.
You can specify one Assignment-level Review Policy and one HIT-level Review Policy when you
call CreateHIT using the HIT Review Policy data structure.
The Assignment-level Review Policy ScoreMyKnownAnswer/2011-09-01 and the HIT-level
Review Policy SimplePlurality/2011-09-01 can be used in the same call to
CreateHIT.
Once an Assignment-level Review Policy is applied, the Assignment's status is changed to Submitted and optionally an event notification can be sent. Assignments with Submitted status are returned by the GetAssignmentsForHIT operation and the results of applying the Review Policy are available by using the GetReviewResultsForHIT operation.
You can use different Review Policies on distinct HITs in a HIT type. For example, you may wish to apply the ScoreMyKnownAnswers/2011-09-01 policy to a small number of HITs that have known answers in them, but apply the SimplePlurality/2011-09-01 policy to all HITs in a group. Workers do not have access on the Worker User Interface to information about whether a Review Policy has been applied to a HIT.
To help you understand Worker performance on your Review Policy you can call the GetRequesterWorkerStatistic operation to get the percentage of known answers that were answered correctly or the Worker agreement level for your HITs.