Milestone 4 Opera Transparency:FairPay

From crowdresearch
Jump to: navigation, search

Idea

Current idea is to achieve the goal of fair payment. Payment should be done transparently, timely and effectively (i.e., decoupling the payment from rejecting the task).

If requester expects to finish the tasks sooner then the price for the tasks can be quoted at a higher amount and the price will go down as the time progress. Lets say, for the first hour the price will be 3 times the initial quoted price and for subsequent hour it will be 2 and then will move its to original price (Original idea from The Kickstarter Model).

Before submitting a task, a minimum payment (say 20%) needs to be paid by requester for the task. It is based on N parameters including the quoted price by the requester like complexity, time taken, urgency etc. This payment will be used to compensate workers in case there is an incorrect rejection by the requester or to pay the workers in case the remaining payment by the worker is not done on time. Both of these steps are shown in below figure

OperaTrans Step1.jpg

Check points will be put by system to review intermediately and proceed further in finishing the tasks. For example: 100 HITs are submitted by a requester and first few check points will be with less number of HITs. Let’s say first check point is for 10% of the submitted work then workers can pick only 10 HITs. After this, requester needs to review and accept/reject the tasks. Improved the original idea of check point Checkpoint System

If the rejection rate is less, then requester need to clear the remaining payment for 10% of work and make new minimum payment for next check point say 40%. The subsequent checkpoint is the end one or may contain more iterations. Less number of iterations will help in reducing the overall time taken to finish. If the payment for previous checkpoint is not done then system will ensure that the requester will not get the subsequent HITs done by workers.

If the number of rejections is more than a certain percent say 50% then the requirements of the tasks to the reviewed and/or to update the tasks accordingly. If based on the more info added to the task, if complexity or time to complete increases then the price of the subsequent tasks needs to be increased. System will allow increasing such payment.

The flow chart in the below figure explains the remaining steps of the flow, once the requester gets approval for proceeding further. OperaTrans Step2.jpg


Limitation

The system may slow down the completion time of a request because of check points but this will help in more happy workers and requesters will be happy with quality of work.