Sponsors make Crossref membership accessible to organizations that would otherwise face barriers to joining us. They also provide support to facilitate participation, which increases the amount and diversity of metadata in the global Research Nexus. This in turn improves discoverability and transparency of scholarship behind the works.
We are looking to work with an individual or organization to perform an audit of, and propose changes to, the structure and information architecture underlying our website, with the aim of making it easier for everyone in our community to navigate the website and find the information they need.
Proposals will be evaluated on a rolling basis. We encourage submissions by May 15, 2025.
At the end of last year, we were excited to announce our renewed commitment to community and the launch of three cross-functional programs to guide and accelerate our work. We introduced this new approach to work towards better cross-team alignment, shared responsibility, improved communication and learning, and make more progress on the things members need.
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.
Our reports are tools to help you evaluate and improve your metadata. The dashboard gives an overview of our ever-growing corpus of metadata. How good is your metadata? Find out using Participation Reports and other reports to evaluate your metadata records, check for any issues, and learn how to resolve them.
We send reports by email from reports@crossref.org to specific contacts on your account. Do add this address to your email contacts list or safe senders list to ensure that you receive them. These reports are intended to help you keep your metadata records up-to-date, and include:
Conflict report - this report shows where two (or more) DOIs have been submitted with the same metadata, indicating that you may have duplicate DOIs. You’ll start receiving conflict reports if you have at least one conflict. These reports are sent out on a monthly basis, or more frequently if your number of conflicts peaks by over 500, and it is sent to the main Technical contact on your account.
DOI error report - a DOI error report is sent immediately when a user informs us that they’ve seen a DOI somewhere which doesn’t resolve to a website, and it is sent to the main Technical contact on your account.
Resolution report - this monthly report shows the number of successful and failed DOI resolutions for the previous month, and it is sent to the Primary contact on your account (please note - this contact used to be known as the Business contact).
Schematron report - the main Technical contact on your account may also receive periodic Schematron reports if there’s a metadata quality issue with your records.
If you aren’t receiving reports, please check the emails aren’t being caught by your spam filter. It might also be because we our contact information for your organization is not current, or you aren’t the designated reports person in our database. Please contact us and we’ll sort it out for you.
If you are not the appropriate person to receive reports, we can send reports to a different email address. If you don’t find our reports useful, please contact us and we’ll see what we can do.
If you need information about something that’s not covered by your reports, please explore all the information you can access through our REST API, or contact us for help.