MétaCan
Menu
Back to cohort
Record W4391437750 · doi:10.1080/10439463.2024.2311921

The importance of context: re-examining the ‘deployments’ of SWAT teams in Canada

2024· article· en· W4391437750 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.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenuePolicing & Society · 2024
Typearticle
Languageen
FieldSocial Sciences
TopicPolicing Practices and Perceptions
Canadian institutionsCarleton University
FundersSocial Sciences and Humanities Research Council of Canada
KeywordsContext (archaeology)Public relationsSociologyPolitical sciencePublic administrationGeographyArchaeology

Abstract

fetched live from OpenAlex

Based on an analysis of data released through Freedom of Information (FOI) requests, Canadian researchers have suggested that Special Weapons and Tactics (SWAT) teams are no longer exclusively deployed to resolve high-risk incidents but now frequently respond to routine calls that do not necessitate their involvement. Given concerns about these conclusions, we submitted the same FOI requests to the 14 police agencies examined by Roziere and Walby [2020. Special weapons and tactics teams in Canadian policing: legal, institutional, and economic dimensions. Policing and society, 30 (6), 704–719] and worked with the FOI analyst from each agency to ensure that the data were being interpreted correctly. Based on our re-analysis of the FOI-released data, we report on two problems with the conclusions reached by Roziere and Walby: the conflation of incidents where any SWAT officer responds to calls with full SWAT team deployments and the masking of potential risk factors in calls when relying on call type categories. Our findings illustrate the value of police agencies disclosing relevant contextual information to researchers when possible and they reinforce the necessity of collaborating with FOI analysts to better understand the data being released.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.120
Threshold uncertainty score0.335

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.046
GPT teacher head0.350
Teacher spread0.304 · 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