This year, metadata development is one of our key priorities and we’re making a start with the release of version 5.4.0 of our input schema with some long-awaited changes. This is the first in what will be a series of metadata schema updates.
What is in this update?
Publication typing for citations
This is fairly simple; we’ve added a ‘type’ attribute to the citations members supply. This means you can identify a journal article citation as a journal article, but more importantly, you can identify a dataset, software, blog post, or other citation that may not have an identifier assigned to it. This makes it easier for the many thousands of metadata users to connect these citations to identifiers. We know many publishers, particularly journal publishers, do collect this information already and will consider making this change to deposit citation types with their records.
Every year we release metadata for the full corpus of records registered with us, which can be downloaded for free in a single compressed file. This is one way in which we fulfil our mission to make metadata freely and widely available. By including the metadata of over 165 million research outputs from over 20,000 members worldwide and making them available in a standard format, we streamline access to metadata about scholarly objects such as journal articles, books, conference papers, preprints, research grants, standards, datasets, reports, blogs, and more.
Today, we’re delighted to let you know that Crossref members can now use ROR IDs to identify funders in any place where you currently use Funder IDs in your metadata. Funder IDs remain available, but this change allows publishers, service providers, and funders to streamline workflows and introduce efficiencies by using a single open identifier for both researcher affiliations and funding organizations.
As you probably know, the Research Organization Registry (ROR) is a global, community-led, carefully curated registry of open persistent identifiers for research organisations, including funding organisations. It’s a joint initiative led by the California Digital Library, Datacite and Crossref launched in 2019 that fulfills the long-standing need for an open organisation identifier.
We began our Global Equitable Membership (GEM) Program to provide greater membership equitability and accessibility to organizations in the world’s least economically advantaged countries. Eligibility for the program is based on a member’s country; our list of countries is predominantly based on the International Development Association (IDA). Eligible members pay no membership or content registration fees. The list undergoes periodic reviews, as countries may be added or removed over time as economic situations change.
For most metadata elements, you can just update the record to delete elements. However, if you are sending us XML, there are some non-bibliographic metadata elements where you have to go through a two-stage process - firstly send us a submission to delete this element, and then send us a further submission to add in the replacement data.
Metadata that needs to be explicitly deleted includes:
You can also delete non-bibliographic metadata by supplying an empty parent element (see examples below), and include it in a metadata update or submit it as a resource-only deposit. Note that metadata submitted as part of a Crossmark update needs to be removed within Crossmark metadata (see examples below).
Remove all Crossmark data
Remove allCrossmark data from a record by supplying an empty Crossmark element in a metadata deposit:
Remove funding, clinical trial, or license data from Crossmark
Funding, license, and clinical trial data may all be supplied as part of a Crossmark update. If you need to remove funding, license, or clinical trial metadata from your Crossmark metadata, you must submit the appropriate empty element within a Crossmark update. Note the other Crossmark metadata must be present as well to be retained.
In this example, funding data is removed from a Crossmark update:
Remove text and data mining, Similarity Check, and multiple resolution URLs
Text and data mining and multiple resolution secondary URLs may be removed from a record by submitting an update containing an empty collection tag that includes the appropriate property:
Text and data mining uses property text-mining
Similarity Check URLs use the property crawler-based
Multiple resolution secondary URLs use the property list-based