MétaCan
Menu
Back to cohort
Record W2069768043 · doi:10.1177/0967010614543582

Iterations of Olympic security: Montreal and Vancouver

2014· article· en· W2069768043 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

VenueSecurity Dialogue · 2014
Typearticle
Languageen
FieldSocial Sciences
TopicPolicing Practices and Perceptions
Canadian institutionsUniversity of AlbertaUniversity of Waterloo
Fundersnot available
KeywordsPeacetimeTerrorismContext (archaeology)Security studiesInternational securityPolitical scienceEvent (particle physics)Computer securityPublic administrationLawGeographyComputer science

Abstract

fetched live from OpenAlex

Abstract This article compares security dynamics at two Olympic Games hosted by Canada: Montreal (1976) and Vancouver (2010). It is the first study of security at the Montreal Olympics and was only made possible after four years of requests under the Access to Information Act that resulted in the release of thousands of classified security documents in French and English. A comparative study of the two largest peacetime security operations in Canadian history offers unique insights into the challenges of hosting a major international gathering in the aftermath of an international terrorist incident: the 1972 Munich massacre and the 11 September 2001 attack on the World Trade Center. The comparison further offers an opportunity to chart the continuities and differences in Olympic security over time. We focus in part on how the historical context of each event informed ‘imaginaries of disaster’. We also examine continuities in the official security response, such as the emphasis on advance intelligence gathering, security ‘mock-ups’, manpower allocation, coalitions of security agencies and technological innovation. We conclude with some considerations on security legacies and the importance of major event security as a subject of comparative inquiry.

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.000
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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.695
Threshold uncertainty score0.871

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.017
GPT teacher head0.302
Teacher spread0.285 · 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