What can I do to get the maximum out of the academic papers I read?
June 24, 2010 9:16 AM   Subscribe

What can I do to get the maximum out of the academic papers I read?

I have established a pattern of reading academic papers in my subject (computer science) in the evenings in order to avoid wasting time in front of the TV. Generally, I try and read papers that I think are interesting. This means I read a lot of papers within and outside of my field, based on skimming of abstract and title. The papers range in quality from published conference/journal papers to magazines to unpublished rants put up on individual websites.

Generally once I've read a paper I make notes about it, summarize it and, if it's in my field or immediate area of interest - try and generate three questions or projects from the paper itself.

However, I feel that because my reading is pretty random (e.g. in the last week I read one paper on event processing, one in computer vision, two in data compression and one in operating systems) maybe I should be making a more concerted effort to be a bit more disciplined (or maybe not?).

In this respect, I'm wondering if people who read academic papers regularly are able to give me any further ideas on how I can make this a more productive experience/hobby and what other things I should be doing when I read papers. Especially with regards to being able to later use this information productively.
posted by gadha to Education (10 answers total) 13 users marked this as a favorite
 
In addition to the summarizing/synthesizing that you do, I also try to really pick apart the methods section on the first read, making an effort to predict the limitations and try to consider why there are any discrepancies between my list and the one presented by the authors. I read mostly medicine/public health, so perhaps this is not an issue with compsci. Something a little more applicable to your field that might also address the discipline/focus issue you brought up: skim the citations at the end of the paper and look up anything that strikes your fancy. This helps you learn about related contemporary research and can also direct you to older, influential papers.

But yeah, most of the time I don't get too much further beyond the abstracts.
posted by The White Hat at 9:28 AM on June 24, 2010


Read the abstracts of the papers cited. Rinse, repeat.
posted by An algorithmic dog at 10:10 AM on June 24, 2010


I'm curious where you get papers. Do you have access to electronic journal databases through a university or a library? If so, check out the Science Citation Index. It shows how many times each paper was cited and where, so you can kind of chart the evolution of ideas from one author to the next.

The citation index is part of the ISI Web of Knowledge database, which has been my go-to resource in my research. It makes it easy to find series of related papers while weeding out "insignificant" work. It's also plain old brain fun, the academic equivalent of flitting around wiki pages or tvtropes.com.
posted by Freyja at 10:10 AM on June 24, 2010


I can't address the "how to choose what to read" aspect, but the "how to use this information later" question basically is about making a personal notes-library, and I can tell you how I've handled that, you can see if any of that sounds useful.

What do you do afterwards now? Is this project-related, or just for general interest? Are you keeping/archiving the papers (either in a file cabinet or as pdfs)? If so, how do you organize them, and how are you planning to refer back to them? As you're writing comments, are they in a notebook, in a txt file attached to the pdf, in the (digital or physical) margins, on post-it notes, etc?

What was really useful for me in project-related readings has been keeping a digital bibliography, renaming all the files with a fixed format (example - "Smith2008JCP_spectra", referring to Joe Smith's 2008 article on the spectrum of the molecule I'm looking at, in the Journal of Chemical Physics) Then in the comments section of the properties box, a few-phrase summary of why that article was relevant. "rotational spectrum of Molecule at temps from _ to _K". Then I'd set up the folder properties to display that column, and it's not too hard to skim down. I once tried folders for subcategories but ran into indexing trouble with stuff that had multiple possible locations. Whatever works for you, i'm sure there are tools out there. I also had a physical notebook or sometimes a word file with my notes in it, because I didn't reliably have the ability to make margin-comments on the pdfs, though that's the preferable route for me now.
posted by aimedwander at 10:12 AM on June 24, 2010


I've found that, in my research area at least, the keywords authors choose aren't very consistent. So, whenever I get a new article I replace the keywords the author chose with ones from my list of keywords (I have about 30 keywords that I use). If you're reading in several areas, that might be more difficult. Once I read the paper I also generate a short summary (about 10 lines) of the highlights. That way, when I'm looking for something I can narrow the search down with the keywords I've added, then skim some summaries to find the few papers that I'm looking for. I also keep a list of the keywords that authors are using, so that I can effectively search for new articles based on whatever terminology is in vogue.
posted by periscope at 10:58 AM on June 24, 2010


