Field note
What does one record represent?
The population or universe statement tells readers what one row represents, which entities or events are included, and important exclusions or skip conditions.
Begin at dataset level
Write one plain sentence saying what a single record represents, then add which entities or events are included and which are deliberately left out. The sample says one record represents one observed tree within the fictional Northbank survey boundary. Without that sentence, a reader counting rows cannot tell whether they are counting things or observations of things.
Refine at field level
Individual fields often have a narrower universe than the dataset. A question asked only of certain respondents, or a measurement taken only where the team could physically reach, applies to a subset, and saying so stops a reader treating its blanks as data-quality failures instead of out-of-universe rows. Record the skip condition in the folio's universe alongside the missing-value meanings.
Avoid unsupported completeness claims
A universe statement says what you intended to cover. It is not evidence that coverage was achieved, that the records are representative, or that nothing is absent, and the studio checks none of those. Write what the collection was designed to include and let the reader judge, rather than implying completeness the data cannot support.
Worked example from the sample project
The sample's population statement is one sentence: one record represents one observed tree within the fictional Northbank survey boundary. It does most of the interpretive work in the whole project. Without it, a reader counting rows does not know whether they are counting trees, observations, or trees that happened to be reachable on the days the team walked.
Field-level universes refine it. A field only collected for trees the team could physically approach has a narrower universe than the dataset, and saying so is what stops somebody treating its blanks as data-quality failures rather than as out-of-universe rows.
What this does not do
- The studio cannot verify coverage, completeness or representativeness of any dataset.
- A population statement is an authored claim, not a sampling guarantee.
- It does not detect rows that fall outside the universe you described.
Do this in the studio
Write what one row is before you write anything about a column.
- Open the Dataset context station and state the population in one plain sentence.
- Add the collection period and any known exclusions.
- Narrow the universe at field level wherever a field was not collected for every row.
Open the studio at the Dataset context station