Winter Milestone 8
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:
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 task interface for workers to report time spent working).
- Frontend implementation of our taskfeed mocks from last week and this week (make basic HTML and CSS changes on the taskfeed to display and collect the necessary data: rejection rate and time spent).
- Backend 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 - particularly the task time system. If enough cycles, begin outlining the paper or working on related work.
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.
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 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:
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