Jump to ContentJump to Main Navigation
Once Were PacificM ori Connections to Oceania$
Users without a subscription are not able to see the full content.

Alice Te Punga Somerville

Print publication date: 2012

Print ISBN-13: 9780816677566

Published to Minnesota Scholarship Online: August 2015

DOI: 10.5749/minnesota/9780816677566.001.0001

Show Summary Details
Page of

PRINTED FROM MINNESOTA SCHOLARSHIP ONLINE (www.minnesota.universitypressscholarship.com). (c) Copyright University of Minnesota Press, 2022. All Rights Reserved. An individual user may print out a PDF of a single chapter of a monograph in MNSO for personal use.date: 20 May 2022

A Time and a Place

A Time and a Place

(p.213) Epilogue A Time and a Place
Once Were Pacific

Alice Te Punga Somerville

University of Minnesota Press

This chapter considers the potentially negative connotation of an argument by which “indigenous bodies” might be recorded as “migrant bodies”. It discusses the project Once Were Pacific's demands for a regional identification that “emphasizes” rather than “distracts” from indigeneity. The chapter concludes with a review of Once Were Pacific's portrayal of Tupaia's painting of an Englishman bearing tapa and a Māori man bearing seafood in 1769. Once Were Pacific perceives Tupaia's painting in terms of the complicated dynamic of Māori-Pacific connection, implying that a symbolic reunion of the artwork describes a tangible affirmation of Pacific oral traditions and cultural practices.

Keywords:   indigenous bodies, migrant bodies, Once Were Pacific, regional identification, indigeneity, Tupaia, Māori-Pacific connection, oral traditions, cultural practices

Minnesota Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.