Over the past year, I’ve been experimenting with different ways to take notes on what I read (mainly books, research papers, and academic articles). While doing my coursework, my reading strategy was haphazard and very course-dependent. Sometimes, I would take notes in-line. Other times, I would write them down on post-its or loosely organized sheets. This worked well enough for individual projects… but it is unruly as a long-term collection of notes.
Since my preliminary exams, I’ve been using a dedicated reading journal, which I highly recommend (all the pictures I use in this post come from that reading journal).
At the beginning of my book is an Index, which lists the books or articles that I have reading, and the page I begin my notes for that book or set of articles.
Since last month, I’ve started using the book log strategy from the Bullet Journal site. I’m a fan of bullet journaling in general, and the original bullet journal method is great for those looking for a planner/to-do list/organization system (you can learn about the bullet journal rapid logging system here, and I highly recommend the 5-minute video tutorial here).
This system is originally made for books, but you can also use this system for journal articles you read in class or for a project.
What makes the book log system unique?
Chapter Index: Reading notes begin with a chapter index. This is usually the table of contents for a book. If I were reading articles for a class or research project, I would list all the articles here. I was somewhat irked with the time it took to write down all the chapters, but it has been absolutely worth it when I come back to old notes.
“Treading”: When I take notes and want to point to a specific part of the book, I write the page, paragraph, and line number down. (This is not quite the same as bullet journal threading, but it has a similar principle). As the blog post recommends, you can use a “^” arrow to indicate “same as previous” (like an “ibid.”).
Different bullets: Like rapid logging, the book log system several different “bullets” to indicate different types of notes and tasks. The ones they recommend are dashes for regular notes (this is the most common bullet for me), a quote for quotes, and a dot for tasks.
- dashes
“ quotes
tasks
I added two (well, three) more to this list:
= for combining ideas
? for questions (I haven’t used this, but I imagine it would be useful in class or guided reading)
o I use an open circle for incomplete tasks. I fill it in when the task is complete*
(* the only tasks I really have in my book log, however, is to add to my zettelkasten.)
These six “bullets” collectively constitute my key.
How do I use this system?
I begin by writing out my chapter index. Though the book log system recommends writing the chapter in as you read it, I actually wrote down all the chapters I was interested in at the beginning. When I take notes for a chapter, I write the first page of those notes on the far right.
Underneath the chapter index, I will have space to write some main points from the book. This typically includes a “purpose statement”: one sentence about why the author wrote the book or what the author hopes to accomplish with the book.
When I read a chapter, I write “CHAPTER #” and then take notes below that. I do my threading on the far right of the page (at the minimum, I usually write the page number). All my threads are highlighted so I can find them easily.
What if I’m reading a couple of articles?
I haven’t used this method as much for reading articles, but I imagine it would still be useful. I did read a set of articles about North Korea, and I found it was useful to read related pieces in 4-5 article batches. In this case, I treated each article as a “chapter.” I wrote an article index, with the “key points” section beneath. Like chapters, some articles are more or less useful than others. I also use the citation shorthand (AUTHOR, DATE) instead of the chapter number. I thread similarly, but I add a column number (page, column/paragraph, line).
For seminars, I would recommend treating each class session as a batch.
What do I take notes on?
Before I started using the book log system, but after I started taking notes in a book, I was asked to do a presentation on organizing your notes. One student had asked me “how do you know what to take notes on, instead of writing everything down?”
At the time, I gave a very lackluster answer: I followed my gut. I’ve been frustrated with that response ever since, which got me thinking about my note-taking process. And, of course, when I think, I read. Andrew Abbott’s book Digital Papers had a great chapter on Reading (Chapter 7). He describes several “modes of reading”: (1) narrative reading, (2) meditative reading, (3) scan reading, (4) mastery of argument reading, (5) party mastery readings.
This typology is great for thinking about what information you want to extract from reading—and what notes you want to take. I use my book log for meditative reading and when I am trying to understand (or “master”) the core argument of someone’s book or article. For this reason, having a “purpose” or “key points” section below my chapter index is really useful, and keeps my focus on the goal (comprehension).
In books, the first few chapters tend to be the most theory-laden, with the subsequent chapters or parts focusing on proof (either statistical, qualitative, case-based, or some combination thereof). I spend a lot of time on these earlier chapters and tend to write the most notes for them.
Going beyond the book
One of the things I’ve struggled with the most is how I translate notes in my book into a broader collection of “ideas” between multiple books. One of the ways that I do so is my combination bullet (=), which I use if what I’m reading reminds me of another author. These notes help me connect multiple authors or concepts in-the-moment; in other words, it’s great short-term.
For the long-term, I rely on my zettelkasten, which I’m hoping to talk about in my next blog post.