Final Project--Wiki
I've thought a lot about a useful project for my library. My first thought was a myspace page. I have actually already put up a rudimentary page. I find it not as easy to do what I'd like with it as I would like. Since then I've developed a lot of enthusiasm about the usefulness of wikis. Wikis are an application which allow any user to add content. I think that something I would like to do is develop a library instruction wiki. Our library is a very small one and most of the librarians are part-time. There is no opportunity for us to all sit together in one place and discuss ideas. We do a lot of informal idea sharing about library instruction classes. However, that's all oral and dependent upon whether the librarian with an upcoming class happens to cross paths with the librarian who last did a particular class. A wiki would provide a place to share this sort of information.
The foremost example of this use of wikis is, of course, the Oregon Library Instruction Wiki instructionwiki.org This is a place where libraries have collected many types of library instruction resources, including: handouts, tutorials, etc. This wiki and library instruction wikis generally are widely praised. See:
www.webstylus.net/vala/node/17
blog.nekls.org/index.php/archives/161
libtechtexas.wordpress.com/2005/11/03/library-instruction-wiki/
One of the beauties of a wiki for me would be the opportunity to circumvent the institutional roadblocks often encountered in my library. We often have difficulty convincing IT of the validity of our needs. Wikis are so easy I can just do it myself! The only in-library problem I might encounter is a feeling on the part of some librarians that there is "too much new technology to keep up with". I think this may be overcome by the usefulness of the wiki. It could overcome a real problem in communication for each of us. I also don't have to worry about money. I can use a free, remotely hosted wiki program.
I might use pbwiki since we already use it for one purpose in the library and staff are familiar with it. I've looked at wikimatrix for other programs that meet my criteria (free, remotely-hosted) and a couple of possibilities are Cospire and Jotspot.
Another beauty of the wiki would be its ease of maintenance. If people start using it much of the maintenance is just getting people to add to it. Since it will be for library in-house use only there should be little or no maintenance of entries, etc. My role should be to encourage use and keep an eye for software updates.
I'm enthusiastic about this new tool for my library and look forward to working on it.
- ellieswanson's blog
- Login to post comments

Ellie this is a great idea
Ellie this is a great idea and so fun! I am excited for you :) I ended up with PBwiki too and so far, I am really pleased. It meets our needs (no cost!), allows us to educate and inform our patrons and staff simply and it puts the power of doing so in our hands. IT has so much to do, so you are right, it gets y'all involved with no cost except that of your time. But it's a wise investment and should allow you to reap the rewards continuously. Coolness!
Rachel S. Kingcade
Ellie, You've got the right
Ellie, You've got the right idea! Creating a wiki as a space to gather resources and instructional ideas is a great solution. Especially, since most of the librarians you work with are part-time. Your wiki could begin as your virtual meeting space, possibly this might solve your in-house problem. Using the wiki to satisfy one need for now. For instance, you could use PBwiki (free, easy, clean look and your librarians may be familiar with this format) to discuss ideas in a forum/chat and if "too much technology to keep up with" is a concern - maybe you could have a new technology wiki page that pulls in some key RSS feeds. I think your idea is excellent!
Good Luck :)
Looks good! I like the line
Looks good! I like the line at the top of the OR Library Instruction Wiki: "...stop reinventing the wheel." Too true.
Ellie, Your wiki idea
Ellie,
Your wiki idea sounds really well thought out. It seems like a good idea for a library of your size, where you want to avoid "reinventing the wheel" as much as possible. The advantage of your wiki would be that it could be modified and added to as needed.
Dell Bayer TechLibrary
Dell Bayer TechLibrary Sandia National Labs jabayer@sandia.gov
This sounds like a foolproof idea, especially since the wiki would be low maintenance and you can do so much of it yourself. No need for IT involvement. I think these new social tools are freeing a lot of librarians from their previous dependence on IT folks (who often don't even speak the same language / jargon). The communication among your (mostly) part-time staff colleagues would be easier and hopefully more productive than it is now. So that is well worth the effort. Good luck!