This month marks one year since the Dutch Research Council (NWO) introduced grant IDs—an important milestone in our journey toward more transparent and trackable research funding. We created over 1,600 Crossref Grant IDs with associated metadata. We are beginning to see them appear in publications. These early examples show the enormous potential Grant IDs have. They also highlight that publishers could extend their efforts to improve the quality of funding metadata of publications.
eLife recently won a Crossref Metadata Award for the completeness of its metadata, showing itself as the clear leader among our medium-sized members. In this post, the eLife team answers our questions about how and why they produce such high-quality open metadata. For eLife, the work of creating and sharing excellent metadata aligns with their mission to foster open science and supports their preprint-centred publication model, but it also lays the groundwork for all kinds of exciting potential uses.
TLDR: We’ve successfully moved the main Crossref systems to the cloud! We’ve more to do, with several bugs identified and fixed, and a few still ongoing. However, it’s a step in the right direction and a significant milestone, as, whilst it is a much larger financial investment, it addresses several risks and limitations and shores up the Crossref infrastructure for the future.
Following up on his earlier post (which was also blogged to CrossTech here), Leigh Dodds is now [Following up on his earlier post (which was also blogged to CrossTech here), Leigh Dodds is now]3 the possibility of using machine-readable auto-discovery type links for DOIs of the form
These LINK tags are placed in the document HEAD section and could be used by crawlers and agents to recognize the work represented by the current document. This sounds like a great idea and we’d like to hear feedback on it.
Concurrently at Nature we have also been considering how best to mark up in a machine-readable way DOIs appearing within a document page BODY. Current thinking is to do something along the following lines:
which allows the DOI to be presented in the preferred Crossref citation format (doi:10.1038/nprot.2007.43), to be hyperlinked to the handle proxy server (<a href="http://dx.doi.org.ezproxy.csu.edu.au/10.1038/nprot.2007.43">http://dx.doi.org.ezproxy.csu.edu.au/10.1038/nprot.2007.43</a>), and to refer to a validly registered URI form for the DOI (info:doi/10.1038/nprot.2007.43). Again, we would be real interested to hear any opinions on this proposal for inline DOI markup as well as on Leigh’s proposal for document-level DOI markup.
(Oh, and btw many congrats to Leigh on his recent promotion to CTO, Ingenta.)