Upload
steven-lehrburger
View
759
Download
5
Embed Size (px)
DESCRIPTION
Feature breakdown and initial ideas on what interface features will be necessary for my group's RapidSMS/Mechanical Turk project in Clay Shirky's Design for UNICEF class at NYU's Interactive Telecommunications Program.
Citation preview
SMS Check
Interface Proposals
Admin panel requirements
• Payment configuration• Credit card info• MTurk account info• Balance available
• Control amount of redundancy, based on cost considerations and importance of good data• Text entry for HIT instructions• ?? View and Accept/Reject completed HITs (accepted HITs inserted in database)• View statistics on total cost, completed HITs
Things to be done with an SMS:
1. Classification2. Correction3. Response
Classification
• Unusable messages sent to MTurk• Worker sees original SMS and selects the type
• Data entry error• Question• Emergency• "You're welcome"• Other
• Admin panel requirements• Select which are displayed• Create custom choices
Correction
• Data entry error messages sent to MTurk• Worker sees original SMS and fills text fields
• Text fields correspond to database columns• Option to split into multiple database entries
• Admin panel requirements• Addition/modification/deletion of fields generated from database columns• Creation of detailed description of what sort of data can go in each field
Response
• Question messages sent to MTurk• Worker sees original SMS and list of possible responses to be chosen from (radio buttons)• Admin panel requirements
• View previous SMS messages classified as questions that required answers• Write new answers to appear in list of possible responses from which workers will choose
New focus -> new name?
• SMS Check
• PreText, PostText, PerText
• Textonic
• Smurk, RapidTurk, Smarter Message Service
• Detextive