CACrown ArchivesThe cinema collection
Menu
Research dossier · History & Society

Battle of Ganghwa

1871 Joseon–United States battle

Layered newspapers, civic records and oral-history reels arranged as chronological evidence
History and societyInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionAug 21, 2026
Entity authoritySource title only
Source-derived summary

The Battle of Ganghwa was fought during the 1871 United States expedition to Korea, a conflict between Joseon and the United States. In May of that year, five Asiatic Squadron warships set sail from Japan to ascertain what happened to the crew of the SS General Sherman as well as to establish a trade treaty with the Hermit Kingdom similar to the one Commodore Perry had pressured Japan into adopting in the early 1850s. When American forces arrived in Korea, the originally peaceful mission turned into a battle when guns from a Korean fort suddenly opened fire on the Americans. The battle to capture Ganghwa Island's forts was the largest engagement of the conflict.

Editorial summary

“Battle of Ganghwa” enters the record as 1871 Joseon–United States battle. Crown Archives preserves that source wording while asking what Battle, Ganghwa and Joseon can confirm, complicate or overturn.

Editorial reviewA strong contextual entry point for chronology, institutions and public events when official records are distinguished from later interpretation. The current lead gives the account dated anchors—1871—that can be checked directly. The selected authority fields contribute no independent date. Its strongest next move is a source search built around Battle, Ganghwa and Joseon.
Editorial analysis

Why this record matters

“Battle of Ganghwa” is worth following because a concise public description often conceals a longer documentary argument. Here, Battle, Ganghwa and Joseon provides the most credible route into that argument.

Evidence profile

Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Aug 21, 2026. The first chronological checks are 1871.

Critical limits

Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.

Best used for
  • Event chronology
  • Institutional context
  • Locating named record creators
Verify next

Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.

Three-step research path

  1. Establish the record: confirm the title “Battle of Ganghwa”, its source revision and the description used here.
  2. Expand the search: follow Battle of Ganghwa primary sources, Battle of Ganghwa archive and Battle research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Battle of Ganghwa”?
  2. What chronology connects this entry to wider political or social change?
  3. Which voices are present, absent or mediated by the institution?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Battle of Ganghwa” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.