Zoonotic spillover risk mapping for Bangladesh
Combine livestock density, land-use change, and reported human case data to build a district-level spillover risk surface. Deliverable: a reproducible R/Python pipeline plus a mapped risk index.
Every BORA project is chosen on one test: can a motivated student with a laptop produce a defensible, publishable result from open data? If yes, it is a BORA project.
Combine livestock density, land-use change, and reported human case data to build a district-level spillover risk surface. Deliverable: a reproducible R/Python pipeline plus a mapped risk index.
Reconstruct a past outbreak using human, veterinary, and environmental records together, and document where the three sectors failed to share signal in time.
Fit time-series models to open national case data, quantify seasonality, and test whether reported surges exceed expected baselines.
Estimate the effective reproduction number across waves and districts, with explicit treatment of reporting delay and under-ascertainment.
Pull South Asian isolate genomes from public repositories, run standardised assembly and AMR-gene detection, and compare resistance profiles by host and source.
Map resistance-gene carriage from farm to market to clinic using existing published sequence data, and identify where the strongest overlap sits.
Reanalyse published transcriptomic datasets with modern pipelines and test whether the original conclusions hold.
Compare regional isolate genomes against global references to locate lineage-specific variation.
Quantify reported livestock disease burden by district and correlate it with production loss estimates.
Reconcile national production statistics against export records to size the unexplained gap.
Pooled prevalence and resistance estimates for Bangladesh-specific questions with no current synthesis.
Bring a question. If it runs on open data and survives moderator review, it becomes a cohort project. Pitch it →
A mentor or student writes a one-page scope: question, dataset, method, expected output.
A moderator checks feasibility, ethics, and whether the data genuinely exists and is open.
A team of 4–5 students is assigned under a core mentor, with tasks split explicitly.
Code to GitHub, manuscript to a preprint server or journal, entry to the BORA archive.