Amazon Mechanical Turk Integration: Difference between revisions

From Google Summer of Code 2009
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 3: Line 3:
We would like to automate the process of submitting the HITs file to Mechanical Turk. Skills required for this task involve using Ruby on Rails and the Mechanical Turk API.
We would like to automate the process of submitting the HITs file to Mechanical Turk. Skills required for this task involve using Ruby on Rails and the Mechanical Turk API.


Here is the API documentation: [http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1852&categoryID=28]
Here is the API documentation: [http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1852&categoryID=28 http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1852&categoryID=28]

Latest revision as of 08:12, 27 March 2009

As an extension to the Scriptgen tool, we have begun to integrate Amazon's Mechanical Turk as an alternate means of gathering data. We create HITs (Human Intelligence Tasks) on Mechanical Turk which would lead the Turkers to the Scriptgen tool where they would complete the task and receive a confirmation code. The confirmation code is then entered into the HIT page on Amazon to complete the task. Currently, the HITs are generated from the scripting tool's database into a CSV (comma separated values) file. This file is then manually uploaded to Mechanical Turk to publish the HITs.

We would like to automate the process of submitting the HITs file to Mechanical Turk. Skills required for this task involve using Ruby on Rails and the Mechanical Turk API.

Here is the API documentation: http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1852&categoryID=28