The Wikipedia Adventure: Difference between revisions

From CommunityData
No edit summary
Line 18: Line 18:
* Revise introduction to focus on two study framing
* Revise introduction to focus on two study framing
**Incorporate idea that large scale field testing is important
**Incorporate idea 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).
* Change framing to focus on gamification as well
* Change framing to focus on gamification as well
** Examples from Jake's notes
** Examples from Jake's notes
Line 25: Line 26:
* Fix citations
* Fix citations
* Incorporate UIST model paper system evaluation stuff suggested by Mako
* Incorporate UIST model paper system evaluation stuff suggested by Mako
** Use Webstrates paper (UIST 2015) as a model.
* Refine organization of Study 1 findings
* Refine organization of Study 1 findings
* Refine Study 2 Discussion (Jmo)
** Explain why TWA didn't alter behavior
* Add overarching discussion & conclusion sections
* Add overarching discussion & conclusion sections
** Make sure to
* Analyze differential attrition


==Timeline for CSCW 2017 submission==
==Timeline for CSCW 2017 submission==
===Friday, May 6th===
** 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).
===Thursday, May 12th===
* revise discussion to incorporate two study framing, and make sure concerns about framing TWA as a failure are addressed (Sneha)
* make sure the description of study 1 is consistent with how Jake and Jonathan remember conducting it (Sneha)
* Analyze differential attrition in field experiment (Sneha)
* Beef up systems design and evaluation section (Jonathan, Jake)
** Explain design rationale
** Identify key features
** Use Webstrates paper (UIST 2015) as a model.


===Friday, May 13th===
===Friday, May 13th===

Revision as of 20:27, 13 May 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.


Current TO DO list

  • Fill in section about "Why Gamify Being a Wikipedian?"
  • Determine what should be in the discussion section
  • Redo bar chart graphics
  • Revise introduction to focus on two study framing
    • Incorporate idea 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).
  • Change framing to focus on gamification as well
    • Examples from Jake's notes
    • See Mako for other sources
    • Hamari HICCS
  • Fix citations
  • Incorporate UIST model paper system evaluation stuff suggested by Mako
    • Use Webstrates paper (UIST 2015) as a model.
  • Refine organization of Study 1 findings
  • Refine Study 2 Discussion (Jmo)
    • Explain why TWA didn't alter behavior
  • Add overarching discussion & conclusion sections
    • Make sure to
  • Analyze differential attrition

Timeline for CSCW 2017 submission

Friday, May 13th

  • redo survey bar charts and graphics
  • get citations working
  • build up a prior work section gamified tutorials

Friday, May 20th

  • read it a hundred times, make sure the title works

Friday, May 27th

  • submit final version! (though earlier is better)