MétaCan
Menu
Back to cohort
Record W1611144994 · doi:10.5703/1288284316658

Developing a Weighted Collection Development Allocation Formula

2018· article· en· W1611144994 on OpenAlexaff
Jeff Bailey, Linda Creibaum, Star Holloway

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSpreadsheets and End-User Computing
Canadian institutionsPurdue Pharma (Canada)
Fundersnot available
KeywordsCollection developmentComputer scienceFactor (programming language)Production (economics)Process (computing)Data collectionInstitutionDevelopment (topology)Operations researchSubject (documents)Engineering managementLibrary scienceMathematicsStatisticsEngineeringProgramming languageEconomicsSociology

Abstract

fetched live from OpenAlex

In this preconference workshop Bailey, Creibaum, and Holloway presented detailed instructions on how to create a spreadsheet-based library collection development allocation formula, one option to manage a library’s collection development budget. The presenters demonstrated and led participants through the process of creating customizable Excel-based formulas that can easily be modified to utilize the criteria relevant to a specific library and institution. The primary element in the success of such a formula is the use of weights applied to each factor contained in the spreadsheet. Potential factors include the number of students graduating from each degree program, total faculty per department, departmental credit hour production, the number of courses offered, and the average costs of books and journals in a discipline. By carefully assigning weights to each factor, the output of the formula results in an equitable allocation of funds to each subject area.

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.040
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.011
Threshold uncertainty score0.051

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0100.040
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0050.005
Science and technology studies0.0010.001
Scholarly communication0.0030.005
Open science0.0020.002
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0110.003

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.031
GPT teacher head0.264
Teacher spread0.232 · 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 designNot applicable
Domainnot available
GenreMethods

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

Citations0
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicSpreadsheets and End-User ComputingFrench-language works237,207