Blog

 4 minute read.

Linking data and publications

Geoffrey Bilder

Geoffrey Bilder – 2014 September 21

In CollaborationDatacite

Do you want to see if a Crossref DOI (typically assigned to publications) refers to DataCite DOIs (typically assigned to data)? Here you go:

http://0-api.labs.crossref.org.wam.leeds.ac.uk/graph/doi/10.4319/lo.1997.42.1.0001

Conversely, do you want to see if a DataCite DOI refers to Crossref DOIs? Voilà:

http://0-api.labs.crossref.org.wam.leeds.ac.uk/graph/doi/10.1594/pangaea.185321

Background

“How can we effectively integrate data into the scholarly record?” This is the question that has, for the past few years, generated an unprecedented amount of handwringing on the part researchers, librarians, funders and publishers. Indeed, this week I am in Amsterdam to attend the 4th RDA plenary in which this topic will no doubt again garner a lot of deserved attention.

We hope that the small example above will help push the RDAs agenda a little further. Like the recent ODIN project, It illustrates how we can simply combine two existing scholarly infrastructure systems to build important new functionality for integrating research objects into the scholarly literature.

Does it solve all of the problems associated with citing and referring to data? Can the various workgroups at RDA just cancel their data citation sessions and spend the week riding bikes and gorging on croquettes? Of course not. But my guess is that by simply integrating DataCite and Crossref in this way, we can make a giant push in the right direction.

There are certainly going to be differences between traditional citation and data citation. Some even claim that citing data isn’t “as simple as citing traditional literature.” But this is a caricature of traditional citation. If you believe this, go off an peruse the MLA, Chicago, Harvard, NLM and APA citation guides. Then read Anthony Grafton’s, The Footnote? Are you back yet? Good, so let’s continue…

Citation of any sort is a complex issue- full of subtleties, edge-cases exceptions, disciplinary variations and kludges. Historically, the way to deal with these edge-cases has been social, not technical. For traditional literature we have simply evolved and documented citation practices which generally make contextually-appropriate use of the same technical infrastructure (footnotes, endnotes, metadata, etc.). I suspect the same will be true in citing data. The solutions will not be technical, they will mostly be social. Researchers, and publishers will evolve new, contextually appropriate mechanisms to use existing infrastructure deal with the peculiarities of data citation.

Does this mean that we will never have to develop new systems to handle data citation? Possibly But I don’t think we’ll know what those systems are or how they should work until we’ve actually had researchers attempting to use and adapt the tools we have.

Technical background

About five years ago, Crossref and DataCite explored the possibility of exposing linkages between DataCite and Crossref DOIs. Accordingly, we spent some time trying to assemble an example corpus that would illustrate the power of interlinking these identifiers. We encountered a slight problem. We could hardly find any examples. At that time, virtually nobody cited data with DataCite DOIs and, if they did, the Crossref system did not handle them properly. We had to sit back and wait a while.

And now the situation has changed.

This demonstrator harvests DataCite DOIs using their OAI-PMH API and links them in a graph database with Crossref DOIs. We have exposed this functionality on the “labs” (i.e. experimental) version of our REST API as a graph resource. So…

You can get a list of Crossref DOIs that refer to DataCite DOIs as follows:

http://0-api.labs.crossref.org.wam.leeds.ac.uk/graph?rel=cites:*&filter=source:crossref,related-source:datacite

And the converse:

http://0-api.labs.crossref.org.wam.leeds.ac.uk/graph?rel=cites:*&filter=source:datacite,related-source:crossref

Caveats and Weasel Words

  • We have not finished indexing all the links.
  • The API is currently a very early labs project. It is about as reliable as a devolution promise from Westminster.
  • The API is run on a pair of raspberry-pi’s connected to the internet via bluetooth.
  • It is not fast.
  • The representation and the API is under active development.Things will change. Watch the Crossref Labs site for updates on this collaboration with DataCite

See also:

comments powered by Disqus
RSS Feed

Categories

Archives

Last Updated: 2018 June 13 by Geoffrey Bilder
https://0-www-crossref-org.wam.leeds.ac.uk/blog/linking-data-and-publications/
0-www-crossref-org.wam.leeds.ac.uk
crawl=CC-MAIN-2018-26
56570
application/http; msgtype=response
sha1:DL2OANDNERAEHSNQG43O2QRHM767LNHN
<urn:uuid:e87ff7e2-7da5-46db-8006-859005a803d1>
2018-06-18T21:14:53Z
129.11.21.2
text/html
sha1:SODQSNGEZH3DA3GMUTURMSEBXQFWMNZO
<urn:uuid:1b21d483-6888-4605-8d8c-e5299b37f201>
https://0-www-crossref-org.wam.leeds.ac.uk/blog/linking-data-and-publications/
response
<urn:uuid:c9c3a04b-8d18-4ec7-af25-8d7b8cff6bc6>
robots: classic
hostname: ip-10-143-191-145.ec2.internal
software: Nutch 1.6 (CC)
isPartOf: CC-MAIN-2018-26
operator: Common Crawl Admin
description: Wide crawl of the web for June 2018
publisher: Common Crawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf