In what sense does a wiki really belong to the library that hosts it? Sure, if it’s an internal wiki, it fully belongs to the library. But what if it’s a product that the library provides for patrons? Isn’t it their wiki then? I don’t mean that patrons shouldn’t feel and have some ownership of their library’s resources — but what is the library providing?
Of course, this raises the question of how much the library has to be a provider as opposed to a facilitator. Maybe this is our new job: not only provide information, but provide a platform for its creation, too. (Is that the same as publishing?)
Actually, the SJCPL wiki is a little more “Web/Library 1.0” in that it’s the traditional activity of making pathfinders or reading lists (in this case, of web resources). I like it. I think that lots of libraries could emulate that one, starting with their commonest reference questions and common research topics.
Another wiki use I’d like to see might be appropriate to a public library website: a “Guide to Fairbanks [or FNSB]” wiki. The public library gets plenty of questions from tourists on things to see, places to eat, walks and hikes to take, et cetera — and those aren’t of interest only to tourists. What a great place for locals to get the skinny (and dish the dirt) on their favorite restaurants, CSA ventures, health care options… hell, anything. People would be willing to share plenty.
I think that another interesting one would be a UAF wiki: “The Student, Faculty, Staff, and Visitor Guide to UAF”. Would the university, having sponsored this, engage in “radical trust” over the content? What an exciting — and maybe dangerous — way for current and potential studnets to learn about us.