A Pan-Canadian Comparison of Cyanobacteria Bloom Management Policies, Programs, and Practices
Bibliographic record
Abstract
Across the globe, reports of cyanobacteria blooms are on the rise. The increasing occurrence of cyanobacteria blooms and cyanotoxins is attributed to phosphorous (P) loading, climate change, among a mix of other factors. While eutrophic lakes have a higher risk of blooms, oligotrophic and mesotrophic lakes are also experiencing blooms. This means governments need to develop a robust cyanobacteria management strategy (prevent, control, and mitigate) to protect public health. In Canada, water management is a shared responsibility among the federal, provincial, and local governments; however, cyanobacteria management is mainly a provincial and local government responsibility. This research compares and contrasts five provincial cyanobacteria management strategies from Alberta, Manitoba, Nova Scotia, Ontario, and Saskatchewan. Using a policy analysis framework, the methods of data collection include a review of grey and academic literature, legislation/regulations, and interviews with actors involved in cyanobacteria bloom management in each province. Also, three case studies Lake Erie, Ontario; Lake Winnipeg, Manitoba; and Pigeon Lake, Alberta were selected to analyze the policies and programs in practice. A robust cyanobacteria management strategy involves prevention, control, and mitigation to avoid public health risks. All jurisdictions in Canada have initiatives to manage cyanobacteria blooms. Nutrient management continues to be the cornerstone of bloom prevention by controlling point and diffuse sources of P runoff control. Nutrient management mostly relies on voluntary participation, so reductions in nutrient loading are heavily dependent on financial incentives, and education and outreach programs; however, there is little to no understanding or tracking of implementation. Also, P control will not reduce the risk of blooms in low P lakes. Monitoring programs and targets should include dissolved oxygen. Public health risks associated with cyanotoxins are mitigated through public reporting or monitoring drinking water sources and recreational waters. The monitoring and reporting programs vary by province. For instance, certain drinking water sources and recreational waterbodies are routinely monitored, whereas in other provinces sampling is driven by public reporting.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.009 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.006 | 0.017 |
| Science and technology studies | 0.006 | 0.001 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".