Monday, March 24, 2008

MLA CE Week 2 - Wikis

This week I:
1. Reviewed the various wikis created by librarians to discover how they could be used in our library network.

2. Joined the class wiki @
http://mlawikiclass.wetpaint.com

3. Created a wiki called Peeps Pathfinder that is located @
http://peepspathfinder.wetpaint.com
The purpose of this wiki is to providing links to a variety of Peeps' e-resources ~ Overview of Peeps, Peeps in the News, Reference & Research, Books, Health & Nutrition, Blogs, Photos, & Videos. This is a sample of how a library staff wiki team could create subject guides to library resources ~ both print and online.

4. Posted a link to the blog I created on the
MLA Web 2.0 101 Blogs page : http://webphile.blogspot.com
Posted a link to the wiki I created on the MLA Web 2.0 101 Wiki page: http://peepspathfinder.wetpaint.com/

5. Wiki Collaboration. Became a member of the
Food in Town Wiki where I also created a post.

6. Created Blog Roll links to the
MLA Web 2.0 101 Blogs page and MLA Web 2.0 101 Wiki page on my blog--My Web 2.0 Conspectus

7. Difference between blogs and wikis:
I found both Blogs and Wikis easy to use and create. Blogs are authored by one with comments allowed by readers/users while wikis can include many authors/contributors. Blogs provide news or commentary on a particular topic. Blog entries are generally arranged in reverse chronological order.

Wikis are especially well suited for group collaboration projects resulting in documentation, user manuals requiring updates. Wikis allow anyone to add, edit or delete pages based on the parameters established for the wiki by the administrator. Wikis represent a real plus for the AMEDD MEDLI-NET librarians who are geographically dispersed throughout the United States and overseas. I think individual libraries or several libraries could work together to create a variety of subject guide wikis. AKO does not yet feature wikis but there are group collaboration/document management capabilities available. Wikis can be used as vehicle for both internal library communication as well as with the library’s users.

No comments: