The Wikipedia Adventure: Difference between revisions
From CommunityData
No edit summary |
|||
Line 24: | Line 24: | ||
===Friday, May 6th=== | ===Friday, May 6th=== | ||
* revise subsections for study 1 to keep refining structure (see Aaron's comments in the document) | * revise subsections for study 1 to keep refining structure (see Aaron's comments in the document) | ||
* redo survey bar charts and graphics | |||
* revise introduction and framing. | * revise introduction and framing. | ||
** add justification for 2-study design | ** add justification for 2-study design |
Revision as of 20:17, 29 April 2016
Project page for The Wikipedia Adventure paper co-authored by Sneha Narayan, Jake Orlowitz, Jonathan Morgan, Mako Hill, and Aaron Shaw.
Current Status
We are in the process of revising this for submission to CSCW 2017. The timeline and milestones for submission are living on this page (below).
Resources
- We're writing on sharelatex. The project lives here.
- Bibliography is currently stored in a shared zotero directory. Aaron and Mako can share access if needed.
Timeline for CSCW 2017 submission
Friday, April 29
- draft methods from survey study (Sneha)
- draft results from survey study (Sneha)
- draft restructuring of section headers (Sneha)
- recover old pieces of design rationale and add to system design section (Sneha)
- read & discuss new draft sections (Aaron)
- plan next revision (Sneha & Aaron)
- upload to sharelatex (Sneha)
Friday, May 6th
- revise subsections for study 1 to keep refining structure (see Aaron's comments in the document)
- redo survey bar charts and graphics
- revise introduction and framing.
- add justification for 2-study design
- incorporate the argument that large-scale field testing is important.
- challenges of deploying new systems in a massive community with passionate, experienced members
- large-scale user survey and invitation-based field experiment under realistic conditions provide more useful evidence (than hallway testing or small-scale usability studies).
- revise the discussion (make sure Jake's concerns are addressed).
- share completed draft with collaborators
Friday, May 13th
- incorporate feedback from collaborators (double check with Jake)
Friday, May 20th
- read it a hundred times, make sure the title works
Friday, May 27th
- submit final version! (though earlier is better)