The jabberwocky programming environment for structured social computing
By Salman Ahmad, Alexis Battle, Zahan Malkani, Sepandar D. Kamvar. 2011
144 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Computer Science Applications
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Adam Marcus
- Aditya G. Parameswaran
- Michael S. Bernstein
- Melissa A. Valentine
- Samuel Madden
- Bjoern Hartmann
- Anand Pramod Kulkarni
- Matthew Can
In Computer Science Applications
- Adam Marcus
- Aditya G. Parameswaran
- Michael S. Bernstein
- Melissa A. Valentine
- Sewoong Oh
- Samuel Madden
- Rob Miller
- David R Karger
Citations in the corpus
- Collaboratively crowdsourcing workflows with turkomatic (2012, background): “Jabberwocky can target workers in both paid and volunteer workforces [4].”
- Counting with the Crowd (2012, background): “In the databases field, several crowd-powered databases and query executors including CrowdDB [10], Deco [19], Jabberwocky [1], and our own Qurk [16] enable users to issue data-oriented tasks to crowd workers.”
- Challenges in Data Crowdsourcing (2016, background): “There are a variety of systems that provide procedural mechanisms to decompose a problem into tasks issued by humans, including Turkit [30], Automan [12], Dog [7].”
- A survey of the use of crowdsourcing in software engineering (2017, background): “Jabberwocky [149] is a programming framework for crowd computation.”
- Crowdsourced Data Management: Industry and Academic Perspectives (2015, methodology): “At a higher level of abstraction, toolkits such as CrowdForge [116] and Jabberwocky [22], and Automan [32] help specify crowdsourced workflows.”
- Beyond Mechanical Turk: An Analysis of Paid Crowd Work Platforms (2015, unknown): “…the need to support complex work has led to a flurry of research (Kittur, Khamkar, André, & Kraut, 2012; Kulkarni, Can, & Hartmann, 2012; Ahmad, Battle, Malkani, & Kamvar, 2011; Noronha, Hysen, Zhang, & Gajos, 2011) and open-source toolkits (Little, Chilton, Goldman, & Miller, 2009;…”
- No Workflow Can Ever Be Enough (2017, background): “These toolkits enable programatic description of workflows [2, 44] and decompositions of work into smaller partitions [33, 36].”