DOCSLIB.ORG

Amazon Mechanical Turk Developer Guide API Version 2013-11-15 Amazon Mechanical Turk Developer Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Amazon Mechanical Turk Developer Guide API Version 2013-11-15 Amazon Mechanical Turk Developer Guide Amazon Mechanical Turk Developer Guide API Version 2013-11-15 Amazon Mechanical Turk Developer Guide Amazon Mechanical Turk: Developer Guide Copyright © 2014 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. The following are trademarks of Amazon Web Services, Inc.: Amazon, Amazon Web Services Design, AWS, Amazon CloudFront, Cloudfront, Amazon DevPay, DynamoDB, ElastiCache, Amazon EC2, Amazon Elastic Compute Cloud, Amazon Glacier, Kindle, Kindle Fire, AWS Marketplace Design, Mechanical Turk, Amazon Redshift, Amazon Route 53, Amazon S3, Amazon VPC. In addition, Amazon.com graphics, logos, page headers, button icons, scripts, and service names are trademarks, or trade dress of Amazon in the U.S. and/or other countries. Amazon©s trademarks and trade dress may not be used in connection with any product or service that is not Amazon©s, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Amazon Mechanical Turk Developer Guide Table of Contents Welcome ..................................................................................................................................... 1 How Do I...? ......................................................................................................................... 1 Introduction to Amazon Mechanical Turk ............................................................................................ 2 Overview of Amazon Mechanical Turk ....................................................................................... 2 Business Model ............................................................................................................ 2 Advantages .................................................................................................................. 3 Amazon Mechanical Turk Concepts .......................................................................................... 3 Requesters .................................................................................................................. 3 Workers ....................................................................................................................... 3 Human Intelligence Tasks (HITs) ...................................................................................... 4 Assignments ................................................................................................................. 4 Approval and Payment ................................................................................................... 4 Qualifications and Quality Control ..................................................................................... 4 Questions and Answers .................................................................................................. 5 Architectural Overview of Amazon Mechanical Turk ..................................................................... 6 Making Requests .......................................................................................................................... 7 Making SOAP Requests ......................................................................................................... 7 Using SOAP ................................................................................................................. 7 Using Operation Parameters With SOAP ........................................................................... 8 The Structure of a Request Message ................................................................................ 8 Making REST Requests ......................................................................................................... 9 Using REST ................................................................................................................. 9 Using Operation Parameters With REST ............................................................................ 9 Parameters Specific to REST Requests ........................................................................... 10 Sample REST Request ................................................................................................. 10 AWS Request Authentication ................................................................................................. 11 AWS Accounts ............................................................................................................ 11 Authenticating Requests ............................................................................................... 12 Summary of AWS Request Authentication ........................................................................ 12 Calculating Request Signatures ..................................................................................... 13 Using REST and SOAP Transactions .............................................................................. 13 URL Encoding ............................................................................................................. 13 Code Samples for Request Authentication ....................................................................... 13 Understanding Responses .................................................................................................... 15 Response Messages, SOAP and REST ........................................................................... 15 The Structure of a Response ......................................................................................... 15 Understanding Requesters and Workers .......................................................................................... 17 Working With Amazon Mechanical Turk Accounts ...................................................................... 17 Using Statistics and System Qualifications ............................................................................... 17 Contacting Workers .............................................................................................................. 18 Working With HITs ....................................................................................................................... 19 Creating HITs ..................................................................................................................... 19 The Title, Description, and Keywords ....................................................................................... 20 Using International Characters ....................................................................................... 20 The Reward ........................................................................................................................ 20 Deadlines and Expirations ..................................................................................................... 20 Asking Workers to Upload Files .............................................................................................. 21 Using Your Website to Host Questions ..................................................................................... 21 The Requester Annotation ..................................................................................................... 21 Understanding HIT Types .............................................................................................................. 22 HIT Types ........................................................................................................................... 22 Properties of a HIT Type ....................................................................................................... 22 How HIT Types Are Created .................................................................................................. 23 How to Change the HIT Type ................................................................................................. 23 Properties Specific to a HIT ................................................................................................... 23 API Version 2013-11-15 iii Amazon Mechanical Turk Developer Guide Creating and Managing Assignments .............................................................................................. 24 A Worker Accepts a HIT ........................................................................................................ 24 Multiple Assignments, HIT Lifetime ......................................................................................... 25 Seeing HITs In Progress ....................................................................................................... 25 The Worker Submits, Returns or Abandons the Assignment ........................................................ 25 Forcing a HIT to Expire Early ................................................................................................. 26 Retrieving and Approving Results ........................................................................................... 26 Reviewing HITs ................................................................................................................... 27 Paying the Worker a Bonus .................................................................................................... 27 Disposing of the HIT ............................................................................................................. 28 Extending a HIT .................................................................................................................
Load more

