TL;DR We missed an error that led to resource resolution URLs of some 500,000+ records to be incorrectly updated. We have reverted the incorrect resolution URLs affected by this problem. And, we’re putting in place checks and changes in our processes to ensure this does not happen again.
How we got here Our technical support team was contacted in late June by Wiley about updating resolution URLs for their content. It’s a common request of our technical support team, one meant to make the URL update process more efficient, but this was a particularly large request.
Crossref Conversations is an audio blog we’re trying out that will cover various topics important to our community. This conversation is between colleagues Anna Tolwinska and Rosa Morais Clark, discussing how we can make research happen faster, with fewer hurdles, and how Crossref can help. Our members have been asking us how Crossref can support open science, and we have a few insights to share. So we invite you to have a listen.
We’ve just added to our input schema the ability to include affiliation information using ROR identifiers. Members who register content using XML can now include ROR IDs, and we’ll add the capability to our manual content registration form, participation reports, and metadata retrieval APIs in the near future. And we are inviting members to a Crossref/ROR webinar on 29th September at 3pm UTC.
The background We’ve been working on the Research Organization Registry (ROR) as a community initiative for the last few years.
We’re excited (and a little nervous) to launch a new research project designed to assess the effects of metadata on research communications. We’re expecting this effort to be a significant contribution to the existing research on the topic and we’re really looking forward to getting started. We’re also a little nervous because of course we don’t know what the conclusions will be (after all, if we did, we wouldn’t be starting this project).
Funders are joining Crossref to register their grants so that they can more easily and accurately track the outputs connected to the research they support.
Once you’re a member, registering grants with us means giving us information about each awarded grant, including a DOI which uniquely and persistently identifies each record. At the moment just direct XML deposit methods is supported but we’re working on a manual form to deposit and update grant metadata. This section focuses on grants, but you can also register other content types such as reports, data, and working papers.
Something to consider before you begin
Decide which grants to register first, as you get into the swing of things. For example, pilot a particular country, or area of support. It’s better to start with newly-awarded grants, and then move on to older or long-running awards - these are cheaper to register, and are more likely to have produced research papers, so they’re great for demonstrating the full potential of connected research metadata.
Constructing your identifiers (DOIs)
A DOI is made up of a DOI resolver, a prefix, and a suffix. When you join Crossref as a member, we give you a DOI prefix. You combine this with a suffix of your choice to create a DOI. Although some funders choose to use their internal grant identifier as the DOI suffix, we advise you to make your suffix opaque, meaning that it does not encode or describe any information about the work. Your DOI becomes active once it is successfully registered with us.
Grant landing pages
Your grant metadata records should link to a landing page where you can find information about the grant. Examples: https://doi.org/10.37717/220020589, https://doi.org/10.35802/107769. Should a grant move to a new landing page, the URL in the grant’s metadata is updated to point to the new location. There’s no charge to update metadata for existing deposits.
Formatting grant metadata for registration
Grants can be registered for all sorts of support provided to a research group or individual, such as awards, use of facilities, sponsorship, training, or salary awards.
Here’s the section of our schema for grant metadata. If you’re working with a third-party system, such as Proposal Central or EuroPMC, they may be able to help with this piece of work.
You may be able to map your own data and identifiers to our schema. See our example deposit file - this is a full example, and many of the fields it contains are optional, but we encourage you to provide as much information as you can. Rich metadata helps maximum reuse of the grant records you register with Crossref. This .xsd file helps explain what goes into each field, and the parameters (length, format) of what is accepted in each field. Here’s a less techy version.
When you’ve created your XML files, use our checker to test them - this will show any potential errors with your files. For help with resolving problems, send your XML file and the error message to Support.
Uploading your files to Crossref
Once you’re happy with your files, upload them to us using the admin tool, or submit them through HTTPS POST.
Once your submission is successful, your grant DOIs are ‘live’ and ready to be used. It’s good practice to add the grant DOI to the landing page for the grant, as in this example for https://doi.org/10.37717/220020589:
Spread the word about your grant identifiers
Let your grant submission systems, awardees, and other parties know you are supporting Crossref grant identifiers, and that they should start collecting these identifiers too. Crossref grant metadata (including grant DOIs) is made openly available through our APIs, so it can be used by third parties (including publishers, grant tracking systems) to link grants to related research outputs.
Page owner: Rachael Lammey | Last updated 2020-April-08