WinterMilestone 2 Ganler=edit

Soylent : A word Processor with a crowd inside

Need

1. Human contributions into the interfaces

2. To shorten documents, proofread documents and edit parts of their document on demand.

3. to correct Word, grammar spelling mistakes

4. the task is huge to execute (proofreading)

5. Trimming through paragraphs to fit in the size of the document.

6. There is a need more than good interfaces aid and good artificial intelligences

7. Need for easy word processing

8. Difficulty in writing – grammar, spelling mistakes.(Crowdproof)

9. Easy work to change tenses of sentences

10. Large tasks for a writer for change in a decision

11. Help in complex cognition and manipulation tasks

12. Help from friends and other people

13. Need to take care of these complex tasks for writers

14. Need to monitor spell checks

15. Need to correct sentences without change in the sentence meaning (Shortn)

16. Need for these text corrections to be done in real time

17. Need for the correctors to understand the context

18. Solutions must maintain privacy, give timely output and be cost-effective

19. Need for the provided corrections themselves to be proof-read

20. Need for prevention of errors into the document

21. Need for the correctors to choose their comfortable area of correction

22. Need for the corrections to be notified to the owner

23. Need for the writer to be familiar with the new correction interface

24. Need for the corrections to be done as quickly as possible

25. Need to find the error, fix it and verify the error (followed by Soylent)

26. Need for sentence compression

27. To maintain the content length within the time frame

Shortn

28. Need for the writer to express his expectation out of paragraph shortening

29. Need for the writer to provide real time feedback which correction takes place

30. Need for user to have control over the corrections (incorporated in Crowdproof)

31. The writer should have the freedom to choose the paragraph or sentence which should be edited or corrected

32. Need to efficiently convey the necessary methods of correction to the computer using scripting

33. Need to convey the necessary correction to be done efficiently to a human corrector

34. An intuitive interface for the writer and the corrector to understand what is going on

35. The control in the hands of the writer to allow how many people need to work on his content

36. Need for the writer to correct his instructions as he gets misunderstood work from the turkers(correctors)

37. Need to verify of the correctors have understood the instructions or are they just working without even reading/understanding the instructions.

38. To minimize lazy turkers from undedicated working

39. Avoid overwork to further complicate the task for the writers (Eager Beavers)

40. Need to motivate the turkers to work efficiently. (Find-Fix-Verify)

41. Need to generalize the number of turkers allowed to work on a task

42. Need for artitificial intelligence support to help turkers work better

43. Need for a standard communication pattern from the turkers side

44. Need for turker to be familiar with the topic to which he is about to contribute.

A Plea to Amazon: Fix Mechanical Turk!

Need

1. to get the basics of crowdsourcing right

2. to understand the foundation of MTurk and build over it

3. to scale up

4. To manage the complex API

5. To manage execution time

6. To ensure quality

7. Of a system which is more than just matching requesters and workers

8. A better interface to post tasks

9. A easy way to search tasks and start work faster

10. A better worker scrutinizing system for the requester to rely upon and majorly focus on providing tasks

11. A better interface which helps requesters easily manage work with a crowd

12. A worker reputation system

13. A system which helps the requestors differentiate good workers from the bad

14. A system to retain the good workers in the marker

15. To have a more public qualification tests

16. To keep track of working history

17. To allow rating of workers

18. To disconnect payment from rating

19. To differentiate spammers from honest workers who have produced different results

20. To separate HITS and ratings by type

21. To make all the mentioned points accessible from an API, which helps in automatic hiring decisions

22. A requester trustworthiness guarantee for a worker

23. To show speed of payment

24. To show the rejection rate for the requester

25. To show the appeal rate for the requester

26. To disallow the ability to reject work that is not spam

27. To show total volume of posted work

28. To make all the mentioned points accessible from an API

29. A better task search interface

30. A better way to predict the task completion time

31. A browsing system

32. To improve the search engine

33. To use a recommender system to propose HITs to workers