Recommended publications
  • Commvault on AWS Comprehensive Cloud Data Management for Hybrid IT Table of Contents
    Commvault on AWS Comprehensive Cloud Data Management for Hybrid IT Table of Contents The Data Management Challenge 3 Commvault and Amazon Web Services 4 Benefits 7 Case Study: Dow Jones 8 Getting Started 9 2 The Data Management Challenge Today, more data is being generated than ever before. Keeping up with the rapid pace of data growth presents a series of challenges. Enterprise organizations are collecting petabytes of customer and application data that must be backed up and accessible to meet compliance requirements. Increased regulation around data retention policies make it more difficult to manage backup and archive storage, as critical data may be required to be kept for years and maybe difficult to find. Further complicating matters, point solutions often overlap and leave gaps where data is unprotected and require additional staff to manage them. These issues lead to increased costs, yet many IT departments are facing budget cuts and cannot expand upon their capital to meet increased performance demands. Today’s hybrid IT organizations realize cloud can help solve many data storage issues. With cloud storage comes the need for a comprehensive data management platform to manage data both on-premises and in the cloud. Savvy organizations streamline IT operations and reduce cloud waste with flexible orchestration to automate resource provisioning, policies and routine tasks. This eBook will demonstrate how Commvault and Amazon Web Services (AWS) deliver a cost-effective data management solution that addresses all of these challenges with a single, scalable solution. 3 Commvault and Amazon Web Services Unlike most backup and recovery solutions, Commvault offers a single data platform solution for all backup and recovery needs; as opposed to having to several point solutions for each use case (i.e.
    [Show full text]
  • AWS Managed Services (AMS)
    AWS Managed Services (AMS) Application Developer's Guide AMS Advanced Operations Plan Version September 16, 2020 AWS Managed Services (AMS) Application Developer's Guide AMS Advanced Operations Plan AWS Managed Services (AMS) Application Developer's Guide: AMS Advanced Operations Plan Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. AWS Managed Services (AMS) Application Developer's Guide AMS Advanced Operations Plan Table of Contents Application Onboarding to AMS Introduction ........................................................................................ 1 What is Application Onboarding? ................................................................................................. 1 What we do, what we do not do .................................................................................................. 1 AMS Amazon Machine Images (AMIs) ............................................................................................ 2 Security enhanced AMIs ...................................................................................................... 4 Key terms .................................................................................................................................
    [Show full text]
  • Performance Efficiency Pillar
    Performance Efficiency Pillar AWS Well-Architected Framework Performance Efficiency Pillar AWS Well-Architected Framework Performance Efficiency Pillar: AWS Well-Architected Framework Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Performance Efficiency Pillar AWS Well-Architected Framework Table of Contents Abstract and Introduction ................................................................................................................... 1 Abstract .................................................................................................................................... 1 Introduction .............................................................................................................................. 1 Performance Efficiency ....................................................................................................................... 2 Design Principles ........................................................................................................................ 2 Definition .................................................................................................................................
    [Show full text]
  • A Data-Driven Analysis of Workers' Earnings on Amazon Mechanical Turk
    A Data-Driven Analysis of Workers’ Earnings on Amazon Mechanical Turk Kotaro Hara1,2, Abi Adams3, Kristy Milland4,5, Saiph Savage6, Chris Callison-Burch7, Jeffrey P. Bigham1 1Carnegie Mellon University, 2Singapore Management University, 3University of Oxford 4McMaster University, 5TurkerNation.com, 6West Virginia University, 7University of Pennsylvania [email protected] ABSTRACT temporarily out-of-work engineers to work [1,4,39,46,65]. A growing number of people are working as part of on-line crowd work. Crowd work is often thought to be low wage Yet, despite the potential for crowdsourcing platforms to work. However, we know little about the wage distribution extend the scope of the labor market, many are concerned in practice and what causes low/high earnings in this that workers on crowdsourcing markets are treated unfairly setting. We recorded 2,676 workers performing 3.8 million [19,38,39,42,47,59]. Concerns about low earnings on crowd tasks on Amazon Mechanical Turk. Our task-level analysis work platforms have been voiced repeatedly. Past research revealed that workers earned a median hourly wage of only has found evidence that workers typically earn a fraction of ~$2/h, and only 4% earned more than $7.25/h. While the the U.S. minimum wage [34,35,37–39,49] and many average requester pays more than $11/h, lower-paying workers report not being paid for adequately completed requesters post much more work. Our wage calculations are tasks [38,51]. This is problematic as income generation is influenced by how unpaid work is accounted for, e.g., time the primary motivation of workers [4,13,46,49].
    [Show full text]
  • Migrating to Google Cloud Storage Nearline from Amazon Glacier
    Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Migrating to Google Cloud Storage Nearline From Amazon Glacier Page 1 Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Migrating to Google Cloud Storage Nearline From Amazon Glacier Table of contents: Summary Overview Prerequisites Create a Workspace and Staging Area Create a Bucket Using the Nearline Storage Class Choose a Naming Convention Begin Storing New Data in Cloud Storage Nearline Migrating Data Stored Directly in Amazon Glacier Get an Inventory of Archives Make an Archive Available for Download Download the Archive to a Staging Area Upload Data to Cloud Storage Nearline Migrating in Batches Migrating Data Stored in Amazon Glacier via Amazon S3 Get an Inventory of Archives Make an Archive Available for Download Upload Data to Cloud Storage Nearline Migrating in Batches Understanding the Cost of Retrieving Data from Amazon Glacier Recommendations Appendix A: Creating a Workspace and Staging Area Create or Select a Cloud Platform Project Install and Configure the Cloud SDK Create and Configure a Compute Engine Instance References Page 2 Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Page 3 Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Summary Google Cloud Storage Nearline is a low cost storage class available in Google Cloud Storage which is attractive for archival workloads, such as cold storage and disaster recovery. Amazon Glacier also provides a storage service suitable for archival workloads, but retrieval latency in Amazon Glacier is measured in hours whereas Google Cloud Storage Nearline provides retrieval latency measured in seconds.
    [Show full text]
  • Amazon Mechanical Turk Developer Guide API Version 2017-01-17 Amazon Mechanical Turk Developer Guide
    Amazon Mechanical Turk Developer Guide API Version 2017-01-17 Amazon Mechanical Turk Developer Guide Amazon Mechanical Turk: Developer Guide Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Amazon Mechanical Turk Developer Guide Table of Contents What is Amazon Mechanical Turk? ........................................................................................................ 1 Mechanical Turk marketplace ....................................................................................................... 1 Marketplace rules ............................................................................................................... 2 The sandbox marketplace .................................................................................................... 2 Tasks that work well on Mechanical Turk ...................................................................................... 3 Tasks can be completed within a web browser ....................................................................... 3 Work can be broken into distinct, bite-sized tasks .................................................................
    [Show full text]
  • Dspace Cover Page
    Human-powered sorts and joins The MIT Faculty has made this article openly available. Please share how this access benefits you. Your story matters. Citation Adam Marcus, Eugene Wu, David Karger, Samuel Madden, and Robert Miller. 2011. Human-powered sorts and joins. Proc. VLDB Endow. 5, 1 (September 2011), 13-24. As Published http://www.vldb.org/pvldb/vol5.html Publisher VLDB Endowment Version Author's final manuscript Citable link http://hdl.handle.net/1721.1/73192 Terms of Use Creative Commons Attribution-Noncommercial-Share Alike 3.0 Detailed Terms http://creativecommons.org/licenses/by-nc-sa/3.0/ Human-powered Sorts and Joins Adam Marcus Eugene Wu David Karger Samuel Madden Robert Miller {marcua,sirrice,karger,madden,rcm}@csail.mit.edu ABSTRACT There are several reasons that systems like MTurk are of interest Crowdsourcing marketplaces like Amazon’s Mechanical Turk (MTurk) database researchers. First, MTurk workflow developers often imple- make it possible to task people with small jobs, such as labeling im- ment tasks that involve familiar database operations such as filtering, ages or looking up phone numbers, via a programmatic interface. sorting, and joining datasets. For example, it is common for MTurk MTurk tasks for processing datasets with humans are currently de- workflows to filter datasets to find images or audio on a specific sub- signed with significant reimplementation of common workflows and ject, or rank such data based on workers’ subjective opinion. Pro- ad-hoc selection of parameters such as price to pay per task. We de- grammers currently waste considerable effort re-implementing these scribe how we have integrated crowds into a declarative workflow operations because reusable implementations do not exist.
    [Show full text]
  • Amazon Mechanical Turk Requester UI Guide Amazon Mechanical Turk Requester UI Guide
    Amazon Mechanical Turk Requester UI Guide Amazon Mechanical Turk Requester UI Guide Amazon Mechanical Turk: Requester UI Guide Copyright © 2014 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. The following are trademarks of Amazon Web Services, Inc.: Amazon, Amazon Web Services Design, AWS, Amazon CloudFront, Cloudfront, Amazon DevPay, DynamoDB, ElastiCache, Amazon EC2, Amazon Elastic Compute Cloud, Amazon Glacier, Kindle, Kindle Fire, AWS Marketplace Design, Mechanical Turk, Amazon Redshift, Amazon Route 53, Amazon S3, Amazon VPC. In addition, Amazon.com graphics, logos, page headers, button icons, scripts, and service names are trademarks, or trade dress of Amazon in the U.S. and/or other countries. Amazon©s trademarks and trade dress may not be used in connection with any product or service that is not Amazon©s, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Amazon Mechanical Turk Requester UI Guide Table of Contents Welcome ..................................................................................................................................... 1 How Do I...? ......................................................................................................................... 1 Introduction to Mechanical Turk .......................................................................................................
    [Show full text]
  • Privacy Experiences on Amazon Mechanical Turk
    113 “Our Privacy Needs to be Protected at All Costs”: Crowd Workers’ Privacy Experiences on Amazon Mechanical Turk HUICHUAN XIA, Syracuse University YANG WANG, Syracuse University YUN HUANG, Syracuse University ANUJ SHAH, Carnegie Mellon University Crowdsourcing platforms such as Amazon Mechanical Turk (MTurk) are widely used by organizations, researchers, and individuals to outsource a broad range of tasks to crowd workers. Prior research has shown that crowdsourcing can pose privacy risks (e.g., de-anonymization) to crowd workers. However, little is known about the specific privacy issues crowd workers have experienced and how they perceive the state ofprivacy in crowdsourcing. In this paper, we present results from an online survey of 435 MTurk crowd workers from the US, India, and other countries and areas. Our respondents reported different types of privacy concerns (e.g., data aggregation, profiling, scams), experiences of privacy losses (e.g., phishing, malware, stalking, targeted ads), and privacy expectations on MTurk (e.g., screening tasks). Respondents from multiple countries and areas reported experiences with the same privacy issues, suggesting that these problems may be endemic to the whole MTurk platform. We discuss challenges, high-level principles and concrete suggestions in protecting crowd workers’ privacy on MTurk and in crowdsourcing more broadly. CCS Concepts: • Information systems → Crowdsourcing; • Security and privacy → Human and societal aspects of security and privacy; • Human-centered computing → Computer supported cooperative work; Additional Key Words and Phrases: Crowdsourcing; Privacy; Amazon Mechanical Turk (MTurk) ACM Reference format: Huichuan Xia, Yang Wang, Yun Huang, and Anuj Shah. 2017. “Our Privacy Needs to be Protected at All Costs”: Crowd Workers’ Privacy Experiences on Amazon Mechanical Turk.
    [Show full text]
  • Crowdsourcing for Speech: Economic, Legal and Ethical Analysis Gilles Adda, Joseph Mariani, Laurent Besacier, Hadrien Gelas
    Crowdsourcing for Speech: Economic, Legal and Ethical analysis Gilles Adda, Joseph Mariani, Laurent Besacier, Hadrien Gelas To cite this version: Gilles Adda, Joseph Mariani, Laurent Besacier, Hadrien Gelas. Crowdsourcing for Speech: Economic, Legal and Ethical analysis. [Research Report] LIG lab. 2014. hal-01067110 HAL Id: hal-01067110 https://hal.archives-ouvertes.fr/hal-01067110 Submitted on 23 Sep 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Crowdsourcing for Speech: Economic, Legal and Ethical analysis Gilles Adda1, Joseph J. Mariani1,2, Laurent Besacier3, Hadrien Gelas3,4 (1) LIMSI-CNRS, (2) IMMI-CNRS, (3) LIG-CNRS, (4) DDL-CNRS September 19, 2014 1 Introduction With respect to spoken language resource production, Crowdsourcing – the process of distributing tasks to an open, unspecified population via the inter- net – offers a wide range of opportunities: populations with specific skills are potentially instantaneously accessible somewhere on the globe for any spoken language. As is the case for most newly introduced high-tech services, crowd- sourcing raises both hopes and doubts, certainties and questions. A general analysis of Crowdsourcing for Speech processing could be found in (Eskenazi et al., 2013). This article will focus on ethical, legal and economic issues of crowdsourcing in general (Zittrain, 2008a) and of crowdsourcing services such as Amazon Mechanical Turk (Fort et al., 2011; Adda et al., 2011), a major plat- form for multilingual language resources (LR) production.
    [Show full text]
  • Using Amazon Mechanical Turk and Other Compensated Crowd Sourcing Sites Gordon B
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Opus: Research and Creativity at IPFW Indiana University - Purdue University Fort Wayne Opus: Research & Creativity at IPFW Organizational Leadership and Supervision Faculty Division of Organizational Leadership and Publications Supervision 7-2016 Using Amazon Mechanical Turk and Other Compensated Crowd Sourcing Sites Gordon B. Schmidt Indiana University - Purdue University Fort Wayne, [email protected] William Jettinghoff Indiana University - Bloomington Follow this and additional works at: http://opus.ipfw.edu/ols_facpubs Part of the Industrial and Organizational Psychology Commons, and the Organizational Behavior and Theory Commons Opus Citation Gordon B. Schmidt and William Jettinghoff (2016). sinU g Amazon Mechanical Turk and Other Compensated Crowd Sourcing Sites. Business Horizons.59 (4), 391-400. Elsevier. http://opus.ipfw.edu/ols_facpubs/91 This Article is brought to you for free and open access by the Division of Organizational Leadership and Supervision at Opus: Research & Creativity at IPFW. It has been accepted for inclusion in Organizational Leadership and Supervision Faculty Publications by an authorized administrator of Opus: Research & Creativity at IPFW. For more information, please contact [email protected]. Business Horizons (2016) 59, 391—400 Available online at www.sciencedirect.com ScienceDirect www.elsevier.com/locate/bushor Using Amazon Mechanical Turk and other compensated crowdsourcing sites a, b Gordon B. Schmidt *, William M. Jettinghoff a Division of Organizational Leadership and Supervision, Indiana University-Purdue University Fort Wayne, Neff 288D, 2101 East Coliseum Blvd., Fort Wayne, IN 46805, U.S.A. b Indiana University Bloomington, 8121 Deer Brook Place, Fort Wayne, IN 46825, U.S.A.
    [Show full text]
  • Using Amazon Web Services for Disaster Recovery October 2014
    Amazon Web Services – Using AWS for Disaster Recovery October 2014 Using Amazon Web Services for Disaster Recovery October 2014 Glen Robinson, Attila Narin, and Chris Elleman Page 1 of 22 Amazon Web Services – Using AWS for Disaster Recovery October 2014 Contents Introduction ...............................................................................................................................................................3 Recovery Time Objective and Recovery Point Objective ................................................................................................4 Traditional DR Investment Practices ............................................................................................................................4 AWS Services and Features Essential for Disaster Recovery ...........................................................................................5 Example Disaster Recovery Scenarios with AWS ...........................................................................................................9 Backup and Restore ................................................................................................................................................9 Pilot Light for Quick Recovery into AWS ................................................................................................................. 11 Warm Standby Solution in AWS ............................................................................................................................. 14 Multi-Site Solution Deployed
    [Show full text]