Make it easier for the reader to follow extracts used repeatedly.

Should we reorganize Ch4 to only include the calculation of indicators, but save the graphics for Chapter 5? This would isolate some differences between Stata & R.

Because many figures need to be rotated for full page display, let's save all figures as pngs and read with knitr::include_graphics.

We should be careful not to say "missing" when describing the value . in Stata. The term "missing" is already used in a value label for survey responses that are not NIU, but are otherwise "missing".

In R, these values appear as NA. In Stata, is it appropriate to say "blank"?

Currently, roman numerals begin on the cover page. It would be better if the began with the TOC.

Every chapter should have a list of included:

• samples
• cases
• variables
• R packages

Can IPUMS issue a DOI?

Major revisions should be noted inline in the guide (e.g. when Phase 3 data are released by IPUMS PMA).

Minor revisions (e.g. typos) can probably just be noted in a commit message.

Makes sure that all relative URLs (e.g. ../2022-03-01-phase2-discovery/#sampling) are removed or replaced with absolute URLs.

Is 17 required? Any other packages?

In-line variables names currently link to the IPUMS PMA documentation only on first-mention, then they switch to code.

Separately, IPUMS Stata variables are always lower-case, while IPUMS R variables are always upper-case.

I've written an R function that will automatically build the URL for a provided variable (corrected by stripping any numeric suffix), and show it in lower case. To implement: find and replace bare variable names with the function call.

Let's promote as many of these as possible to an aside - this is particularly important with the Stata version, where words that are also function-names are colorized incorrectly (seems like a real pain to deal with this otherwise, and the colorization is a nice feature otherwise)

I'm using 20% "PMA Pink" (#98579B20) for chunk output background, but no color for chunk input. This is because asides sometimes align with chunk input (if explaining code) and we don't want them to overlap.

Hope this is ok? Could also consider a v-bar on the left (we do this on the blog after all).

Dale suggested a few that looks helpful - should they go at the front or the back?

• Availability of data from pmadata.org
• Suggested citation
• Acknowledgements
• Abbreviations
• Glossary of Terms

The citation function we use for References on the blog isn't implemented by Pagedown. Look into a solution for this (should be NBD: there are only 3-5 citations throughout)