MétaCan
Menu
Back to cohort
Record W7163036270 · doi:10.6082/29p2f-pfx35

Is C&RL Ready for a Data Sharing Policy?

2023· article· en· W7163036270 on OpenAlex
Minglu Wang, Adrian K. Ho, Kristen Totleben

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

VenueUniversity of Chicago · 2023
Typearticle
Languageen
FieldComputer Science
TopicResearch Data Management Practices
Canadian institutionsYork University
Fundersnot available
KeywordsEditorial boardData sharingTransparency (behavior)ConversationOrder (exchange)Scholarly communicationAssociate editor

Abstract

fetched live from OpenAlex

In the summer of 2020, C&RL received a request from the ACRL Board of Directors to establish a registered report submission track as a major step to ensure C&RL's high standards of rigorous methods. The request letter was signed by a group of ACRL members, led by Amy Riegelman, who later published an editorial on this topic (Amy Riegelman, 2021), calling C&RL to be more proactive in supporting open research practices. In order to increase C&RL's rigor in supporting and implementing open research practices, it was recognized that both access to research data and transparency of research methods are necessary. From this line of thought, the C&RL Editorial Board, former Editor Wendi Arant Kaspar and Editor Kristen Totleben, have been engaged in an ongoing conversation on the possibility and the journal's capacity to implement a data sharing policy. For the past three years, Editorial Board member Minglu Wang has been researching academic journals' data sharing policies and reaching out to journal editors and editorial board members for consultation. Her efforts culminated in fall 2022 when she, Totleben, and Editorial Board member Adrian Ho conducted a survey (see Appendix) requesting input from colleagues in academic libraries regarding their perceptions of a data sharing policy and what types of data management support they would need or recommend.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesOpen science
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.758
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.009
Open science0.0060.006
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.303
GPT teacher head0.397
Teacher spread0.094 · 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