A DOI for the Non-Researcher: Zenodo for operators who ship datasets, reports, and field notes

I run small businesses, not a lab. Pump distribution, a welding workshop, leather work. For years I thought a DOI was a thing journals stamped on articles, something that started around the year 2000 and had nothing to do with me. Then I watched a structural engineer cite a settlement-crack dataset that a contractor had simply uploaded, and the cite kept working two years later when the contractor had moved on. That permanence is the whole point, and almost nobody outside academia uses it.

Here is the part I keep getting wrong, so I will say it first: I sat on operational data for years because publishing it felt like something only researchers were allowed to do. That was just fear wearing a costume. Zenodo accepts a dataset, a methods note, an open-source release, a technical report up to 50 GB per file, and hands back a permanent identifier that Google Scholar and DataCite can find. My own pipeline now forces a Zenodo deposit with a reserved DOI before anything I make is allowed to go to a store.

This book walks the deposit by hand. Picking a license without guessing (CC BY for most things, CC0 when you want zero friction, ODbL for an actual database), wiring GitHub so every release archives itself with a fresh DOI, anonymizing field data so you publish without breaking an NDA, and understanding why a concept DOI and a version DOI are not the same number. A composite open-source maintainer in here went from being thanked in acknowledgements to being formally cited inside eighteen months.

If you have searched for how to get a DOI, how Zenodo works, what ORCID and DataCite actually do, which open repository indexes into Google Scholar, or how a practitioner turns field notes into citable data publishing, this is the deposit walkthrough I wish I had read first. Written from running small businesses in Indonesia, but the deposit mechanics and license decisions work the same in any emerging market or one-person shop.