Quality metadata is foundational to the research nexus and all Crossref services. When inaccuracies creep in, these create problems that get compounded down the line. No wonder that reports of metadata errors from authors, members, and other metadata users are some of the most common messages we receive into the technical support team (we encourage you to continue to report these metadata errors).
We make members’ metadata openly available via our APIs, which means people and machines can incorporate it into their research tools and services - thus, we all want it to be accurate.
The other day I was out and about and got into a conversation with someone who asked me about my doctoral work in English literature. I’ve had the same conversation many times: I tell someone (only if they ask!) that my dissertation was a history of the villanelle, and then they cheerfully admit that they don’t know what a villanelle is, and then I ask them if they’re familiar with Dylan Thomas’s poem “Do not go gentle into that good night.
Having joined the Crossref team merely a week previously, the mid-year community update on June 14th was a fantastic opportunity to learn about the Research Nexus vision. We explored its building blocks and practical implementation steps within our reach, and within our imagination of the future.
Read on (or watch the recording) for a whistlestop tour of everything – from what on Earth is Research Nexus, through to how it’s taking shape at Crossref, to how you are involved, and finally – to what concerns the community surrounding the vision and how we’re going to address that.
TL;DR A year ago, we announced that we were putting the “R” back in R&D. That was when Rachael Lammey joined the R&D team as the Head of Strategic Initiatives.
And now, with Rachael assuming the role of Product Director, I’m delighted to announce that Dominika Tkaczyk has agreed to take over Rachael’s role as the Head of Strategic Initiatives. Of course, you might already know her.
We will also immediately start recruiting for a new Principal R&D Developer to work with Esha and Dominika on the R&D team.
A DOI may refer to a journal or book (a title-level DOI), or to a specific article or chapter.
Journals and DOIs
Like a set of nesting dolls, a journal may be made up of volumes, each containing a number of issues, each containing a number of articles. You can assign a DOI at each level, for example:
journal-level-DOI (sometimes called the title-level-DOI) 10.5555/QYPF2031. Like an ISSN, it refers to the whole journal
volume-level-DOI 10.5555/FFFU4804
issue-level-DOI 10.5555/QKLE5634
article-level-DOI 10.5555/CNBT7653
The role of the journal-level-DOI, volume-level-DOI, and issue-level-DOI is to link persistently to a point in the journal structure. These DOIs do not have any associated content, and it does not cost anything to register these DOIs.
However, article-level-DOIs do have associated content, and therefore a fee applies to register these DOIs.
Books and DOIs
Like a set of nesting dolls, a book may be made up of chapters. Again, you can assign a DOI at each level, for example:
book-level-DOI (sometimes called the title-level-DOI) 10.5555/ZAAR1365. Just like an ISBN, it refers to the whole book.
chapter-level-DOI 10.5555/TFWD2627
Both book-level-DOIs and chapter-level-DOIs have associated content, and therefore a fee applies to register these DOIs.
