I agree that the blog is a feasible alternative to listservs and email chains (because it can archive discussions), but I don't think it works as a project management tool. That use would best be served by a wiki so that every participant has equal access to contribute in an organized layout.
Using a wiki to manage a library instruction program
As an intern with StoryCorps, I was able to utilize their wiki to learn about each department's responsibilities. They need a centralized space because the staff is spread out across the country; anyone is able to download forms and manuals directly from the wiki. The article points out the main advantage of wikis when it advises to "use everyone's specific experiences and valuable individual expertise."
Creating the academic library folksonomy
I wonder how much of a problem "spagging" is on library websites. Having subject specialists start the process is a good way to set a professional environment.
Jimmy Wales: “How a ragtag band created Wikipedia”
I'm surprised there was only one software developer maintaining Wikipedia in 2005. Have they added any more paid employees?
I agree with you that application of wiki would be advantageous for a bigger project. However, blogs have a capacity to handle a project and provide ways to manage smaller projects and serve a purpose. Blogs are intuitive and all depends on the scope of the project, chosen platform, server, and etc. At the same time, success of wikis depends on volunteers’ commitment, number of participants, scope of the project, and “popularity”. I think blogs and wikis are “fading” now. Public wants different tools for information access and collaboration. It is just my view.
ReplyDelete