Editing The Wikipedia Adventure

From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
Project page for The Wikipedia Adventure paper co-authored by Sneha Narayan, Jake Orlowitz, Jonathan Morgan, Mako Hill, and Aaron Shaw.
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==
==Resources==
Line 11: Line 6:




== Current TO DO list ==
==Timeline for CSCW 2017 submission==
* '''introduction'''
* '''Background and prior work'''
** Continue to improve gamification subsection (mako)
* '''System design'''
** Use Webstrates paper (UIST 2015) as a model (mako)
* '''Study 1:'''
* '''Study 2:'''
* '''Discussion & Conclusion'''
** make sure connections to framing are clear
* '''Throughout'''
** Full read-throughs for tone, consistency, clear contributions.
** Proofreading


== Recent changes log ==
===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)


'''These have been addressed, but will likely still benefit from further attention so they're here for archival purposes'''
===Friday, May 6th===
 
* revise subsections for study 1 to keep refining structure (see Aaron's comments in the document)
* '''introduction'''
* revise introduction and framing.
* compress the introduction. reduce redundancy (as)
** add justification for 2-study design
** focus on two study framing
** incorporate the argument that large-scale field testing is important.
** Change framing to show that two studies were always part of the plan
** Incorporate idea that large scale field testing is important
** emphasize hypotheses
*** challenges of deploying new systems in a massive community with passionate, experienced members
*** 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).
*** large-scale user survey and invitation-based field experiment under realistic conditions provide more useful evidence (than hallway testing or small-scale usability studies).
* '''Study 1:'''
* revise the discussion (make sure Jake's concerns are addressed).
** replace bar charts w new visualizations (sn)
* share completed draft with collaborators
* '''Study 2:'''
** emphasize hypotheses
** add details of random assignment (sn)
** add more descriptive information about the sample and experiment
** incorporate randomization check (compare days in study across treatment & control)
** restrict main analysis to last 100 days of sampling (sn)
*** revise '''all''' reported statistics to reflect this
** include boxplots (w scatter) of dependent variables for all treatment and control units.
** Include Mann-Whitney tests for distribution shift
* '''Discussion & Conclusion'''
** Make sure to address big contributions.
** Elaborate explanations of null effect.
** Note that most studies on gamified systems don't do quantitative impact assessment, highlight this as a contribution of our


* '''Throughout'''
===Friday, May 13th===
* re-built refs-processed and eliminated missing citation errors (as)
* incorporate feedback from collaborators (double check with Jake)
* change language around Teahouse (jm)
** Add citations currently in text
** Remove excess uses of passive voice
** Add keywords and ACM categories.


==Timeline for CSCW 2017 submission==
===Friday, May 20th===
 
* do multiple passes through the whole paper, editing language, grammar and everything else (sn, as, whoever else wants to)
* share this with folks peer reviewing CSCW paper (sn)
* read it a hundred times, make sure the title works
* read it a hundred times, make sure the title works


===Friday, May 27th===
===Friday, May 27th===
* submit final version! (though earlier is better)
* submit final version! (though earlier is better)
== Post-submission TO-DO list ==
* Reproducibility
** Create RData files for all datasets, models, results, etc.
** Convert paper to .rnw (knitr).
** Create communitydata (wiki?) page to host reproducibility content
** Make sure git repository is up to date and all files have READMEs
* Study 2 analysis
** Report full models w all model fit stats etc. (presumably we cut this down for the CHI note. No need for CSCW).
** Collect additional covariates and include them in the models
*** user data via API (gender, edit count pre-inclusion in the study, etc.)
*** added measures should enhance precision of estimates (even smaller SEs!)
** Convert boxplots to a faceted grid in ggplot2.
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)