How this class has already assisted coworkers...

After ACRL-Oklahoma, our Access Services Librarian decided that Library 2.0 might be just the thing she was looking for to improve communication between the supervisors, students, and staff in her area. She initially wanted to start a wiki for Access Services and give access to just those in her area. As Technology Support, I was the person asked about setting a wiki up. (Wikiup...Native house, right? Oh sorry. Wrong class.) I gave her what I felt were some of the advantages and disadvantages of wikis and blogs. She was wanting to get ride of all the email that contained procedures and policy. She didn't want to get rid of the information, but had a hard time finding the information in the countless email that was kept. By using a wiki, she was hoping to have something accessible to everyone and in one place. She also wanted to make sure that the internal conversations of the department were not accessible from everyone in the world. In retrospect, I think the security of a wiki might possibly rival that of a blog, but I do that that depends on where you set the wiki up. (There's that wikiup again!) I had suggested that blogs had more security options. What we decided was that blogs were easy to post and easy to respond to. The ease of use had to be such that staff and students would feel comfortable using it and would do so for whatever problems arose. My biggest concern was that a wiki would require additional instruction on wiki formatting and code. We will see how the new blog works for the department in the coming months.