06.09.2021 Views

Education for a Digital World Advice, Guidelines and Effective Practice from Around Globe, 2008a

Education for a Digital World Advice, Guidelines and Effective Practice from Around Globe, 2008a

Education for a Digital World Advice, Guidelines and Effective Practice from Around Globe, 2008a

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

25 – Tools <strong>for</strong> Online Engagement <strong>and</strong> Communication<br />

strict definitions of collaboration (see Chapter 28, Online<br />

Collaboration: An Overview).<br />

A technologically unsophisticated user D, encountering<br />

a page authored by a user C, may in many cases<br />

feel too intimidated to alter the text in any way <strong>and</strong> may<br />

instead create a totally new page. If this is titled User D<br />

Perspective, <strong>for</strong> example, this may be an entirely appropriate<br />

strategy. If the pages largely overlap in content,<br />

though, <strong>and</strong> if the relationship between them is not indicated,<br />

it creates a redundancy which may never lead to<br />

real engagement between the two users, since the wiki<br />

does not have the structures in place to push users towards<br />

discussion; or rather, although wikis can easily<br />

support discussion, this functionality is not <strong>for</strong>egrounded<br />

by default. The emphasis is very much on<br />

creating pages, which are works in their own right, ready<br />

to be read profitably by others.<br />

Thus, it may be better to avoid wiki exercises with<br />

non-advanced users or to make the exercises very limited<br />

in scope <strong>and</strong> pre-structure the wiki to some degree.<br />

Product over process<br />

While co-authoring a wiki page can be a highly collaborative<br />

<strong>and</strong> ongoing process, each time a page is saved it<br />

becomes a product. Although this product has the potential<br />

<strong>for</strong> future development, it is nevertheless very<br />

much a product in the eye of the casual visitor, <strong>and</strong> there<br />

is an unseen pressure on the authors to make it a “real”<br />

product on each page. Although much depends on the<br />

purpose of the wiki <strong>and</strong> the context surrounding its<br />

creation, in general the product aspect can be considered<br />

as being <strong>for</strong>egrounded, <strong>and</strong> this has a subtle effect<br />

on the dynamics of the process <strong>and</strong> the interaction between<br />

users. It is up to teachers to decide whether or not<br />

this is a positive thing. In general, we consider it overwhelmingly<br />

positive, as it focuses attention on incompletions<br />

<strong>and</strong> imperfections.<br />

Note that this does not mean that all problems have<br />

to be solved definitively. However, they do have to be<br />

acknowledged <strong>and</strong> defined as far as is practical, <strong>and</strong> this<br />

opens the way <strong>for</strong> future attempts at completion.<br />

From thread to document mode<br />

It is with relatively sophisticated users that wikis may<br />

come into their own, when teachers encourage the use of<br />

thread mode initially, but also encourage a process<br />

leading to a product in document mode (Bruns & Humphries,<br />

2005; Morgan, 2004). In other words, at first<br />

learners respond to each other’s ideas on the page as if<br />

the page were a thread in a discussion <strong>for</strong>um, but gradually<br />

begin to take ideas <strong>from</strong> other contributors, <strong>from</strong><br />

various parts of the page, <strong>and</strong> merge them into a partial<br />

summary or reconciliation of different viewpoints.<br />

These summaries serve in turn as raw material <strong>for</strong> others<br />

to summarize or exploit in other ways to achieve a<br />

higher synthesis.<br />

“Wiki goes meta—almost naturally.” (Morgan, 2004)<br />

In this process, even signed comments lose any clear<br />

authorship <strong>and</strong> become material <strong>for</strong> the co-authored<br />

text that emerges. Though this process can be difficult to<br />

achieve, it is arguably the highest <strong>for</strong>m of collaboration,<br />

<strong>and</strong> serves to demonstrate advantages of wikis over<br />

more fully featured threaded discussion <strong>for</strong>ums.<br />

EXTENDED WIKIS<br />

As mentioned above, wikis are not easy to use to their<br />

full potential in many educational settings. A large part<br />

of the difficulty is a conceptual <strong>and</strong> attitudinal one. If<br />

students do not wish to work together, it will be difficult<br />

to use a wiki effectively (Rick & Guzdial, 2006). There<br />

may be resistance to the idea of editing another’s text.<br />

The number of cases where a satisfying trans<strong>for</strong>mation<br />

<strong>from</strong> thread to document mode takes place may be quite<br />

limited, except where students are mature <strong>and</strong> there is a<br />

pre-existing culture of collaboration (Chapter 28, Online<br />

Collaboration: An Overview).<br />

In addition, there a number of difficulties associated<br />

with classic wiki engines that may be overcome by enhancements<br />

to the software, <strong>and</strong> we deal with some of<br />

these here. We use the term extended wiki to refer to<br />

software that is in general functionality <strong>and</strong> look-<strong>and</strong>feel<br />

a wiki engine, yet sports enhancements that take it<br />

clearly beyond most wiki engines in certain areas. We do<br />

not offer a hard-<strong>and</strong>-fast definition because, as wikis in<br />

general evolve, the functionality that qualifies an engine<br />

to be classified as an extended wiki is something of a<br />

moving target.<br />

Simultaneous edits<br />

Wikis are asynchronous tools in the sense that there is<br />

no requirement to be logged in at the same time as other<br />

users. This is on the whole a strength, but classic wiki<br />

engines can be inconvenient <strong>for</strong> in-class use because two<br />

users may edit the same page at the same time, potentially<br />

causing one user’s changes to be lost, depending<br />

on the relative timing of the respective users’ saves. Most<br />

wiki engines these days implement some measures to<br />

alleviate this problem. PhpWiki, <strong>for</strong> example, uses special<br />

markup to indicate areas where two people have<br />

made simultaneous edits between saves, giving the user<br />

the chance to reconcile the two versions, usually by<br />

396 <strong>Education</strong> <strong>for</strong> a <strong>Digital</strong> <strong>World</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!