This page has links to configuration files, R packages, templates, and a few other things that might be of use to people who want to write (and give talks about) well-formatted social science papers using plain text tools.
Available either as booklet or as a website. As a beginning graduate student in the social sciences, what sort of software should you use to do your work? More importantly, what principles should guide your choices? This article offers some answers. The short version is: you should use tools that give you more control over the process of data analysis and writing. I recommend you write prose and code using a good text editor; analyze quantitative data with R or Stata; minimize error by storing your work in a simple format (plain text is best), and make a habit of documenting what you've done. For data analysis, consider using a format like Rmarkdown and tools like Knitr to make your work more easily reproducible for your future self. Use Pandoc to turn your plain-text documents into PDF, HTML, or Word files to share with others. Keep your projects in a version control system. Back everything up regularly. Make your computer work for you by automating as many of these steps as you can. To help you get started, I briefly discuss a drop-in set of useful defaults to get started with Emacs (a powerful, free text-editor), though I emphasize that there are many other alternatives. I share some templates and style files that can get you quickly from plain text to various output formats. And I point to several alternatives, because no humane person should recommend Emacs without presenting some other options as well.
The gssr package provides the complete General Social Survey cumulative data file (1972-2018) and Three Wave Panel data files in an R-friendly format, together with their codebooks.
The nycdogs package is a fun dataset (actually three separate tibbles: licenses, bites, and zip codes) taken from New York City's Open Data initiative, cleaned up and packaged for R. It's useful for teaching dplyr, for drawing maps, and for seeing where dogs with particular names live.
The uscenpops package contains a table of birth counts for the United States by year-of-age and sex for every year from 1900 to 2018.
The covdata package contains data on COVID-19 from a variety of sources including cross-national data from the ECDC; U.S. state-level data from the CDC and the New York Times; patient-level data from the CDC; excess mortality data from the Human Mortality Database; and mobility data from Apple.
The covmobility package is a companion to covdata and contains COVID-related mobility data released by Apple and Google.
Some Pandoc templates meant to go in
~/.pandoc/templates. Point to them directly from the command line, use them with what's provided in
latex-custom-kjh, or use them as part of a Markdown or RMarkdown workflow.
A collection of LaTeX style files, templates, and org-mode documents providing some nice layouts for typesetting articles using pdfLaTeX or XeLaTeX. They make a pipeline that, for example, lets you begin with an
.org file in Emacs (as set up in the Starter Kit), and go from there to a nice, fully-processed PDF in one step. Or the pieces can be used separately
to set up a
.tex file with a nice Article layout. However, these days I almost never write anything directly in LaTeX. Instead, these templates form part of a pipeline that stars with a Markdown or RMarkdown file and ends up as a HTML, Word, or PDF document.
Now deprecated! This is a much-changed fork of Eric Schulte's Emacs Starter Kit (itself an offshoot of Phil Hagelberg's original) with additional tools included for social scientists, mostly related to writing books or papers in LaTeX and analyzing quantitative data using ESS and R. The goal of the starter kit was to provide a drop-in configuration for Emacs that made it easier to use right from the get-go. However, I no longer use it myself, or maintain it. I don't particularly recommend that anyone just starting out in the social sciences actively choose Emacs these days as their one and only text editor. There are many alternatives and the most important thing, in general, is that you get used to using a good text editor and then just learn the hell out of it. I do continue to use Emacs myself for many things, but that is mostly because I've been using it for decades now. I still kind of hate it, frankly. In late 2021 I began using Doom Emacs rather than the starter kit as the basis for my Emacs configuration. Doom Emacs (with the Vim stuff turned off, in my case) does a great job of managing a bunch of things that the Starter Kit also sets up. If you want to get into Emacs I'd recommend you use that instead, rather than the kit here. So the kit is now retired and will soon be removed from this page and its GitHub repo will probably go away as well. Caveat emptor.
This site is produced using Hugo, a very fast static site generator, which you can read more about here. I've written about my own experience setting it up, too, though the discussion there is now quite old. If you want to look under the bonnet, the code for the entire site is on GitHub, along with a fork of the theme the site uses. Fair warning: if you just want to set up a website with your research interests, contact information, and links to your publications, then there are many simpler and more straightforward options you should seriously consider instead.
Data Visualization: A Practical Introduction is published by Princeton University Press. It introduces you to both the ideas and the methods of data visualization in a clear, sensible, and reproducible way, using R and ggplot2. It is accompanied by an R package containing supporting materials for teaching and learning, including a variety of datasets, convenience functions, and an R Studio project file containing all the code for each of the book's chapters.
This is a short talk, originally given in my Departmental Proseminar, on the topic of giving presentations. I discuss how to think about your talk in general (and how to distinguish it from the paper you're taking about, on the one hand, and the slides you're showing people, on the other.) I then say some things about how to use slides to best get your point across.
Every few months I get an email asking to see the LaTeX markup that I use to generate my Curriculum Vitae. So, here it is. Feel free to adapt it yourself. If you make stylistic modifications, I encourage you to fork the project on GitHub and make them available to others in the same way.
Here is a full list of the various public code and data repositories that I have put on GitHub. They range from the configuration and templating tools listed above to data visualization exercises and other bits of data analysis, mostly written in R.