In December 2026, we plan to publish new Crossref Member Practices which will set out the standards we expect all Crossref members to meet. From August to October 2026 we are consulting with our members on a draft of these Member Practices. This blog provides the background to this, and explains how you can share your views.
The Crossref community in India is as diverse as the region that it represents, comprising 1605 members, 11 sponsoring organisations, and 5 ambassadors, who between them cover the length and breadth of this country. Between November 2025 and March 2026, we organised three webinars focused on supporting this community with best metadata and publishing practices. We collaborated with the Directory of Open Access Journals (DOAJ) and the Committee on Publication Ethics (COPE) to embed understanding of metadata’s role in the greater context of publishing integrity.
PID strategies are being written around the world right now, and the decisions being made will shape the scholarly record for decades. After 25 years running open scholarly infrastructure—now on behalf of 25,000 members in 167 countries—Crossref has an informed perspective on what those decisions should ideally rest on. Today we’re setting it out in our first position paper: Persistent identifiers in research infrastructure policy: the need for a holistic approach. You can read it online or download the PDF; it’s a 16-minute read.
Research is rarely limited to a single contributor performing a single role. Behind every research output are people contributing in various ways: software development, data analyses, methodology design, and much more. Often, the same person contributes in several of these ways. Until now, Crossref metadata could only capture part of that picture, but this is changing with Schema 5.5.
A Schematron report tells you if there’s a metadata quality issue with your records.
Schematron is a pattern-based XML validation language. We try to stop the deposit of metadata with obvious issues, but we can’t catch everything because publication practices are so varied. For example, most family names in our database that end with jr are the result of a publisher including a suffix (Jr) in a family name, but there are of course surnames ending with ‘jr’.
We do a weekly post-registration metadata quality check on all journal, book, and conference proceedings submissions, and record the results in the schematron report. If we spot a problem we’ll alert your technical contact via email. Any identified errors may affect overall metadata quality and negatively affect queries for your content. Errors are aggregated and sent out weekly via email in the schematron report.
What should I do with my schematron report?
The report contains links (organized by title) to .xml files containing error details. The XML files can be downloaded and processed programmatically, or viewed in a web browser: