Evaluating Wikis: A Case Study

03/11/2006

Hello

Phil Wilson
Web Developer
I am not e-learning
- not that bothered about the pedagogical stuff
p.g.wilson@bath.ac.uk
15 minutes! Yikes!

Why are we doing this in the first place?

because we're selfish
internal use expanding too fast
want to support cool things

Who's it for?

did I say we're selfish?
internal use (and the rest)
oh all right then, everyone

What do we need (features)?

everything you expect from a wiki
edit, create, delete
attachments, comments
page history, rollback

What do we need (backend)?

as little work as humanly possible
wiki farming
very flexible permissions system
- users, groups, etc.
hook into our authentication
API, API, API!

What do we need (frontend)?

WYSIWYG
uh
WYSIWYG
themes/skins (maybe)

Choosing candidates

5 years' experience
wikimatrix.org
JSPWiki, Mediawiki, Confluence, JotSpot, XWiki

E-val-u-ate! E-val-u-ate!

all that stuff in a handy-to-use chart

Conclusions

there are no alternatives, only Confluence
flexible enough for e-learning use
- I think
That's it.
If you're serious, pony up.