MétaCan
Menu
Back to cohort
Record W4410982158 · doi:10.1080/0194262x.2025.2512475

Knowledge Synthesis in Engineering: A Practical Guide to Contextualizing Different Review Methodologies

2025· article· en· W4410982158 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueScience & Technology Libraries · 2025
Typearticle
Languageen
FieldEngineering
TopicBiomedical and Engineering Education
Canadian institutionsUniversity of OttawaUniversity of British ColumbiaUniversity of Waterloo
Fundersnot available
KeywordsComputer scienceData scienceLibrary scienceManagement scienceEngineering

Abstract

fetched live from OpenAlex

There is a rapidly increasing amount of scientific information being produced daily, and researchers have acknowledged the significant issues with being able to stay on top of new and emerging research. Literature reviews serve several purposes to combat this: 1) to synthesize research, 2) to critically evaluate it and 3) to provide recommendations. Evidence based systematic searching was initially developed in the medical field, grounded in the knowledge that while there was an importance to having an expert opinion, the best medical advice was based on the accumulation of results from multiple experiments. Engineering has long been borrowing from the review methodology, but this has been happening on a one-off basis, with little to no formal structure to the adaptations. Working with a cross disciplinary team of engineering and health librarians, at institutions across Canada, this paper seeks to contextualize knowledge synthesis for non-health librarians, provide fundamental information on engineering and health databases for reproducible searching, their capabilities and limitations, and open a conversation around working toward a rigorous new methodology applicable in cross disciplinary engineering contexts.

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.006
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: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.791
Threshold uncertainty score0.714

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.006
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.004
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.038
GPT teacher head0.350
Teacher spread0.312 · 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