Requester Tracking of HITs Submitted by Turkers

[ChristopherASA]

Any insight with regard to how requesters track HITs submitted to them by Turkers would be appreciated.

Background. A nice HIT was posted by a certain requester that I've worked for before, but when I accepted the HIT, I was informed that I had already done that HIT. But according to my HIT DB -- which was up to date -- I had completed no such HIT with that title for that requester. (The title of the new HIT was different than those I've done before for that same requester.)

 

[jan]

Any insight with regard to how requesters track HITs submitted to them by Turkers would be appreciated.

Background. A nice HIT was posted by a certain requester that I've worked for before, but when I accepted the HIT, I was informed that I had already done that HIT. But according to my HIT DB -- which was up to date -- I had completed no such HIT with that title for that requester. (The title of the new HIT was different than those I've done before for that same requester.)

perhaps the HIT fell outside the widow that your HIT database tracks? Some HITS are reposted months down the line, and your database can't track that far.
The requester can track you a variety of ways, including your mturk ID and your IP address.

 

[TSolo315]

perhaps the HIT fell outside the widow that your HIT database tracks? Some HITS are reposted months down the line, and your database can't track that far.
The requester can track you a variety of ways, including your mturk ID and your IP address.

Hit Database (the script) can go back indefinitely. Mine has every HIT I have ever done.

But yeah, most of the time they just keep a record of all the worker IDs that completed the survey -- which is provided to them with the HIT results.

 

[jan]

Hit Database (the script) can go back indefinitely. Mine has every HIT I have ever done.

But yeah, most of the time they just keep a record of all the worker IDs that completed the survey -- which is provided to them with the HIT results.

This mistake is the result of my myopia (so, ty). I guess I've just had to start over so many times (two laptops that died) - I made the wrong assumption.