Crossref's July 1 DOI Deadline Is a Journal Operations Story, Not a Technical Footnote

A DOI problem usually reaches leadership late. Not when the deposit is made, but when a library reports a broken route, when citation counts split across duplicate records, or when a platform migration leaves half a backfile pointing to legacy pages nobody is still monitoring. By then, the issue no longer feels technical. It feels like trust leakage.

That is why Crossref’s June reminder about co-access matters beyond the small group directly using it. From July 1, 2026, no new DOIs will be placed into co-access, and existing users are being moved toward multiple resolution before the service is fully deprecated in January 2027. On the surface, that sounds like a narrow infrastructure change. In practice, it reveals which publishers know exactly what their DOI of record is, who owns it, and how versioning, hosting, and discovery are supposed to work once content lives in more than one place.

Circle the Date, Then Look Past It

The immediate operational date is July 1, 2026. Crossref says that after that date, no new co-access DOIs will be created, although metadata for existing co-access book records can still be updated until January 2027. Crossref’s recommended path is multiple resolution: one DOI of record, with readers taken to an interim choice page if the same object is available from more than one source.

That design is cleaner than the old duplicate-DOI pattern. Crossref explicitly notes that multiple resolution supports a single DOI for each item across different hosts, which improves the accuracy of citation counts and usage statistics. That matters more in 2026 than it did a few years ago, because the infrastructure sitting downstream of DOI deposits has become denser and more analytical.

Why This Is Suddenly More Visible

In late May, Crossref reported that its corpus is now connected by more than 2 billion citation links. It also noted that many discovery tools rely on those linked references, and that member-submitted references plus Crossref matching both shape the network that readers and systems see. A month later, Crossref and Knowledge Futures announced a collaboration to test higher-volume, higher-granularity DOI registration for newer publishing and repository use cases.

Taken together, those updates point to a simple conclusion. This is an inference from Crossref’s recent announcements, not a direct quote: DOI management is moving closer to day-to-day publishing operations. The more journals register granular objects, maintain richer links, and publish across multiple surfaces, the less room there is for informal DOI habits.

Three Places Journals Usually Discover They Lack DOI Governance

1. During platform moves

A journal changes hosting vendors, migrates its archive, or rebuilds article pages. Editorially, the move may go well. Operationally, the DOI layer often exposes the gaps. Which landing page is canonical? Who is authorized to update the DOI target? Are old and new hosts both meant to resolve for a period, or should one become an alias? If nobody decided those questions in advance, migration teams improvise under deadline.

2. During multi-host distribution

Books were Crossref’s immediate co-access use case, but the governance lesson applies more broadly. Journals now spread content across publisher sites, society portals, repositories, aggregators, and preservation or mirror environments. When the same article or component object is accessible from several places, readers need a stable DOI story and staff need clear rules for when to register secondary URLs versus separate objects.

3. During record cleanup

Duplicate records can sit quietly for years. Then somebody notices split citations, inconsistent Altmetric tracking, or article pages that still advertise an older DOI on PDFs and metadata tags. Cleanup becomes harder because the problem is historical rather than transactional. Crossref’s migration guidance now requires members to agree on a definitive DOI and alias the others to it. That sounds simple until a publisher realizes it has never documented authority over DOI decisions at title level.

What a Clean Migration Looks Like

• Name a DOI of record for each affected object before anyone touches URLs.
• Map where that DOI currently resolves: article page, PDF, repository copy, aggregator page, or legacy site.
• Decide which additional destinations should exist as secondary URLs and which should disappear.
• Confirm who has the Crossref permissions to unlock DOIs and register secondary URLs.
• Check that the DOI shown on landing pages, PDFs, XML, and indexing feeds all matches the agreed record.
• Test reader journeys after changes, not just deposits.

Crossref’s documentation is unusually concrete here. The primary depositor must enable the DOI for multiple resolution, secondary URLs are usually added through resource-only deposits, and the resolver behavior does not change until those secondary URLs are actually registered. That distinction matters. A team can think it has “prepared” a migration while readers still see the old route because the operational last mile never happened.

This Is Also a Staffing Question

Many journals do not fail on DOI infrastructure because the standards are obscure. They fail because responsibility is fragmented. Editorial offices assume production or platform teams own DOI updates. Production assumes the hosting vendor will catch routing problems. Vendors assume the publisher has made policy decisions about canonical destinations. Nobody is wrong enough to trigger a crisis immediately, but nobody is accountable enough to prevent drift.

That is why a small deadline like July 1 is useful. It forces a concrete audit: where are duplicate records still tolerated, who can authorize a definitive DOI, and what happens when one work needs more than one legitimate destination? Journals that can answer those questions quickly are not just ready for this Crossref transition. They are better prepared for mergers, title transfers, repository mandates, and any future shift toward finer-grained research objects.

Practical Takeaway For Journal Leaders

Before the end of June, ask for one DOI governance sheet for every journal or imprint you operate. It should list the DOI owner, the system of record, who can change targets, how duplicate records are handled, and how platform migrations are tested. If that document does not exist, the risk is not theoretical. Crossref’s July 1 cutoff has simply made it easier to see.