Wiki World

From Library Success: A Best Practices Wiki
Revision as of 17:29, 2 January 2006 by Meredith (Talk | contribs)

Jump to: navigation, search

Contents

What is a Wiki?

Why Wiki?

  • Easy to use
    • Web-based
    • Simple syntax (don't need to know HTML)
  • Anyone can make changes -- no more waiting for the Webmaster to get around to your requested changes.
  • Many free and open source options
  • Flexible and extensible


Why Not?

  • Too open -- "I don't want someone changing my writing!"
  • Vandalism and spam
  • No "credit"
  • Intellectual property issues


How Libraries Can Use Wikis With Their Patrons

  • Wikify the OPAC
    • Patrons annotating the catalog -- see Open WorldCat for an example.


How Librarians Can Use Wikis for Knowledge Sharing and Collaboration

  • Staff Intranet
    • Collaborative Document Development
    • Reference Wiki
  • Collective Knowledge Base
    • Stop reinventing the wheel!
    • Benefit from the experiences of others
    • Examples
      • Library Success Wiki -- space for collecting success stories about providing services in libraries
      • Library Instruction Wiki -- space for collecting Web links, hand-outs, and success stories about providing information literacy instruction.
      • LISWiki -- library science knowledge base
      • DigiWik -- all about digitization
      • The Teachers' Lounge -- collective knowledge base for teachers
  • Planning Space for Conferences, Meetings, etc.
  • Group Projects
    • Collaboratively editing a document.

So You Want To Build a Wiki: Important Considerations

Where Will Your Wiki Live?

DIY Wikis (hosted on your server, installed by you)

Check out the Wiki Matrix to compare wikis side-by-side.

Hosted Wikis/Wiki Farms (your wiki on another company's servers)

Check out the List of wiki farms in the Wikipedia.


Important Things to Consider When Choosing Wiki Software

  • Programming language
  • Ease of installation
  • Ease of use
  • Cost
  • Syntax
  • Version control
  • Ability to hold discussions
  • RSS
  • Ability to change look
  • Security
    • Permissioning
    • Spam prevention


Getting People On Board

  • Have a specific purpose
  • To structure or not to structure?
  • Be explicit.
  • Actively prevent spam.

See my advice for building a successfull wiki at ALA Wiki: What I learned and what Iā€™m doing with it (on my blog) and So You Want to Build a Wiki? (from WebJunction).

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox