How to check the poll completion code in mTurk and issue a ban if they did not enter the correct code?
I am working on mTurk and qualtrics and forwarding the mTurk workerID to qualtrics, and at the end of the qualtrics poll, I show the job ID as the confirmation code. This is the code that was supposed to be pasted into the textbox in the mTurk HIT. My problem is that he is recording the worker ID in the HIT, how can I check that he is entering the code he saw in the Qualtrics survey and not just typing in some number? I am using javacript in HIT to send a worker to Qualtrics.
source to share
Several possibilities, with (2) probably the best:
- You can generate completion code using Javascript in HIT and pass that code to Qualtrics as a URL query string parameter. Then, Qualtrics retrieve the completion code and show it to the worker at the end of the survey. When they enter code, you might have a Javascript function that checks to see if the entered code matches the Qualtrics source code and generates a hidden form field that calls something like
correct
and enters a yes or no value. Then you can approve everyone who matches. - You can do everything as in (1), with the exception of the assignment level ReviewPolicy configuration , which automatically rejects assignments where
correct
"none" is equal. - You can give everyone in the survey the same code (just displayed in Qualtrics) and then use the Assignment level ReviewPolicy function to reject it based directly on the code value. (You cannot set up a "dynamic" review policy with a different correct answer for each assignment, so this is probably the least desirable option.)
Using any of these methods, you can simply warn the employee that they entered the wrong code. You cannot prevent submission with the HIT created in the Requester UI. If you have configured ExternalQuestion (hosted on your own server) or HTMLQuestion generated using the API, then you can prevent submission by only showing a submit button when the code is correct. Note, however, that this is likely to annoy some workers.
source to share
I would highly recommend using # 2. Deviations will give you bad reviews from Turkopticon and potentially drown your research.
I also strongly recommend against # 3 as members of certain tuner groups will share the code and not do the poll.
The first option is by far the best choice and there are tons of javascript snippets to validate form fields to get the job done. Along with this, warning the employee when bad code has been sent is also a good idea, as it gives them the opportunity to either get it again from the survey or to re-conduct the survey. I like Thomas' idea of only showing the submit button when the code is correct. As long as it is working correctly (it is editing the correct code correctly), then it should not annoy any workers who do not cheat.
source to share
For step-by-step instructions for generating individual confirmation codes, I followed Tyler Burleigh's post. This is Thomas Option 1.
https://tylerburleigh.com/mturk/survey-completion-codes-in-qualtrics/
source to share