Skip to content

kimberli/mturk-template

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

25 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Generalized MTurk Task Template

A general-purpose template for Amazon Mechanical Turk tasks.

Development

Run make watch to watch SCSS files and compile to CSS. Run something like python -m SimpleHTTPServer to see the page locally.

Customization

This framework can be used to create MTurk HITs, broken up into discrete repeated subtasks.

To define your own MTurk HIT, you only need to change things in three places:

config.json

Here, you can define your HIT's name, description, number of subtasks, instructions, etc.

Fields:

  • meta.title - the title of your task, displayed in the page title (string)
  • meta.description - a short overview of your task's purpose, displayed as bolded text right below the page title (string)
  • meta.numSubtasks - the number of subtasks your task will have (int)
  • meta.disclaimer - the experiment disclaimer text displayed at the bottom of the page (string)
  • meta.aggregate - whether inputs and outputs for the task should be divided up by subtasks, or the same inputs and outputs should be stored across all subtasks. If false, outputs will be stored in an array of length numSubtasks; otherwise, they will be merged a single object. In general, setting this to false will be better if subtasks are repetitive and self-contained (for example, labeling a series of images), and this to true will be better if the behavior of one subtask depends on input/output from another subtask (for instance, labeling an image in one subtask and writing a description of it in the next).
  • instructions.simple - short instruction paragraph displayed below the task description. You can include HTML tags here! (string)
  • instructions.steps - an array of instruction strings, displayed as a bulleted list on the page. You can include HTML tags here! (array of strings)
  • instructions.images - an array of URLs for demo gifs on the instruction page. One of these will be displayed randomly on each page load. (array of strings)
  • hitCreation.title - the HIT's title on the MTurk worker page (string)
  • hitCreation.description - the HIT's description on the MTurk worker page (string)
  • hitCreation.numTasks - how many duplicates of the HIT you want to create (int)
  • hitCreation.numAssignments - how many assignments each duplicated HIT has (int)
  • hitCreation.rewardAmount - amount to pay per HIT (string)
  • hitCreation.keywords - comma-separated tags (string)
  • hitCreation.duration - how long you want to give each worker to complete the task once started in seconds (int)
  • hitCreation.lifetime - how long you want the HIT on the worker site in seconds (int)
  • hitCreation.taskUrl - the URL where your MTurk task lives (string)
  • hitCreation.production - whether you want to use MTurk's production or sandbox environment (bool)

index.html

Find the section marked <!-- vv CUSTOM EXPERIMENT MARKUP GOES HERE vv -->, and add your custom HTML elements in that section (e.g. image divs, input boxes). Add ids to those HTML elements so you can easily refer to them with JQuery in the page's JavaScript (see assets/js/custom.js).

assets/js/custom.js

Fill out the 4 functions: loadTasks, showTask, collectData, and validateTask. These define behavior for loading initial data, displaying a task, storing data from a task, and validating a task. We recommmend starting by copying one of our template files: assets/js/aggregate-template.js if you have set config.meta.aggregate=true or assets/js/no-aggregate-template.js if you have set config.meta.aggregate=false.

Setting up the MTurk task

Edit the hitCreation fields in config.json. Use script/create_hit.py to create a HIT. Make sure to edit the config for submitting to live or sandbox.

Screenshots

Here's a demo of the task interface: demo

About

Quick framework for generating Mechanical Turk tasks

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages