MétaCan
Menu
Back to cohort
Record W2393243661 · doi:10.5931/djim.v12i1.6450

Librarians and Computer Programming: Understanding the role of programming within the profession of librarianship

2016· article· en· W2393243661 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueDalhousie Journal of Interdisciplinary Management · 2016
Typearticle
Languageen
FieldComputer Science
TopicOpen Source Software Innovations
Canadian institutionsnot available
Fundersnot available
KeywordsContext (archaeology)Code (set theory)Computer scienceSoftwareWorld Wide WebSource codeComputer programmingLibrary scienceSoftware developmentSociologyProgramming language

Abstract

fetched live from OpenAlex

Computer programming is increasingly being discussed as a practice within librarianship. However, contemporary discussions about the role of code within librarianship often suggest that librarians should or should not learn code while failing to qualify how and why librarians are employing code in a professional capacity rather than IT professionals. By investigating case studies that describe librarians writing code, this paper qualifies popular discussions of code and librarianship with how and why programming is being used in practice by librarians. While these case studies reveal that programming solutions were developed in the context of lack of IT staff, librarians are not taking over roles or projects traditionally afforded to software and web developers, instead librarians are writing code for data processing and web services as extensions of their normal responsibilities. Further discussion explores software engineering as the primary concern of librarians who code professionally.

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.002
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: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.894
Threshold uncertainty score0.361

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0020.003
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.022
GPT teacher head0.264
Teacher spread0.242 · 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