<ol>
<li>Take 100 papers.</li>
<li>Sort by number of citations.</li>
<li>Take top 50.</li>
<li>Go to the list references at the end of each paper. Make a <code>big list</code> using all those references. </li>
<li>Sort by number of times some paper appears in the <code>big list</code>.</li>
<li>Choose top 15 papers.</li>
<li>Read. Read. Read. Read one more time. And just once more. </li>
<li>And now you will be able to tell papers you should read from those you shouldn't without much effort. </li>
</ol>

CC BY-SA 2.5
2011-03-31T17:40:52.970Z
... and now I am tempted to write a script that does till 6.
Tathagata
CC BY-SA 2.5
2011-03-31T17:49:21.510Z
Try tex.SE they might have it ready. And if you do enough of 7 you can write script to do 8. I suspect some people on this site actually have such a step 8 script.
Pratik Deoghare
CC BY-SA 2.5
2011-03-31T17:37:04.763Z
2011-03-31T17:37:04.763Z
Pratik Deoghare
<p>I can't comment on the answer of <a href="https://cstheory.stackexchange.com/users/612/machinecharmer">MachineCharmer</a>. Citations have a bias to older papers. You can't learn the state of the art by those.</p>

<p>I would start by some recent prestigious conferences/journals (FOCS, STOC, or whatever is relevant) and I would try to find relevant papers. It also helps to take a look at the most recent papers of researchers in this area.</p>

<p>Choose one paper that is relevant. Print it. Take your pencil and go to an isolated environment. Start reading by noting everything that you think it's important. During the discussion of the subject, you will encounter references which explain some theorems/previous work/ideas/etc. Go back to the references section and note why this reference seems useful. When you have read the initial paper, make a list of what's next and why. Repeat as necessary.</p>

<p>That's what I do as a student. Most likely, a professor could also ask some of his/her colleagues (or here) in order to find an initial point.</p>

CC BY-SA 3.0
2011-04-24T18:32:30.683Z
2011-04-24T18:32:30.683Z
2017-04-13T12:32:28.080Z
Dimitris Leventeas
<ol>
<li>If possible, find a survey, book, or a lecture note. This will help a lot to see the jungle through the trees! To find books, Google Books is your friend. Search the keywords in the Google Books, and try to find a relevant book on the subject.</li>
<li>Take the top-down / bottom-up approach, and alternate. That is, read the most recent papers first (the top research), and references thereof (bottom). Why? Because the top research is likely to be better, and has probably surveyed bottom works and improved them. However, to understand top, it is usually the case that you need to skim the bottom works. <strong>Important:</strong> Don't get stuck at the bottom. After reviewing older works, take the bottom-up approach. Finally, alternate between the top-down and bottom-up approaches.</li>
<li>Don't read a paper unless you are somehow sure that it is really relevant. The relevancy depends on several factors: The amount of citations, the fame of authors, the conference/journal it is published in, and so on. </li>
<li>Be sure to read the title and abstract carefully, and skim the sections. Decide if you should ever read this paper now, and to what extent.</li>
<li>If a paper has a conference version and a journal (full) version, select the first one. The conference version usually gives the general idea, and avoids cumbersome proofs. Read the full version only when you really need to learn the proof details/technique.</li>
</ol>

<p><strong>Edit 1:</strong> Some of my colleagues use reference manager tools like <strong>Zotero</strong> to help them organize their references. I'm not acquainted with such tools, but I think you should give it a go.</p>

CC BY-SA 2.5
2011-03-31T17:35:34.467Z
2011-03-31T17:40:41.873Z
2011-03-31T17:40:41.873Z
Sadeq Dousti
<p>DISCLAIMER: This is an open ended question and stackexchange puritans would probably feel an extraordinary urge to vote it down to oblivion. However, I cannot think of any other forum more appropriate and promising for getting answer to this question.</p>

<p>While working on a research problem for course project I realize that if I model my problem in a particular way I could use techniques from a specialized track [for the recent case - <a href="http://www.nist.gov/tac/2011/RTE/">PASCAL Recognizing Textual Entailment Challenge</a>]. After the initial joy, I'm generally puzzled by the numerous papers with all of them silently shouting "Read me, else you'll miss the best way to solve the problem!". How does one learn to filter which paper to read and which one to discard in the face of deadline? Anything other than sort_by_citation count? </p>

CC BY-SA 2.5
2011-04-01T02:08:33.280Z
This is indeed a broad question, but I like it, and the answers I see so far are very interesting!  Thanks for asking that.
Michaël Cadilhac
CC BY-SA 2.5
2011-04-01T02:21:20.003Z
Yes, both the answers are brilliant ... and it was a hard decision problem to select one.
Tathagata
CC BY-SA 2.5
2011-04-01T22:29:52.240Z
It's a very nice question. I think you should wait some time to accept an answer. I also find the accepted answer brilliant, but you can give others the chance to think about your question and post also a good answer. In particular there are a lot of individual approaches to select a paper. If there is some interest, we can make a new community wiki question about this topic.
Marc Bury
CC BY-SA 2.5
2011-04-02T02:19:28.677Z
@Marc Gillé I felt I should wait for other answers, but @Sadeq Dousti answer was superb. But his point 3 is where people like me get trapped. That is where @MachineCharmer-s algorithm would help newbies without experience. There are many articles on how to read a paper, but there are hardly any that says how to select a paper - I am absolutely up for making it community wiki question.
Tathagata
<soft-question><advice-request>
Selecting papers to read
Tathagata
# Selecting papers to read

