Show Summary Details

Page of

PRINTED FROM OXFORD FIRST SOURSCE (www.oxfordfirstsource.com). (c) Oxford University Press, 2013. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford FIRST SOURCE for personal use (for details see Privacy Policy and Legal Notice).

date: 02 August 2021

Abstract and Keywords

In the aftermath of the Great War, the Allied nations compiled both regimental and general histories of the conflict. In these narratives, the experiences of the soldiers and their commanders are filtered through the ultimate outcomes—and attendant sufferings—inflicted by the war. The errors of judgment and planning made by commanders are preserved in these records, and are particularly significant to our understanding today of battles whose brutality and massive death tolls are still shocking. The contribution of ANZAC (the acronym for Australian and New Zealand Army Corps) troops to the campaigns at Gallipoli and the Dardanelles (April 1915–January 1916) against the Ottoman Turks is marked in the ANZAC countries as a solemn day of remembrance. In this excerpt from a multivolume narrative of the campaigns compiled by C. E. W. Bean, the casualty figures, and Bean’s reactions to the deployment of soldiers and the possible waste of war, are striking.

C. E. W. Bean, The Story of ANZAC from 4 May, 1915, to the Evacuation of the Gallipoli Peninsula, 11th ed. (Sydney: Angus & Robertson, 1941), 743–745, 761–762, available online at http://www.awm.gov.au/histories/first_world_war/AWMOHWW1/AIF/Vol2/.

Access to the complete content on Oxford First Source requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can''t find the answer there, please contact us.