Difference between revisions of "Winter Milestone 9"

From crowdresearch
Jump to: navigation, search
(Task Feed)
(Task Feed)
Line 19: Line 19:
 
**Use the new data from the task time and rejection rate to better rank the taskfeed.
 
**Use the new data from the task time and rejection rate to better rank the taskfeed.
 
**Use the new data from the accepted/rejection rate to alter the cascade.
 
**Use the new data from the accepted/rejection rate to alter the cascade.
*Brainstorming studies for the paper: hangout will be held on Thursday evening. '''@michaelbernstein''' will join for the second half.
+
*Brainstorming studies for the paper: hangout will be held on Thursday 8pm. '''@michaelbernstein''' will join for the second half.
 
*A complete outline of the paper.
 
*A complete outline of the paper.
  

Revision as of 21:06, 7 March 2016

Due date (PST): 8:00 pm 13th March 2016 for submission, 12 pm 14th 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 9 slideshow: coming soon...

Task Feed

Great work last week on our mockups, frontend, and backend implementations!

This week we are continuing our push for the UIST submission. Our goals for this week are the following:

  • Frontend implementation of our timer/data collection mock - finished by Friday. TBD: which mock to use.
  • Design review of the taskfeed and timer on Saturday @christopher.diemert and others.
  • Backend implementation of task time:
    • Data model to record the collection.
    • SQL to compute the predicted time a worker will spend on a given task that appears on their feed.
  • Backend update of Boomerang:
    • Use the new data from the task time and rejection rate to better rank the taskfeed.
    • Use the new data from the accepted/rejection rate to alter the cascade.
  • Brainstorming studies for the paper: hangout will be held on Thursday 8pm. @michaelbernstein will join for the second half.
  • A complete outline of the paper.

We will be having a very brief hangout on Tuesday at 10AM Pacific to divide up work and discuss any questions about this week's milestones.

With the internal deadline on April 3rd, we are going to need all hands on deck for the next month. Whether you are a developer, designer, writer, thinker, etc. there will always be something for you to work on. Please pick up anything and give a yell in the channel so everyone knows who is working on what and so that we can help and guide each other. As always, feel free to reach out to @aginzberg or @dmorina individually with any questions.


Topic background

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

In addition...

  • to identify tasks I can do on my own time
  • to learn new skills

Task Authoring

Our goal for this week is to run our second pilot study to observe the variance between task authorship and task quality.

Watch last week's task authoring meeting here

First half of this week (Volunteer to be a requester): Please message @catherine.mullings for that. Instructions will be released by Wednesday/Thursday.

By Wednesday, brainstorm a task or find dataset to give to requesters in our pilot study. Think of tasks that are more complex than image labeling or doing sentiment judgements. For example, one task might be to transcribe Youtube videos. Transcription is a much more involved task for workers and final results are subjective and up to interpretation.

By Saturday/Sunday, analyze results: After the task results are received, we will analyze the results from the experiment during a Google Hangout on Saturday/Sunday.

The analysis for the study will be formally written 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. Please create a storyboard, to walk us through it step-by-step. Example below:

Storyboard example

Helpful links:

You can use balsamic or Google slides or just pencil/paper drawing 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