Use a program like Mendeley to keep an archive of papers tagged with notes. Mendeley also has some social functions that should recommend papers based on what you've already read.
posted by l33tpolicywonk at 11:11 AM on June 24, 2010


Don't read them. I'm serious.

Unless you're in a tiny niche field with only one or two journals, there are a flood of papers out there. You can't possibly read them all. In fact, the only time you really need to be reading complete papers is when you're learning a new field, or are trying to replicate or build upon someone else's work.

The rest of the time you should be doing something like the following. Stop immediately after any step where you realize that the paper is irrelevant to your work or uninteresting:

1) Read the title
2) Read the abstract
3) Check out the figures
4) Skim the text to find the key section you can use.

Each of these steps will get you progressively deeper into the paper.

Only about 10% of the papers make it past step 1.Another 10% of those will get past step 2. Of those, probably half will prove interesting enough that you make it past the figures, and want to see what the result was or how they accomplished something in the methods section. Even then, you shouldn't read the whole damn paper. Find the snippet of information that's key, make a note, file the paper in your library and move on.

I'm not trying to quash serendipity here, but the truth is, your time is valuable and generally, you'd be better off actually working on solving a problem.
posted by chrisamiller at 2:54 PM on June 24, 2010 [3 favorites]


Also, most journals offer RSS feeds. Subscribe to them, and skim them using the above method. Since you'll never read past the title 90% of the time, this is managable. Even better is using a service like CiteULike to store your library. It'll find users who have bookmarked similar papers and start making recommendations to you. These are often very useful.
posted by chrisamiller at 2:56 PM on June 24, 2010


As Sydney Brenner tells it, during the glory days of the Cavendish lab at Cambridge Francis Crick kept a placard above his desk that said READING ROTS THE MIND. Now, I would obviously take this advice with a large grain of salt, but I think the sentiment is essentially correct in that there are often much better ways to spend your time than mucking about with an ever-growing pile of papers. For instance, talking to other researchers helps sort the interesting questions in your field from the boring ones - which is often very hard to do when reading isolated papers that all treat their objects of study as if they were God's gift to humanity. Even more important is rolling up your sleeves and hacking through some problems/experiments of your own.

That said, reading the literature is important, but it should be done efficiently. My own approach varies with my reason for reading the paper. The easiest case is when I'm looking for a specific fact or methodological detail - I find it an move on. For recent papers that are directly related to my work, I read the abstract and use it to predict the experiments and figures that are in the paper. I then check myself, and try to figure out why the authors did things differently than I would have. For keeping up with work outside my field, I do essentially what chrisamiller describes above - triage ruthlessly, stop reading as soon as boredom sets in, and don't get bogged down in the details.
posted by phage! at 8:47 PM on June 24, 2010


I have had tremendous luck trying to track down specific answers for stuff that everyone else takes for granted and stumbling into things I didn't know I needed to know.

For example - in my assay I use a reagent called TMB. What this stuff does is turn blue in the presence of peroxidase and you get your numbers from how blue it's turned. So one day I was looking for the name of the product of the TMB reaction for a report. I went diving in the literature and found a paper written some time in the early 70's that answered my question. But it also hinted at explanations for some other observations, so I start poking around some more. And of course that raises new questions in my mind and pretty soon I tripped over a big pile of serendipity.

An example of this is when I went to check the spelling of serendipity a few seconds ago (Just like it sounds? No way!) and found this: One aspect of Walpole's original definition of serendipity that is often missed in modern discussions of the word is the "sagacity" of being able to link together apparently innocuous facts to come to a valuable conclusion.

So I believe that this is a feature, not a bug (Of course I'm also the guy who posted this AskMe so your mileage may vary.)

Don't read a paper just because trees died for it. Read it because it seems to answer a question you have. It may or may not, but while you're in the neighborhood, it might answer questions you didn't know you had.
posted by Kid Charlemagne at 5:00 AM on June 25, 2010 [1 favorite]


« Older Not so easy as 1-2-3   |   textbook design Newer »
This thread is closed to new comments.