Thank you to everyone who responded with feedback on the Op Cit proposal. This post clarifies, defends, and amends the original proposal in light of the responses that have been sent. We have endeavoured to respond to every point that was raised, either here or in the document comments themselves.
We strongly prefer for this to be developed in collaboration with CLOCKSS, LOCKSS, and/or Portico, i.e. through established preservation services that already have existing arrangements in place, are properly funded, and understand the problem space.
I’m pleased to share the 2023 board election slate. Crossref’s Nominating Committee received 87 submissions from members worldwide to fill seven open board seats.
We maintain a balance of eight large member seats and eight small member seats. A member’s size is determined based on the membership fee tier they pay. We look at how our total revenue is generated across the membership tiers and split it down the middle. Like last year, about half of our revenue came from members in the tiers $0 - $1,650, and the other half came from members in tiers $3,900 - $50,000.
https://doi.org/10.13003/c23rw1d9
Crossref acquires Retraction Watch data and opens it for the scientific community Agreement to combine and publicly distribute data about tens of thousands of retracted research papers, and grow the service together
12th September 2023 —– The Center for Scientific Integrity, the organisation behind the Retraction Watch blog and database, and Crossref, the global infrastructure underpinning research communications, both not-for-profits, announced today that the Retraction Watch database has been acquired by Crossref and made a public resource.
Today, we are announcing a long-term plan to deprecate the Open Funder Registry. For some time, we have understood that there is significant overlap between the Funder Registry and the Research Organization Registry (ROR), and funders and publishers have been asking us whether they should use Funder IDs or ROR IDs to identify funders. It has therefore become clear that merging the two registries will make workflows more efficient and less confusing for all concerned.
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 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. 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.
Registering grant metadata
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.
Formatting grant metadata for direct deposit
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.
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
