Skip to main navigation Skip to search Skip to main content

Festival processes, innovation, and locality response: Evidence from South Africa's Rage youth festival

  • University of Johannesburg

Research output: Contribution to journalArticlepeer-review

9 Citations (Scopus)

Abstract

One underrepresented theme in the burgeoning literature on festivals relates to the hosting of dedicated youth tourism festivals. Applying a qualitative research methodology, this article investigates festival development processes using the example of the annual Rage youth festival in South Africa. It is argued that despite their large economic impacts for destinations, youth tourism festivals often are controversial events that are associated with problematic social behavior by revelers. In this case study, several innovations were enacted by festival organizers for the purposes of control and containment, which potentially allows the local economic benefits to be realized at a minimal social cost. The example of the Rage Festival is instructive in the international context for demonstrating the need to understand innovative festival development processes at the microscale through a qualitative research approach, which offers fresh insight to complement traditional quantitative analysis of festival expenditure impacts.

Original languageEnglish
Pages (from-to)169-179
Number of pages11
JournalTourism Review International
Volume21
Issue number2
DOIs
Publication statusPublished - 2017

UN SDGs

This output contributes to the following UN Sustainable Development Goals (SDGs)

  1. SDG 9 - Industry, Innovation, and Infrastructure
    SDG 9 Industry, Innovation, and Infrastructure

Keywords

  • Festival process
  • Festival tourism
  • Innovation
  • South Africa
  • Youth tourism

ASJC Scopus subject areas

  • Tourism, Leisure and Hospitality Management

Fingerprint

Dive into the research topics of 'Festival processes, innovation, and locality response: Evidence from South Africa's Rage youth festival'. Together they form a unique fingerprint.

Cite this