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.
Learn more about conflicts and the conflict report. Conflicts are usually flagged upon deposit, but sometimes this doesn’t happen, creating a missed conflict.
A missed conflict may occur for several reasons:
Two DOIs are deposited for the same item, but the metadata is slightly different (DOI A deposited with an online publication date of 2011, DOI B deposited with a print publication date of 1972)
DOIs were deposited with a unique item number. Before 2008, DOIs containing unique item numbers (supplied in the <publisher_item> element) were not checked for conflicts.
The missed conflict report compares article titles across data for a specified journal or journals. To retrieve a missed conflict report for a title:
The missed conflict interface will pop up in a second window. Enter your email address in the appropriate field. Multiple title IDs can be included in a single request if needed
A report will be emailed to the email address you provided. This report lists all DOIs with identical article titles that have not been flagged as conflicts.
Page owner: Isaac Farley | Last updated 2024-July-22
icon at the far right of the title