MétaCan
Menu
Back to cohort
Record W3029726963 · doi:10.1111/csp2.220

Identifying research needs to inform white‐nose syndrome management decisions

2020· article· en· W3029726963 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

VenueConservation Science and Practice · 2020
Typearticle
Languageen
FieldAgricultural and Biological Sciences
TopicBat Biology and Ecology Studies
Canadian institutionsUniversity of WinnipegUniversity of Prince Edward Island
FundersSouth Central Climate Adaptation Science CenterU.S. Fish and Wildlife Service
KeywordsContext (archaeology)WildlifeEnvironmental resource managementBusinessKnowledge managementRisk analysis (engineering)Data scienceEcologyComputer scienceGeographyBiology

Abstract

fetched live from OpenAlex

Abstract Ecological understanding of host–pathogen dynamics is the basis for managing wildlife diseases. Since 2008, federal, state, and provincial agencies and tribal and private organizations have collaborated on bat and white‐nose syndrome (WNS) surveillance and monitoring, research, and management programs. Accordingly, scientists and managers have learned a lot about the hosts, pathogen, and dynamics of WNS. However, effective mitigation measures to combat WNS remain elusive. Host–pathogen systems are complex, and identifying ecological research priorities to improve management, choosing among various actions, and deciding when to implement those actions can be challenging. Through a cross‐disciplinary approach, a group of diverse subject matter experts created an influence diagram used to identify uncertainties and prioritize research needs for WNS management. Critical knowledge gaps were identified, particularly with respect to how WNS dynamics and impacts may differ among bat species. We highlight critical uncertainties and identify targets for WNS research. This tool can be used to maximize the likelihood of achieving bat conservation goals within the context and limitations of specific real‐world scenarios.

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.004
metaresearch head score (Gemma)0.007
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.409
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.007
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.003
Science and technology studies0.0020.000
Scholarly communication0.0000.001
Open science0.0000.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.338
GPT teacher head0.412
Teacher spread0.074 · 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