Codebookery

Field note

Which questions do these notes answer?

Every published note about profiling a dataset, writing field documentation, recording missing-value and allowed-value semantics, reviewing with real readers, freezing editions, and handing a dictionary on. The index below links all of them.

Every published note

Policy and product pages

Every published note

The notes below cover the whole workflow: reading structure from a file, writing definitions readers can act on, recording what missing values and allowed codes mean, testing comprehension with a real reader, freezing editions, and handing a dictionary on. Each answers one question and links to the station in the studio where that work is done. Together they are the reasoning behind the product rather than a feature list.

Policy and product pages

The policy pages are kept separate because they answer different questions: what the studio does not do, where project content is stored, what the local-first boundary covers, the accessibility position, the terms, the licence, and how to reach support. Each fact is stated once, in the page that owns it, rather than repeated across the notes.

Where to start

If you are new, read the complete workflow first, then follow the end to end worked example, which runs the whole studio on the fictional Northbank tree survey and hands you the file it was built from. After that, read the note for whichever part of your own dataset is hardest, which is usually missing values or allowed codes.