Difference between revisions of "Winter Milestone 8"
|Line 8:||Line 8:|
== Task Feed ==
== Task Feed ==
goals for this week :
*the .to the workers report time spent .
*and the to the time spent
the to the rejection and to the .
*and of . .
Revision as of 20:07, 29 February 2016
Due date (PST): 8:00 pm 6th March 2016 for submission, 12 pm 7th March 2016 for peer-evaluation.
This week, we will refine methods and systems proposed last week further:
- Youtube link of the meeting today: watch
- Winter Meeting 8 slideshow: coming soon...
Last week we achieved near convergence on our taskfeed system proposal and generated some mocks for our new taskfeed!
This week we are beginning the push for our UIST submission. Our goals for this week are the following:
- Design mocks for the data collection part of the taskfeed (i.e. how are we going to change the actual tasks so that workers can report time spent working).
- Front end implementation of our taskfeed mocks from last week (make basic HTML and CSS changes on the taskfeed to display the necessary data: rejection rate and time spent).
- Back end implementation of rejection rate (write the SQL needed to compute the rejection rates of each task for a given worker and return to the frontend).
- Continued refinement and writeup of our system and methodologies. If enough cycles, begin outlining or even writing the paper.
Check out our system proposal, mainly first few pages and comments to catch up on what we've been working on and thinking about.
The task feed hangouts from previous weeks:
- Youtube link of the task feed meeting 1: watch
- Youtube link of the task feed meeting 2: watch
- Youtube link of the task feed meeting 3: watch
Michael's synthesized needs:
- to find new tasks that will maximize income (reduce uncertainty in payment, rejection, maximize certainty in what will be asked of me and how quickly I can do it)
- to find new tasks that fit my expertise profile
- to refind old requesters' new tasks, since I know I like them
- to identify tasks I can do on my own time
- to learn new skills
Our goal for this week is to run experiments, then analyze the findings and write up a report. By the end of the week, we want to produce a report with findings from our pilot experiments - this will help us in making future decisions.
First half of the week (Volunteer to be a requester): Pilot participants should try to finish their HTML task designs, that takes about an hour. Please message @catherine.mullings for that. Once we have your task designs, @dmorina will post them on Mechanical Turk for you. The taskauthoring folks are looking for a couple volunteers to create some tasks for four datasets that we have. We give you the task and some example input/outputs, and you try to write a task interface in Mechanical Turk that will get workers to produce the right answers.
Second half of the week (analyze+report): We analyze the results from the experiment, conduct a Google hangout with @michaelbernstein, and produce a report on the findings. We can start making contributions to the report here on Google doc.
Open Gov and Design
Check out this week's meeting, and based on the open gov discussions here - create a mock, minimal design within Daemo. Think about questions like: how does it work as a system? how it would fit in Daemo? Like, walk us through. I’m a new worker on Daemo. What do I do? Am I already part of a guild? How do I get into one? How do I get work once I’m in one? What if the requester doesn’t like what I do? And how does all this solve the reputation problem? Try to pitch a story/wireframe with specific design that has as few moving parts as possible.
You can use balsamic or Google slides to give shape to your ideas. Design folks, come join and help move this effort forward. Once you're done, post here: http://crowdresearch.meteor.com/category/open-gov