A better way to browse DBLP: Faceted DBLP

Scientists are silly sometimes. For example, there is no standard way to figure out what a given researcher has published, nor to find out which papers appeared at a given conference and a given year. DBLP is one tool that tries to solve this problem for Computer Science. It is far from perfect, but its coverage is sometimes considered good enough.

For better or for worse, the reviewers of my last grant applications skipped my carefully crafted c.v. and jumped right into my DBLP publication list. (Remind me to no longer submit publication lists with my grant proposals and just write “see DBLP”.) I must admit that I routinely use DBLP to quickly determine what are the research interests of a given individual, or to find interesting conferences or journals.

One limitation of the DBLP is that its search engine is just not very powerful. Things are improving thanks to Faceted DBLP. The search function itself is not more powerful, but you get aggregated statistics on individuals and conferences. Want to know whether a given conference grows in number of papers presented per year? Want to know the most prolific author at a given conference over the years? These queries are now trivial.

Try it out now!

Published by

Daniel Lemire

A computer science professor at the University of Quebec (TELUQ).

2 thoughts on “A better way to browse DBLP: Faceted DBLP”

  1. Thanks for that post, Daniel. Good bibliographic databases that span publishers and disciplines shouldn’t be as hard to get at as they are. And we shouldn’t be relying on services like BPLP – Libraries should be offering this service! I expect they can’t – or can’t make them public anyway – because of intellectual property rights from publishers….. Sigh.

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