(Asked by: username_0 on 2011-03-31)

DISCLAIMER: This is an open ended question and stackexchange puritans would probably feel an extraordinary urge to vote it down to oblivion. However, I cannot think of any other forum more appropriate and promising for getting answer to this question.

While working on a research problem for course project I realize that if I model my problem in a particular way I could use techniques from a specialized track [for the recent case - [PASCAL Recognizing Textual Entailment Challenge](http://www.nist.gov/tac/2011/RTE/)]. After the initial joy, I'm generally puzzled by the numerous papers with all of them silently shouting "Read me, else you'll miss the best way to solve the problem!". How does one learn to filter which paper to read and which one to discard in the face of deadline? Anything other than sort\_by\_citation count?

**Tags:** soft-question, advice-request
> **Comments:**
> **username_1**: This is indeed a broad question, but I like it, and the answers I see so far are very interesting!  Thanks for asking that.  
> **username_0**: Yes, both the answers are brilliant ... and it was a hard decision problem to select one.  
> **username_2**: It's a very nice question. I think you should wait some time to accept an answer. I also find the accepted answer brilliant, but you can give others the chance to think about your question and post also a good answer. In particular there are a lot of individual approaches to select a paper. If there is some interest, we can make a new community wiki question about this topic.  
> **username_0**: @Marc Gillé I felt I should wait for other answers, but @Sadeq Dousti answer was superb. But his point 3 is where people like me get trapped. That is where @MachineCharmer-s algorithm would help newbies without experience. There are many articles on how to read a paper, but there are hardly any that says how to select a paper - I am absolutely up for making it community wiki question.  

---

## 3 answers

### Answer by username_5 on 2011-03-31. Score: 21 | Accepted answer

1. If possible, find a survey, book, or a lecture note. This will help a lot to see the jungle through the trees! To find books, Google Books is your friend. Search the keywords in the Google Books, and try to find a relevant book on the subject.
2. Take the top-down / bottom-up approach, and alternate. That is, read the most recent papers first (the top research), and references thereof (bottom). Why? Because the top research is likely to be better, and has probably surveyed bottom works and improved them. However, to understand top, it is usually the case that you need to skim the bottom works. **Important:** Don't get stuck at the bottom. After reviewing older works, take the bottom-up approach. Finally, alternate between the top-down and bottom-up approaches.
3. Don't read a paper unless you are somehow sure that it is really relevant. The relevancy depends on several factors: The amount of citations, the fame of authors, the conference/journal it is published in, and so on.
4. Be sure to read the title and abstract carefully, and skim the sections. Decide if you should ever read this paper now, and to what extent.
5. If a paper has a conference version and a journal (full) version, select the first one. The conference version usually gives the general idea, and avoids cumbersome proofs. Read the full version only when you really need to learn the proof details/technique.

**Edit 1:** Some of my colleagues use reference manager tools like **Zotero** to help them organize their references. I'm not acquainted with such tools, but I think you should give it a go.


---

### Answer by username_3 on 2011-03-31. Score: 6

1. Take 100 papers.
2. Sort by number of citations.
3. Take top 50.
4. Go to the list references at the end of each paper. Make a `big list` using all those references.
5. Sort by number of times some paper appears in the `big list`.
6. Choose top 15 papers.
7. Read. Read. Read. Read one more time. And just once more.
8. And now you will be able to tell papers you should read from those you shouldn't without much effort.

> **Comments:**
> **username_0**: ... and now I am tempted to write a script that does till 6.  
> **username_3**: Try tex.SE they might have it ready. And if you do enough of 7 you can write script to do 8. I suspect some people on this site actually have such a step 8 script.  

---

### Answer by username_4 on 2011-04-24. Score: 4

I can't comment on the answer of [MachineCharmer](https://cstheory.stackexchange.com/users/612/machinecharmer). Citations have a bias to older papers. You can't learn the state of the art by those.

I would start by some recent prestigious conferences/journals (FOCS, STOC, or whatever is relevant) and I would try to find relevant papers. It also helps to take a look at the most recent papers of researchers in this area.

Choose one paper that is relevant. Print it. Take your pencil and go to an isolated environment. Start reading by noting everything that you think it's important. During the discussion of the subject, you will encounter references which explain some theorems/previous work/ideas/etc. Go back to the references section and note why this reference seems useful. When you have read the initial paper, make a list of what's next and why. Repeat as necessary.

That's what I do as a student. Most likely, a professor could also ask some of his/her colleagues (or here) in order to find an initial point.


---

