# Notes on notes

Shortly after the 24:00 mark in the latest episode of Gabe Weatherhead’s Generational podcast, Gabe’s guest, Walton Jones, starts talking about his system for annotating and summarizing academic papers. If you can listen to that 8- to 10-minute stretch without being inspired to improve your own methods for managing the flood of information in your job, then you’re dead to me.

## Walton’s system

To be sure, Walton’s system is highly tuned to the specifics of his profession. As a scientist, a good portion of his time is spent analyzing and synthesizing the research of others. That research comes to him in the form of PDFs of journal papers. He adds color-coded annotations to the PDFs as he reads them: red for summaries, green for references, yellow for results, and so on. This may sound like nothing more than a digital version of Post-it notes, but Walton has an amazing trick up his sleeve. When he’s done reading a paper, he runs an AppleScript that goes through the PDF and creates a Markdown document with all the paper’s annotations listed by page number and organized according to category (summary, reference, result, etc.). The Markdown is then turned into a new page in a VoodooPad document.

So he has this VoodooPad document with his notes on the papers he’s read, which is nice, but that’s not the end. Each individual note in VoodooPad is linked to the page of the PDF to which it refers. The power of this system is that he can search through his VoodooPad document, which has his notes and therefore uses terminology that come naturally to him while searching, and when he finds what he’s looking for, he can click a link and be taken immediately to the right spot in the right paper. This is so much better than simply searching through abstracts or lists of keywords, all of which are words chosen by others.

But don’t just go by my description, read Walton’s own explanation of his system.

## My system

While I don’t pore over research papers anymore, I do deal with a menagerie of documents—drawings, photographs, videos, test reports, deposition testimony, presentation slides, email trails—that are increasingly in some sort of electronic format. I try to organize this mess by turning everything except the photos and videos into PDFs. Like Walton, I make notes on these documents as I go through them, but I don’t do it the way he does.

My system is based on talking. Long ago, I talked into a voice recorder. Later, I started talking into my iPhone, using Griffin’s iTalk app. With both of these systems, I’d replay the recording to myself and type up the notes, usually cleaning up the sentence structure as I went along. For the past two months, though, I’ve had a much better system: Siri.

Say all the mean things you want about Siri; for me, she’s a great dictation transcriber. The individual notes I make as I read through a document are typically one or two sentences long, which is just about the perfect length for Siri. In Notesy, I tap the microphone button on the keyboard, say my one or two sentences, and tap Done. A few seconds later, the note appears. Unless I’ve hemmed and hawed or there’s a peculiar word, the transcription needs no editing and I move on.

I have a particular format I prefer, with the page number on a line of its own, then the note itself, then a blank line. A typical session would be me saying something like

Fifty-two. New line. A solid or liquid to a change in direction will be as great as a ton per square inch. Period. There are many transformations of motion. Period. New paragraph.

which comes out in Notesy as

Notesy syncs to Dropbox, so the file will be on my Mac when I’m done making notes. The format is not exactly Markdown, but it’s easy to run a global search-and-replace to add a pair of space characters after each page number to provide the line breaks I want in the output. Marked then turns the text file into a PDF.

This is a pretty good system, but what’s missing—and what Walton inspired me to add—are links from my notes to the page numbers in the original documents. Since I keep my summaries in the same directory as the original documents, the links could be added this way in Markdown:

[52](example-report.pdf#page=52)
A solid or liquid to a change in direction will be as
great as a ton per square inch. Period. There are many
transformations of motion.


I’m currently working on a script that’ll do this. It works, but it isn’t especially robust and there’s too much “by hand” work in turning the Markdown into a PDF. I’ll do a complete post when I get those problems solved.

I should mention here that neither Preview (under Lion) nor PDFpenPro handles page number links correctly. Preview opens the original document (sometimes—other times it refuses and says I don’t have permission to open it, which is probably some kind of sandboxing stupidity) but won’t go the linked page number. PDFpenPro doesn’t even get that far; it opens a blank document that it claims in the title bar is original document.

Skim, on the other hand, handles page number links like a boss. This was a little surprising to me, because Walton says in another post that it doesn’t and that he had to write a script to word around that limitation. All I can say is that Skim has worked fine in all my tests so far. I just need to get that script working so I can start using summaries with links.