Thursday, May 15, 2008

Wikis in practice



Presented by Kathryn Sullivan and Danielle Whren
Full notes available here

Features of wikis include:
Editing
Comments
History
RSS
Search
Recent history log (for back up and to revert to earlier copies)
Changes can be sent to email

Why wikis?
Collaborative
Dynamic Text
Crosslinking
Thoughfully written
Topical arrangement
Accessibility
Eases info sharing
Easy to learn
Instantaneous updating (not reliant on one person)
Non-linear navigation
Well structured
Searchable
Inexpensive

Workplace benefits?
Growth in collaborative work
Simplified document management
Establishment of institutional memory
Increased staff feedback and voice
Improved customer service

On Wikis and other 2.0 tools: Libraries need to be present in spaces where people are.

Features and Considerations
WYSIWYG editors
Cost
Security
Locally hosted vs. Externally hosted

Locally hosted:
customizable
no space limitations
requires time and someone on staff with technical expertise in MySQL and PHP

Free/open source examples include PmWiki and MediaWiki (This is the platform that Wikipedia uses, it has a WYSIWYG editor and lots of good documentation already exists. A stable platform.)

Externally hosted:
little customization available
space limitations with an option to purchase more
little technical knowledge necessary

Examples include PBwiki and Wetpaint.

Compare Wikis at wikimatrix
[Note: One of the presenters stated that her organization is moving to Confluence.]

Building a wiki:
Have goals
Get input from staff
Select projects to include
Create some structure as a base before staff populate your wiki
Determine access levels
Prepare documentation/help/guidelines

Internal uses:
Scheduling
To-do lists (track who is doing what on various projects)
Team and Committee collaboration
List logins and passwords
Directory and contact info
Policies and procedures
Document repository
Project work and updates

HINT: As with any new technology, libraries will experience mixed levels of staff participation. However, if you want staff to start using the wiki, begin by finding a fun use. One library provided space to their "Cheers Committee" and staff had to sign up for the next staff potluck via the wiki.

Uses of an external (for patrons) wiki:
Research guides
Collaboration on projects with patrons (giving them a voice)
Collaboration with other libraries and librarians

Real world example:
Loyola Notre Dame’s wiki

They added a meebo widget to their wiki, so that staff can IM; they replaced their old HTML subject guides with new ones on the wiki; added tutorials for databases and style guides; included a new FAQ.

No comments: