These are textbook examples of the presentation of data in ways that encourage bad habits.
This might look like a data frame, but the individual columns have no meaning and the rows are not a unit of observation.
… and so on. Make it a habit to show a unique identifier which facilities tracking back mistakes and joining with other data.
A data frame with a single variable should still be represented as a table. Among other things, this makes it easier to read in the data with software.
There are two header rows and so the time columns can’t be referenced in the usual way.
Also, it’s hard to read in these data.
No column names
These data are actual organized by columns, but notice how the column names are shown inline, e.g. with \(\sigma = 5\).
We all know what the authors are trying to do here, but they have formatted the presentation the same way as data. That’s the basic mistake. But taking that mistake as an intention to display data, a proper presentation should be
- n: sample size
- xbar: sample mean
- s: sample standard deviation
- background: the color of ….
Where the data came from, perhaps even where the original data are stored.
Omitting the codebook is practically universal in intro textbooks. Sometimes, there is a narration explaining the data, but this is not identified as a separate file as it should be to form good habits.
There should be a reference to the meta-data for a table. Some possibilities:
- A link to a text/PDF/etc file
- A package::dataset name in R.
- A print-out of a file, making it clear that it’s a presentation of a separate file, not part of the data file.
- If you’re using spreadsheets to hold data tables and you want there to be only one link, put the metadata in a separate tab from the data. (But remember, “tabs” are not a database concept.)
Use a consistent format for missing data.
NA is standard and works well with graphics and statistics software.
List the many ways in which this “table” violates the conventions for effective data organization.
- The rows should be turned into columns.
- There are no variable names
- If we stipulate that “temperature” is a variable name, the units (deg F) should be included in the metadata, not the variable name.
- Time should be a variable and it should be stored in a machine-readable format. The very simplest uses numbers (e.g. 8.00) but others are available depending on the software.