MétaCan
Menu
Back to cohort
Record W2767320254 · doi:10.17705/1cais.04118

The World IT Project: History, Trials, Tribulations, Lessons, and Recommendations

2017· article· en· W2767320254 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueCommunications of the Association for Information Systems · 2017
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsLakehead University
Fundersnot available
KeywordsContext (archaeology)PoliticsPolitical scienceCorporate governancePublic relationsScale (ratio)SociologyManagementHistoryGeographyLawEconomics

Abstract

fetched live from OpenAlex

We conceived The World IT Project, the largest study of its kind in the IS field, more than a decade ago. This ambitious mega project with an enormous global scale was formally launched in 2013 and is expected to finish by 2017. Major publications on the project should appear through 2019. The project responded to the pervasive bias in IS research towards American and Western views. What IS research glaringly lacks is a global view that tries to understand the major IS issues in the world in the context of unique cultural, economic, political, religious, and societal environments. The World IT Project captures the organizational, technological, and individual issues of IT employees across the world and relates them to cultural and organizational factors. This first major paper provides the project’s objectives and history, its general framework, governance, important decision points, and recommendations for future researchers based on lessons learned. Ultimately, we hope to provide a world view of IT issues that will be relevant to stakeholders at the firm, national, and international levels. We also invite scholars to send their recommendations for analyzing and writing papers using our vast database.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.005
metaresearch head score (Gemma)0.010
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Science and technology studies, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.986
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.010
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0030.000
Scholarly communication0.0010.003
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.264
GPT teacher head0.394
Teacher spread0.130 · 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