Those of you who are regular readers of Ars' science content are probably aware of our use of Digital Object Identifiers, or DOIs, which act as online reference information, taking readers directly to the papers being discussed. Readers almost never comment about that feature, except when it fails, in which case we invariably hear about it—and it fails at least once a month. We've tried explaining both our reasons for using them and the reasons they break in the forums, and have recently linked to Ed Yong's excellent discussion of the system and its problems. Within a week, we were dealing with complaints due to a broken DOI. So, this is an attempt to provide a comprehensive description of the DOI system, why we use it, and why it doesn't always work smoothly.
Referencing, effort, and reward
For most of our readership, reading an Ars science article is the beginning and end of their exposure to a topic. But we also have a notable population of scientists who read, and they may find themselves interested in reading the academic paper that led to our coverage. There are any number of good reasons for doing that: the paper may be relevant to their work, they may want details we did not provide in our coverage, they suspect we might have gotten something wrong and want to correct us, etc. As a result, some form of reference to the paper is a definite good—it's a benefit for some of our readership, and may help correct errors that are read by the rest of our audience.
Traditionally, academic references have been handled with text that identifies (at a minimum) the journal, authors, and time of publication. There are several problems with using this. For starters (as anyone who can remember the pre-PubMed days knows), it's error prone. Since it's a lot of work to get right, it would add significantly to the workload of our authors, who already go well beyond the call of duty when it comes to effort. It also adds to the effort involved in navigating to the appropriate issue of the journal and finding the paper, so it doesn't serve our readership.