Site Logo
All articles
Commentary on News

APC Trap: qualitative analysis of open-access APCs

Evidano6 min read

Researchers face contradictory pressures: publish open access to increase reach, but pay rising article processing charges (APCs) that worsen equity. This post walks UX, library, and research teams through a practical qualitative analysis of open-access APCs based on a July 1, 2026 PLOS ONE study (Cantrell et al.), and shows how to reproduce actionable insights with an AI-enabled qualitative analysis platform. You will get the study snapshot, the implications for decision-makers, and a compact 7-step AI-enabled workflow to turn 154 open-ended responses into stakeholder-ready evidence.

Key Takeaways

The PLOS ONE study by Cantrell et al. identified an "APC Trap, " eight overlapping themes that create moral and operational binds for authors paying open-access APCs. The qualitative sample included 154 substantive open-ended responses, and 90% of those contained at least one APC Trap theme. The post describes implications for PIs, libraries, UX/ops teams, and a 7-step workflow to reproduce the study’s analysis with an AI-enabled platform.

  • Cantrell et al. published the study on July 1, 2026 and coded 154 substantive free-text responses into eight APC Trap themes.
  • Survey collection occurred Oct 31–Nov 21, 2023, and 322 surveys were completed with 154 open-text responses used for coding.
  • Ninety percent of the coded responses (n=139) showed at least one APC Trap code, with 62% containing 1–2 codes and 28% containing 3+ codes.
  • Top concerns in the qualitative sample were Financial Concern (~34%) and Diversity/Equity (~32%), with demographic patterns showing HSS authors reported APC stress more often.

Fast take + source

Fast take: Cantrell et al. (PLOS ONE, July 1, 2026) analyzed 154 substantive open-ended responses from authors at four U.S. R1 institutions and identified an "APC Trap" of eight overlapping themes.

Read the full paper: PLOS ONE.

  • Study dates: survey collected Oct 31–Nov 21, 2023; published July 1, 2026.
  • Core finding: 8 APC Trap codes (Financial Concern, Diversity/Equity, Threshold of Reasonableness, Restriction of Decisions, Grants Don’t Cut It, Academic Obligation, Academic Labor, Quality/Rigor).
  • Sample: 322 completed surveys; 154 substantive free-text responses coded; 90% of those showed ≥1 APC Trap code.

Findings snapshot

MetricValueSource / Note
PublishedJuly 1, 2026PLOS ONE
Survey periodOct 31–Nov 21, 2023Methods section
Respondents (completed)322Quantitative pool
Substantive open-text responses154Qualitative sample used for coding
APC Trap codes identified8Inductive codebook
Responses showing ≥1 APC Trap code90% (n=139)Thematic coding result
Institutions sampledUCB, UMass, Pitt, UTKFour U.S. R1 public universities

What happened (plain English)

Cantrell et al. appended two open-ended questions to a broader APC funding survey and used inductive thematic coding to identify eight overlapping APC Trap themes from 154 substantive replies.

Cantrell et al. combined responses from authors at four R1 U.S. universities and required coder consensus and iterative codebook refinement during analysis.

  • Most responses contained 1–2 codes (62%); 28% showed 3+ codes, reflecting layered frustrations.
  • Top concerns: Financial Concern (~34%), Diversity/Equity (~32%), and decisions restricted by fees.
  • Demographic patterns: HSS authors reported APC stress more often; Hybrid OA authors showed more APC Trap codes than Gold OA authors.

Implications for researchers: qualitative analysis of open-access APCs

For PIs and lab leads

The APC Trap shows a trade-off between career expectations and budgets: PIs routinely reallocate discretionary or trainee funds to pay APCs.

PIs should expect pressure to justify publication venue choices to promotion committees, plan budgets accordingly, and document trade-offs.

For library & scholarly communication teams

The findings underline demand for clearer institutional OA support and transparent APC reporting.

Library teams should note that hybrid/read-and-publish agreements may hide costs but do not remove the ethical concerns flagged by surveyed authors, and should prioritize targeted communication and equitable waiver policies.

