When each line of code is written it is surrounded by a sea of context: who in the community this is for, what problem we’re trying to solve, what technical assumptions we’re making, what we already tried but didn’t work, how much coffee we’ve had today. All of these have an effect on the software we write.
By the time the next person looks at that code, some of that context will have evaporated.
It turns out that one of the things that is really difficult at Crossref is checking whether a set of Crossref credentials has permission to act on a specific DOI prefix. This is the result of many legacy systems storing various mappings in various different software components, from our Content System through to our CRM. To this end, I wrote a basic application, credcheck, that will allow you to test a Crossref credential against an API.
Subject classifications have been available via the REST API for many years but have not been complete or reliable from the start and will soon be deprecated.
The subject metadata element was born out of a Labs experiment intended to enrich the metadata returned via Crossref Metadata Search with All Subject Journal Classification codes from Scopus. This feature was developed when the REST API was still fairly new, and we now recognize that the initial implementation worked its way into the service prematurely.
Crossref and DOAJ share the aim to encourage the dissemination and use of scholarly research using online technologies and to work with and through regional and international networks, partners, and user communities for the achievement of their aims to build local institutional capacity and sustainability. Both organisations agreed to work together in 2021 in a variety of ways, but primarily to ‘encourage the dissemination and use of scholarly research using online technologies, and regional and international networks, partners and communities, helping to build local institutional capacity and sustainability around the world.
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. You can use the grant registration form or direct XML deposit methods to deposit and update grant metadata. This section focuses on grants, but research funders can also register other record types such as reports, data, and working papers.
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.
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. Read more about constructing your DOIs.
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.
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.
Registering grant metadata using the grant registration form ``
You can use the grant registration form to register grants, with no prior knowledge of XML. You fill out the form and the XML is created for you in the background. You enter your account credentials and the metadata is submitted directly.
If you’d prefer to work directly with XML, 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.
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:
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: Isaac Farley | Last updated 2020-April-08