Publishing Your Research · Lesson 3 of 5
Data & Code Availability
~10 min
The Concept
A journal's submission checklist asks for your 'data availability statement.' You realize you've never had to write one before, and that the honest answer for a fictional-but-realistic dataset like Bluewater Basin is refreshingly simple.
A data availability statement (a short note saying exactly where to find the data behind a result) tells readers exactly where the data behind a result can be found, a public repository, a request process, or an explanation of why it can't be shared (e.g. private health data). Open data doesn't just serve abstract scientific virtue; it's what actually lets someone check your work.
The Analogy
It is like a restaurant listing where its ingredients come from, instead of just saying 'trust us, it's fresh.' Anyone who wants to can go check the source themselves. That openness is what turns a claim into something verifiable.
Why Real Researchers Care
Many journals and funding agencies now require data and code availability statements as a condition of publication or funding, reflecting a broad shift toward open science over the past fifteen years. Choosing an open license (like this platform's own MIT license) and a stable public repository is now considered baseline practice, not an optional extra.
Quick Check
Q1. What is the main purpose of a data availability statement?
Your Goal
Write a one-sentence data availability statement for your Bluewater Basin capstone project, assuming you'll publish the synthetic dataset alongside your code.
Hint: State where it lives (e.g. a public GitHub repository), under what license, and any format details a reader would need.
Teach It Back
Explain why 'the data is available upon request' is considered a weaker practice than depositing data in a public repository.