Studying cooperation and conflict between authors with history flow visualizations
By Fernanda B. Viégas, Martin Wattenberg, Kushal Dave. International Conference on Human Factors in Computing Systems, 2004
951 citations recorded by the source corpus.
Subfields: Communication, Computer Vision and Pattern Recognition, Information Systems
View Paper: https://www.semanticscholar.org/paper/3b799b49a0ae657f9935089199d7c393d50bb988
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Communication
- Robert E. Kraut
- Aniket Kittur
- Loreen Terveen
- Amy S. Bruckman
- Katherine A. Panciera
- Brian S. Butler
- Susan L. Bryant
- Les Gasser
In Computer Vision and Pattern Recognition
- Bernardo A. Huberman
- Loreen Terveen
- Shyong K. Lam
- Dennis M. Wilkinson
- Susan L. Bryant
- Amy S. Bruckman
- Benno Stein
- Les Gasser
In Information Systems
- Loreen Terveen
- John Riedl
- Robert E. Kraut
- Shyong K. Lam
- Laura A. Dabbish
- Jason Tsay
- Nayer M. Wanas
- Amr Magdy
Citations in the corpus
- A systemic and cognitive view on collaborative knowledge building with wikis (2008, methodology): “The application of a history flow diagram could be a method which makes such activities visible (Viégas et al. 2004).”
- Automatic Vandalism Detection in Wikipedia (2008, background): “Vandalism was recognized as an open problem by researchers studying online collaboration [2,4,5,6,7,8], and, of course, by the Wikipedia community.”
- Becoming Wikipedian: transformation of participation in a collaborative online encyclopedia (2005, methodology): “The history flow visualization method was developed as a collaborative effort between MIT and IBM researchers to examine editing trends on wikis [23].”
- Volunteered Geographic Information: the nature and motivation of produsers (2009, background): “Viegas et al. (2004) and more recently Priedhorsky et al. (2007) offer excellent examples of empirical research into quantifying and characterizing the prevalence of such entries in Wikipedia and propose approaches to their quick correction.”
- Harnessing the wisdom of crowds in wikipedia: quality through coordination (2008, background): “Studies have found content of comparable quality to traditional encyclopedias [7], and that vandalism and inaccuracies are often reverted within a matter of minutes [18][31].”
- He says, she says: conflict and coordination in Wikipedia (2007, background): “The notable exception is [23], which examined ~3500 edits in which mass deletion of content occurred.”
- Beyond vandalism: Wikipedia trolls (2010, background): “Viégas, Wattenberg and Dave [13] found that about half of all entries having a mass deletion (i.e. more than 90% of the content was deleted) were repaired within three minutes, while the over-all average repair time was 7.7 days.”
- Assessing Information Quality of a Community-Based Encyclopedia (2005, methodology): “[23] reported the values of one IQ measure in their May 2003 analysis of the Wikipedia features.”
- Understandable Big Data: A survey (2015, methodology): “Dave [29] present history flow as a visualization technique designed to show the evolution of a document efficiently with respect to the contributions of its different authors.”
- Information quality work organization in wikipedia (2008, positive): “Viegas, Wattenberg, and Dave (2004) developed a tool (history flow) to visualize Wikipedia content evolution by using article version histories .”
- Social coding in GitHub: transparency and collaboration in an open software repository (2012, background): “history flow system which visualizes collaborator edits to Wikipedia articles [26]).”
- Don't look now, but we've created a bureaucracy: the nature and roles of policies and rules in wikipedia (2008, background): “Studies of Wikipedia activities [5, 11, 42, 43] and anecdotal discussions among participants [49] suggest that these policies, rules, and guidelines play an important part in both the day-to-day operations and overall success of Wikipedia.”