For UX / research ops teams

The qualitative themes such as Restriction of Decisions and Threshold of Reasonableness are operational signals for UX and research operations teams.

UX and research ops teams should track who is affected by APC issues (discipline, career stage) and convert open-text signals into segment-specific interventions such as funding, training, and alternative outlets.

Do more, faster with Evidano

About Evidano

Evidano is an AI-powered qualitative data analysis platform that ingests spreadsheets or Qualtrics exports, applies reproducible codebooks, and produces stakeholder-ready outputs.

Evidano supports thematic coding at scale while preserving audit trails and human consensus review.

Problem: scattered open-text + manual coding

The problem is scattered open-text responses and manual coding workflows, which make qualitative analysis slow and hard to reproduce.

The solution is that Evidano ingests spreadsheets or Qualtrics exports and runs thematic coding at scale with a reproducible codebook import.

Problem: inconsistent coding and coder drift

The problem is inconsistent coding and coder drift across manual teams, which reduces reliability and increases review time.

The solution is to import the Cantrell et al. codebook into Evidano, run AI-assisted coding, then review consensus disagreements in a single UI to save hours and preserve audit trails.

Problem: where do concerns cluster?

The problem is limited visibility into how concerns co-occur across segments, which hinders prioritization.

The solution is that Evidano cross-segment analysis shows co-occurrence (for example, Financial Concern plus Restriction of Decisions) and builds co-occurrence networks and hierarchical code-to-subcode visualizations to prioritize interventions.

Problem: stakeholder-ready deliverables

The problem is manual preparation of deliverables from coded data, which is time-consuming for teams.

The solution is that Evidano offers one-click exports (word clouds, co-occurrence tables, quote lists per segment) and an AI chat that answers questions over your dataset, all encrypted and never used to train third-party models; try a demo at Evidano.

This week’s 7-step workflow (reproduce the paper’s analysis in Evidano)

This 7-step workflow explains how to convert raw survey exports into an actionable APC report using Evidano.

  • 1) Import: upload your Qualtrics CSV or spreadsheet into Evidano and map the two free-text fields.
  • 2) Normalize & clean: run PII redaction and merge responses per respondent (as the study did).
  • 3) Import codebook: load the eight APC Trap codes (or adapt) as a hierarchical codebook.
  • 4) Auto-code: run AI-assisted coding, tag conflicts, and batch-approve consensus codes.
  • 5) Cross-segment: run by-discipline and by-institution cross-tabs and co-occurrence networks.
  • 6) Extract quotes: filter representative quotes per code and export a stakeholder-ready brief.
  • 7) Share & iterate: use Evidano visualizations in meetings, re-run after policy changes, and keep your dataset secure.

FAQ: open-access APCs

Can automated coding capture the nuance in this study?

Yes, automated coding can capture nuance when combined with human consensus review.

The paper shows that sentiment-only tools can misclassify nuance, so the recommended practice is to use AI-assisted coding as a force multiplier plus human consensus review to preserve nuance.

How do I compare segments (HSS vs NSE) robustly?

Use cross-segment frequency and co-occurrence reports and export filtered quote lists for each segment to compare lived experiences.

Evidano supports by-discipline and by-institution cross-tabs and quote exports so each segment’s experience is visible to decision-makers.

Is the platform secure for sensitive author comments?

Yes, the platform encrypts data at rest and in transit and does not use customer data to train third-party models.

This security posture supports compliance-sensitive research workflows involving author comments and institutional data.

Wrapping up: your next two moves

Wrapping up: the APC Trap reframes APC debates as issues of obligation, inequity, and academic labor, not just price.

  • Action 1: Re-run a targeted qualitative sweep of your institution’s recent authors using the 7-step Evidano workflow.
  • Action 2: Share a one-page brief with library and finance stakeholders using Evidano exports to argue for targeted APC support or policy changes.

See the study at PLOS ONE and Try Evidano for free to run a secure pilot and turn open-ended comments into decisions.

Company
About
Newsletter

Product updates, research, and tips — straight to your inbox.

© Evidano, All Rights Reserved.