MétaCan
Menu
Back to cohort
Record W3213980078 · doi:10.7191/jeslib.2021.1220

Data Management for Systematic Reviews: Guidance is Needed

2021· article· en· W3213980078 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

VenueJournal of eScience Librarianship · 2021
Typearticle
Languageen
FieldDecision Sciences
TopicMeta-analysis and systematic reviews
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsSystematic reviewTransparency (behavior)Best practiceData management planComputer scienceData managementData sharingProtocol (science)Plan (archaeology)Process (computing)Process managementKnowledge managementData extractionData scienceManagement scienceEngineeringMEDLINEData miningMedicinePolitical science

Abstract

fetched live from OpenAlex

Data management practices for systematic reviews and other types of knowledge syntheses are variable, with some reviews following open science practices and others with poor reporting practices leading to lack of transparency or reproducibility. Reporting standards have improved the level of detail being shared in published reviews, and also encourage more open sharing of data from various stages of the review process. Similar to project planning or completion of an ethics application, systematic review teams should create a data management plan alongside creation of their study protocol. This commentary provides a brief description of a Data Management Plan Template created specifically for systematic reviews. It also describes the companion LibGuide which was created to provide more detailed examples, and to serve as a living document for updates and new guidance. The creation of the template was funded by the Portage Network.

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.212
metaresearch head score (Gemma)0.105
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Scholarly communication, Open science, Insufficient payload (model declined to judge)
Consensus categoriesMetaresearch
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.110
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.2120.105
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0050.002
Bibliometrics0.0000.003
Science and technology studies0.0000.000
Scholarly communication0.0030.003
Open science0.0090.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0030.001

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.898
GPT teacher head0.557
Teacher spread0.341 · 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