MétaCan
Menu
Back to cohort
Record W2044032580 · doi:10.1145/2487294.2487332

Determinants of success in crowdsourcing software development

2013· article· en· W2044032580 on OpenAlexaff
Hamed Tajedin, Dorit Nevo

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicOpen Source Software Innovations
Canadian institutionsYork University
Fundersnot available
KeywordsCrowdsourcingCrowdsourcing software developmentDigitizationPopularityData scienceComputer scienceSoftwareSoftware developmentKnowledge managementKey (lock)Process (computing)Work (physics)ConflationFocus (optics)Software development processWorld Wide WebEngineeringPolitical scienceComputer security

Abstract

fetched live from OpenAlex

With the advent of digitization, recent years have witnessed a surge toward collective undertaking of production process different from traditional ways of organizing. In this vein, crowdsourcing has lent itself into a successful emerging mode of organizing and firms are increasingly using it in their value creation activities. However, despite popularity in practice, crowdsourcing has received little attention from IS scholars. Specifically, what the determinants of success in this model are remains an unexplored area of research that we strive to address in this paper. We focus on software development via crowdsourcing and drawing on studies from IS success, OSS and software development, we build a model of success that has three determinants: the characteristics of the project, the composition of the crowd and the relationship among key players. Finally, we describe our research methodology and conclude with potential contributions of our work.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.010
metaresearch head score (Gemma)0.069
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.015
Threshold uncertainty score0.053

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0100.069
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0030.003
Science and technology studies0.0030.004
Scholarly communication0.0050.002
Open science0.0010.004
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0060.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.015
GPT teacher head0.256
Teacher spread0.241 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations29
Published2013
Admission routes1
Has abstractyes

Explore more

Same topicOpen Source Software InnovationsFrench-language works237,207