5 thoughts on “Publish or Perish: the Tool”

  1. Seems cool, but when I tried to use it with a few well-known researchers, it produced a lot of papers that were published by different researchers who happen to have identical or similar names. This makes me doubt the accuracy of the reported statistics.

  2. Yes, that’s one problem. Another problem is that it uses Google Scholar for data, which is biased to what it indexes.

    I have this feeling that librarians of the future will basically be bibliographic data-analysts. Just today I found that one of our databases had indexed many articles several times (i.e. separate entries and differnt journal volumes etc. for the same article), no doubt because of some software error that arose in in the creation of the DB.

  3. Yes, that’s one problem. Another problem is that it uses Google Scholar for data, which is biased to what it indexes.

    What the Web taught us is that recall is far more important than precision.

    The most common problem I have is that I missed a reference. This can cost you months of research time. Google Scholar may be biased (aren’t all libraries biased), but it has excellent coverage.

    At least, it indexes my papers. I bet that if you looked in CISTI’s database, you’d find, at best, half of my papers. Yes. It matters: if you are one of my competitors, and you missed half of what I have done, you are basically flying blind.

  4. Seems cool, but when I tried to use it with a few well-known researchers, it produced a lot of papers that were published by different researchers who happen to have identical or similar names.

    I’ve been using it for about six months. It’s designed to be used in a very interactive and manual way. You’re supposed to iteratively refine your query and also to go through the list of hits and remove the check marks from the ones that don’t belong. It’s not fully automatic, but at least the user interface makes it relatively easy to refine the results.

    P.S.: I’m starting to get good at adding Roman numerals.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax