One size fits all’ never quite works, does it? This is why there are different DOI Registration Agencies to serve the needs of different communities, which are governed by those communities. Crossref and DataCite constitute two of these Registration Agencies, but we overlap more than most in our missions and our communities.
We understand why it might be confusing trying to decide who to join, or whether to join both. We want to help, so that you can get the services that are the best fit for your organization and the type of content you want to register.
Here are some things to think about, to help you decide which organization is the right one for you.
Thinking about how you classify your organization can be helpful; what type of organization/department/initiative/project are you? Do you see your organization as one that sits within a certain community?
Crossref members are organizations who publish content, or register research grants. These include publishers, research institutions, university presses, societies and funders. In order to become a member, register content and deposit metadata and DOIs, you’ll need to meet the criteria set out in our governing by-laws. Membership in Crossref is open to organizations that publish professional and scholarly materials and content. In addition, applicants should be able to meet the terms and conditions of membership.
With DataCite, membership is open to all organisations that share their mission. DataCite’s members work with data centers, stewards, libraries, archives, universities, publishers and research institutes that host repositories and who have responsibility for managing, holding, curating, and archiving data and other research outputs. Members agree with the DataCite statutes. You can see current DataCite members here.
It’s not just about ‘getting a DOI’. Crossref and DataCite have expertise and services that support and enhance the specific needs of our communities and how they work with their content.
Crossref provides services like:
Reference Linking: Reference linking enables researchers to follow a link from the reference list to other full-text documents, helping them to make connections and discover new things.
Cited-by: Cited-by shows how work has been received by the wider community; displaying the number of times it has been cited, and linking to the citing content.
Similarity Check: A service provided by Crossref and powered by iThenticate—Similarity Check provides editors with a user-friendly tool to help detect plagiarism.
DataCite provides services like:
DOI Fabrica: DOI management platform, perfect for manual DOI creation or for human curation of automatically-created DOIs. Register your first DOI in less than a minute.
Link checker: Automatically checks your DOIs to make sure they are still resolving correctly.
Data metrics badge: Embed citation metrics for any DataCite DOI on your own website.
Importantly, both organizations make the metadata you register available via APIs. This metadata is used by thousands of different tools and services. So if you’re registering content with an organization that isn’t the best fit for your content, then you might wonder why it isn’t appearing in specific databases e.g. Google Dataset Search for data, Dimensions for articles. This is why we have specific metadata schemas for different content types, to fit the communities we work with - so that an organization can work with us to get access to all of the data they’re interested in, in a standard format and in one place.
What role do you have in relation to the content being registered?
Do you follow a publishing workflow? I.e. are there editorial processes involved in selecting and stewarding the content e.g. issuing updates like corrections. We know there are lots of definitions of a publisher so it’s hard to be exact, but this might help you think about how you work. If this sounds like you then you should explore joining Crossref.
Or are you depositing content? This could be different types of research outputs using different kinds of platforms, e.g. researchers posting content to an institutional repository. In that case, the DataCite community is a good fit for you.
We’re also working with an increasing number of organizations who have content types that are best served by being members of both organizations, like a publisher who publishes a mix of journal articles and data, or a university that has a publishing program and an institutional repository.
The Center for Open Science (COS) provides a good example of a member who works with both of our organizations to meet the needs of their community:
“We hear from lots of users about how important Digital Object Identifiers (DOIs) are to their work. DOIs ensure persistent links to content and enhance discoverability of one’s research. At the behest of our users, we began issuing DOIs in 2015, first to public registrations, then to public projects in September 2016, and recently to preprints in July 2017. In all, over 22,000 DOIs were registered for content on the OSF. The DOIs issued on the OSF have historically been registered with DataCite, through the California Digital Library’s EZID. Earlier this year, we learned that EZID’s services are evolving, and COS was faced with the choice of a new registration agency for DOIs. This has given us the opportunity to explore how best to support our users and the diverse research outputs they share via OSF. Ultimately, COS decided to pursue registering DOIs with two separate agencies to provide users with services tailored to their needs: registering DOIs for preprints with Crossref and DOIs for projects and registrations with DataCite.”
For identifiers and metadata to work to their full potential, both Crossref and DataCite require that only one identifier be assigned to a research object. Multiple persistent and identifiers for an object reduce the chance of it being identified and discovered, and can split usage, citation information over multiple instances of a work.
If a persistent identifier for an object already exists, you should continue to use that identifier for the content and not reassign another identifier for that object under your own prefix.
We’ve created a diagram to try to help you try to decide who to join, based on the workflow the content you work.
Updated almost 2 years ago