Thursday, August 03, 2006

Wikitravel example

Here's a draft of the Wikitravel project description for the article.

mp
___________________________

The implementation of a project involving Wikitravel in recent Writing in Electronic Environments courses has proven productive in teaching of the course and with students’ engagement in public and collaborative writing. In addition, more than updating electronically traditional goals of writing pedagogy, the project also illustrates the revolutionary role of the networked computer in digital writing (Porter 2002). This project asks students to participate and create in a writing environment that parallels many other environments these “digital natives” (Prensky 2001) engage in regularly, from MySpace or Facebook to blogs to IM and video games. The following brief description outlines this digital writing project and the ways in which it follows Melinda Turnley’s (2005: 132) call for students to “intervene productively in relationships among technology, texts, and people.”

Wikis represent a set of webpages with an open-editing system; in other words, anyone can add to, delete, or change a wiki, making them highly collaborative. No knowledge of HTML is required, only a networked computer with a web browser. While classroom-based wikis present tremendous opportunities for collaborative writing, we aimed for a more public wiki, one which pushed students into the networked environment within which wikis flourish. In other words, we didn’t want the network to be our class.

The Wikitravel site started in June 2003 and represents a free, open, world-wide travel guide created and maintained by “Wikitravellers from around the globe.” With only 8,000 articles, Wikitravel presented a more manageable and productive entry into wikis for my students than the more popular Wikipedia. In addition, the New England area, especially Rhode Island, entries were particularly thin, holding no more than templates. After introducing wikis and Wikipedia, we asked students to explore Wikitravel, honing in on local New England articles. What became apparent was the empty and, at times, inaccurate information for the state of Rhode Island. Their goal was to begin building the Rhode Island aspect of Wikitravel.

The classes divided into groups based on local areas of interest, such as Block Island, Providence, or South County. While all aspects of Rhode Island required content, each group explored the existing or non-existing templates for their region, making decisions as to how and what they would contribute. As the groups quickly noticed, Wikitravel manages contributions by relying on standard templates, including categories for history, travel to and from, eating, and sleeping. Essentially, students were forced to make the choice between breadth and depth, depending on their approach. In other words, they could attempt to add content throughout the template or they could hone in on one or two areas and add substantial content to, for example, the dining section of Providence.

Additionally, Wikitravel has a thorough Manual of Style which outlines in detail the preferred form for entries, including the listing of phone numbers, hours of operation, and URLs. So, students were not only researching Wikitravel and its format, but they were also researching their regions. This research required a merging of first-hand experience with published reviews, articles, or information. Especially in the state of Rhode Island, local knowledge is valued over, and many times conflicts with, official knowledge or information. For example, South County is not an official county. It represents an imaginative geographic area in the southern portion of the state, including the official Washington County. But it also represents a rural and less-populated region complete with beaches, roadside garden stands, and an independent attitude. Students struggled with how to represent their regions accurately to potential travelers within a standard template--how do you make South County fit into Wikitravel’s model?

Unlike web pages, which are published and then frequently or occasionally updated by a webmaster, wikis are always in a state of flux, always being re-published. Students struggled with the collaborative and combative approach to writing Wikitravel required. As they researched, they published and they revised. Group members constantly mediated additions and revisions with fellow group members and the public at large. Ownership of writing was in flux as writers pushed towards a “final” developed node. Minor and major changes from classmates and anonymous Wikitravellers kept the audience and public nature of their writing at the fore as they pushed for a useful travel guide. With a goal of multiple outlet formats, Wikitravel requests that contributors avoid HTML. Instead, contributors are asked to rely on Wiki markup when editing a page. A straightforward table walks Wikitravellers through the process, illustrating “To get this output…use this markup” instructions. Granted, students only learn minimal HTML with this project. However, this contextualized writing for the web provides students with a situation in which they must adopt to their purpose to a prescribed and preferred format—a useful skill in any writing environment. Further, especially in the context of other projects throughout the semester that include web authoring software and Blogger markup language, the Wikitravel project exposes students to the code and structure underlying all writing on the Web. This process complicates what writing in electronic environments consists of and how writers mediate their purposes with preferences and technology.

As a public, technologically-mediated environment, Wikitravel asks students to consider the creation of knowledge in their digital-native culture that values and supports peer-to-peer, distributed networks. In terms of Wikitravel, editors and users must maintain the global picture while they work at the micro-level. Students, many of whom still operate under a Britannica-like knowledge structure, balk initially at the idea of others revising or editing their sentences or words. However, at the macro-scale, students see vast improvements and additions that are ultimately useful and robust. Sure, the Block Island node might have some grammar issues or even an inaccurate phone number for a hotel, but the overall node in the context of the Rhode Island site is a helpful, locally-created travel guide.

2 Comments:

Blogger jeremiah said...

Thanks for this text.

In my thinking, our examples (one on hate speech discussions, one on wikitravel entries) illustrate our description of the "environment" concept.

So far, the wikitravel example makes me think that while students may especially value learning about wikis and about code and markup, the big lesson, in terms of our goals for WRT 235, is a lesson about working within the purpose and mission of the Wikitravel project. Wikitravel is itself an environment for the development of information about local places, and, from your description, at least, one that has already susbtantially customized
the basic wiki technology for that purpose.

I wonder how we can think about the linked discussions about hate speech as constituting an environment in this way? Here are two thoughts: using hyperlinks, our students imported information about (and examples of) online hate speech into the discussion space. We required this; it made for a central part of our (teacherly) customization of the WebCT discussion technology. Another customization was the importation of IEDP-style posting conventions (e.g., acknowledge others' posts, summarize others' arguments, end with your own question).

I'm not so sure that Linda and I were as explicit about what we wanted out of the discussion as Wikitravel is about its purpose and product, but perhaps we can link discussion of the two projects based on a discussion of our students' learning to work with/in these customized writing environments. . .

Hmm. I'm thinking out loud, I guess--

J

10:42 AM  
Blogger jeremiah said...

In response to Jeremiah's reponse, I consider the hate speech experience, especially the students' IEDP style interchanges, as evidence of the course's previous "mind-set" --or "pre-enviornment" approach. For me at least, the underlying structural pattern was linked to Critical thinking about communication with and in the grip of the technology. I set up each project so that students could evaluate how the technology was both inviting them to cmomunicate and undermining the best hopes for that communication. This is an interesting approach a la Cindy Selfe & others, but I believe it is not an approach that is "native" to the technology, nor is it one that starts in 235 reaches through the rest of the curriculum.

This is, to me, opposite in many to the environmental approach. The enviornmental approach is "native" or springs from the circumstances of the technolgy and it represents both a way of thinking about writing in the midst of that technology and being enabled by that thinking, as well as taking critical attitude toward activities tat destroy or are not productive in the enviornment. So, it is an extemely fruitful principle that then stretches from 235 through the rest of the curriculum.

The way of thinking about the hate speech unit and the travel wiki unit pulls the whole paper together, especially including the history segment, which posits that the course has an evolutionary trjectory, moving from pratical motives to a theoretical basis that emerges from the circumstances of wriitng with that technology.
LKS

10:27 AM  

Post a Comment

<< Home