Journal article

A mistaken iconography? Eighteenth-century visitor accounts of Stourhead

Publication status:: Published

Peer review status:: Peer reviewed

Actions

Email

Email this record

Send the bibliographic details of this record to your email address.

Your Email
Please enter the email address that the record information will be sent to.

-
Your message (optional)
Please add any additional information to be included within the email.
Share
Cite

Cite this record

APA Style

Cox, O. (2012). A mistaken iconography? Eighteenth-century visitor accounts of Stourhead. Garden History, 40(1), 98–116.

MLA Style

Cox, O. “A Mistaken Iconography? Eighteenth-Century Visitor Accounts of Stourhead.” Garden History, vol. 40, no. 1, 2012, pp. 98–116.

Chicago Style

Cox, O. 2012. “A Mistaken Iconography? Eighteenth-Century Visitor Accounts of Stourhead.” Garden History 40 (1): 98–116.
Print

Access Document

Files:: Garden History Journal Article (Revised).docx.pdf

(Preview, Accepted manuscript, pdf, 232.3KB, Terms of use)

Authors

+ Cox, O More by this author

Institution:: University of Oxford
Division:: HUMS
Department:: History Faculty
Role:: Author

Publisher:: Garden History Society
Journal:: Garden History More from this journal
Volume:: 40
Issue:: 1
Pages:: 98-116
Publication date:: 2012-08-01
Acceptance date:: 2012-07-01
ISSN:: 0307-1243

Keywords:: SBTMR
Pubs id:: pubs:638889
UUID:: uuid:c21b7ddd-0404-489d-9931-5b68d67d9545
Local pid:: pubs:638889
Source identifiers:: 638889
Deposit date:: 2016-08-17
ARK identifier:: ark:/29072/ora_c21b7ddd0404489d99315b68d67d9545

Terms of use

Copyright holder:: The Garden History Society
Copyright date:: 2012
Notes:: This is the
accepted manuscript of a journal article published by The Garden History Society in Garden History in 2012-08, available online: http://www.jstor.org/stable/41719890

Licence:: Terms and Conditions of Use for Oxford University Research Archive

Views and Downloads

About views and downloads

If you are the owner of this record, you can report an update to it here: Report update to this record

TO TOP