Past Answers to Present Concerns. The Relevance of the Premodern Past for 21st Century Policy Planners: Comments on the State of the Field - NABO
Skip to content
NABO>Latest Posts>News>NABO News>Past Answers to Present Concerns. The Relevance of the Premodern Past for 21st Century Policy Planners: Comments on the State of the Field

Past Answers to Present Concerns. The Relevance of the Premodern Past for 21st Century Policy Planners: Comments on the State of the Field

Past Answers to Present Concerns. The Relevance of the Premodern Past for 21st Century Policy Planners: Comments on the State of the Field

Screenshot of the article showing authors and abstract
Reading Time: < 1 minute

Past Answers to Present Concerns. The Relevance of the Premodern Past for 21st Century Policy Planners: Comments on the State of the Field

This recently published paper is a collaboration sponsored by the CUNY-Princeton- U Maryland consortium which has had some very productive international workshops on trying to actually close the many gaps between what we think the past should be able to teach planners for a more sustainable future and what they are actually likely to use.  This is a product of the CUNY Human Ecodynamics Research Center and the NABO cooperative (based at Hunter College and the CUNY Graduate Center), who are very grateful to John Haldon and the Princeton Climate Change and History research team for hosting these events and bringing the project forward.

Haldon, J., Mordechai, L., Dugmore, A., Eisenberg, M., Endfield, G., Izdebski, A., Jackson, R., Kemp, L., Labuhn, I., McGovern, T., Metcalfe, S., Morrison, K.D., Newfield, T. and Trump, B. (no date) Past Answers to Present Concerns. The Relevance of the Premodern Past for 21st Century Policy Planners: Comments on the State of the Field, WIREs Climate Change, p. e923.

 

Related Posts


Share this:

Facebooktwitterredditpinterestlinkedinmail

Comments

Your email address will not be published. Required fields are marked *

NABO uses Accessibility Checker to monitor our website's accessibility. Read our Accessibility Policy.