TheDropTimes: If Knowledge Belongs to Everyone, Why Does It Cost So Much?
If Knowledge Belongs to Everyone, Why Does It Cost So Much?
Editor's Pick | Vol. 4 | Issue. 44
Opening access is only the first step. Sustaining the people, institutions and infrastructure that keep knowledge available is the greater challenge.
Behind every published research paper lies years of work, often supported by public funding. Yet the institutions producing that knowledge do not necessarily control how it reaches the world. New research released by SPARC on 14 October, ahead of International Open Access Week, estimates that more than 95% of investment in a typical research article occurs before publisher submission, based on its accounting model. A companion study found operating margins of 24% to 38% among major academic publishers in 2025. The figures raise an uncomfortable question: who should benefit from knowledge that society has largely paid to create?
Removing paywalls is important, but it does not automatically make scholarly publishing fair or sustainable. Some open-access models shift costs from readers to researchers through publication fees, potentially excluding scholars with fewer resources. Alternatives exist. Harvard Library, for instance, supports journals that charge neither authors nor readers. Such models still require institutional investment, editorial labour and dependable technology. The real challenge is not simply making research available, but ensuring that openness does not depend on another form of exclusion.
The same challenge extends to the infrastructure behind public knowledge. A 14 October appeal from SCOSS sought renewed funding for the Research Data Alliance and Software Heritage, noting that insufficient funding had delayed some planned standards work. Open-source communities understand these pressures. Drupal, for example, supports complex institutional publishing environments, including a UK university platform managing more than 190,000 research records. Maintaining such systems requires continuing work on security, accessibility, data management and technical reliability. The software may be open, but the responsibility of sustaining it remains substantial.
Perhaps the most important lesson from this year's Open Access Week is that openness needs a long-term commitment, not just a declaration of principle. Universities, governments and other institutions should treat shared digital infrastructure as an essential public investment, with predictable funding, accountable governance and support for the people maintaining it. The open-source movement has demonstrated what communities can build together. Its continuing challenge is ensuring that those contributions remain useful and accessible for generations. Knowledge should belong to everyone, but keeping it that way must also become everyone's responsibility.
Follow The DropTimes on LinkedIn and Bluesky, or join #thedroptimes on Drupal Slack.
Kazima Abbas wrote and curated this issue of Editor’s Pick.
On the Limits of Drupal Orchestration and Shared Infrastructure
Drupal 12 Upgrade Guide: Release Date, Requirements and Removed Modules
Pantheon P1 Brings AI Agents to Web Building Without Replacing Drupal
Southwestern Ontario Drupal Camp 2026 Tackles AI Trust and Drupal 12 Readiness
DrupalCamp Italy 2026 Speakers Preview AI Migrations, Civic Platforms and Enterprise Security
Bringing Drupal Learning Closer to Home: Southwestern Ontario Drupal Camp 2026
Drupal Association Audits Drupal.org After PHP2Shell Fixes
Drupal Issues 34 Contrib Security Advisories, Including Highly Critical RCE
Jürgen Haas Proposes Charter-First Approach to Drupal Federation
Independent Audit Verifies Three Accessibility Fixes in Convivial for GovCMS
Drupal CMS Speeds Up Prototyping, but Delivery Still Depends on More
Dries Buytaert Demonstrates Drupal Tool Reuse Across AI, APIs and Workflows
Drupal AI Disclosure Beta Adds Spoken Audio Notices and Video Labels
FlowDrop 2.7 Adds In-Editor Workflow Testing and Execution Fixes
Mercury Editor 3 Reaches Stable Release With Autosave, Undo and Component Navigation
Symfony 8.2 to Add Declarative Controller Locking With #[Lock] Attribute
You are receiving this email because you opted in via our website.
Our mailing address is: