In our previous instalments of the blog series about matching (see part 1 and part 2), we explained what metadata matching is, why it is important and described its basic terminology. In this entry, we will discuss a few common beliefs about metadata matching that are often encountered when interacting with users, developers, integrators, and other stakeholders. Spoiler alert: we are calling them myths because these beliefs are not true! Read on to learn why.
We’ve just released an update to our participation report, which provides a view for our members into how they are each working towards best practices in open metadata. Prompted by some of the signatories and organizers of the Barcelona Declaration, which Crossref supports, and with the help of our friends at CWTS Leiden, we have fast-tracked the work to include an updated set of metadata best practices in participation reports for our members.
It’s been a while, here’s a metadata update and request for feedback In Spring 2023 we sent out a survey to our community with a goal of assessing what our priorities for metadata development should be - what projects are our community ready to support? Where is the greatest need? What are the roadblocks?
The intention was to help prioritize our metadata development work. There’s a lot we want to do, a lot our community needs from us, but we really want to make sure we’re focusing on the projects that will have the most immediate impact for now.
In the first half of this year we’ve been talking to our community about post-publication changes and Crossmark. When a piece of research is published it isn’t the end of the journey—it is read, reused, and sometimes modified. That’s why we run Crossmark, as a way to provide notifications of important changes to research made after publication. Readers can see if the research they are looking at has updates by clicking the Crossmark logo.
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://0-doi-org.libus.csd.mu.edu/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
