WinterMilestone 1 Lightsaber

From crowdresearch
Revision as of 17:09, 16 January 2016 by Vijaymahanteshsiddappamurganoor (Talk | contribs) (Experience the life of a Worker on Mechanical Turk)

Jump to: navigation, search

Experience the life of a Worker on Mechanical Turk

What do you think can be improved about the system?

  • The worker doing manual task of entering data and putting it in a webform might be boring after so many repetitions. So having options to mixing it up with a HIT tasks might be an interesting idea to explore.
  • Building systems and tasks that not only collects data but also coaches it workers to be skillful in new tasks and doing it faster and better. Ex : Any web crawling based tasks, the worker has to open a new tab get the data and writing about it on a new tab can kill some time.
  • There is no minimum wage set by the amazon turk system. Following the state and country laws for minimum wage will be good for both workers and requesters. We think having uber pricing model is better.
  • In the current system, If the result is not adequate, the job is rejected and the requester is not required to pay. Tailoring the models to have partial pay will be encouraging to workers.

Experience the life of a Requester on Mechanical Turk

Reflect on your experience as a requester on Mechanical Turk. What did you like? What did you dislike? Also attach the CSV file generated when you download the HIT results. If you're from outside the USA and unable to access MTurk, you can try the MTurk requester sandbox, or CrowdFlower or Microworkers or Clickworker

Explore alternative crowd-labor markets

Compare and contrast the crowd-labor market you just explored (TaskRabbit/oDesk/GalaxyZoo) to Mechanical Turk.



What do you like about the system / what are its strengths?

It tailors to the local users. Based on the paper, the mobile phone penetration is relatively high, about 50%, and the cost of mobile internet is very low. Therefore, it is much easier to attract new users and distribute micro-tasks through mobile. The information is broken into pieces. Users might have different size of screens depending on what device they use. MobileWorks breaks the information into small pieces for users to process, and then put them back together after they complete the task. It makes the user experience better because MobileWorks won’t have to worry if users can view the information properly on their screen.

It is fairly accessible. Since users can complete all the tasks on their phones, it is very easy for them to access anytime they want, and this certainly goes well along with the mobile trend.

What do you think can be improved about the system?

First of all, we think the paper could have been more comprehensive. For example, when the author(s) tried to demonstrate the quality and efficiency, I think it’s hard to compare or determine if they were able to reach high efficiency because there wasn’t too much information for readers to compare.

The system can possibly further improve the way they send and retrieve information. At the moment, the system breaks down the information into pieces and send them to users one by one. While this might avoid the loss of information, it is still not the most effective way to process information.

Collecting data on user behaviors could be one way to solve this problem. If the system has the ability to detect what kind of device the user is using and makes it a larger sample, it’s possible to understand what devices most users have in order to make the information processing more seamlessly. Optimizing the way the system sends users information might help users save power of the phone as well as internet usage.


  • What do you like about the system / what are its strengths?
  • What do you think can be improved about the system?

Flash Teams

  • What do you like about the system / what are its strengths?
  • What do you think can be improved about the system?

Milestone Contributors

Slack usernames of all who helped create this wiki page submission: @kessyena, @reneelin, @mahsa, @marim_g