MétaCan
Menu
Back to cohort

Who are the users? Who are the developers? Webs of users and developers in the development process of a technical standard

2009· article· en· W2149485622 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

VenueInformation Systems Journal · 2009
Typearticle
Languageen
FieldSocial Sciences
TopicInformation Systems Theories and Implementation
Canadian institutionsUniversité du Québec à Montréal
Fundersnot available
KeywordsProcess (computing)Software deploymentComputer scienceOrder (exchange)InformaticsKnowledge managementInformation systemProcess managementEngineeringSoftware engineeringBusiness

Abstract

fetched live from OpenAlex

Abstract The paper presents an empirical study of user involvement in developing a technical standard for a scientific community's information system project. The case illustrates how multiple perspectives are involved when considering the user role in practice. The case presents a situation where both developers and users were pre‐defined in the design and development phases of the standard as homogeneous groups of actors. Groups of actors changed to become more heterogeneous and ‘fluid’ in the deployment and implementation phases, thus forming ‘webs of developers’ and ‘webs of users’. Detailed analysis of the process in its entirety shows the blurredness of boundaries between ‘developer’ and ‘user’ categories and roles, and reveals challenges at social and organizational levels. Three models pertaining to the system development process are presented in order to illuminate differing perspectives on the user and on the development process itself. The paper draws theoretically from information systems, social informatics, and science and technology studies. The research contributes to a deeper, interdisciplinary understanding of ‘the’ user, of multiple roles in systems development, and of dynamic sets of user–developer relations.

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.007
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.078
Threshold uncertainty score0.802

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0070.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.002
Open science0.0010.000
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.025
GPT teacher head0.321
Teacher spread0.296 · 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