Add an entry to the VBPL Reader's Advisory wiki

I like the concept of the site, but it was hard to navigate through. I went to the Adult book list and couldn't get past the "Fiction" "Nonfiction" page -- it had no links to move beyond it.
I then went to the Staff Picks and added two titles, but evidently only saved one. The fiction title I added definitely showed up. I thought that was really cool to add a favorite title so that others can read it too! I then tried to add comments to the entry and got totally lost - I wanted to add the taglines there like I see one person had done and got nowhere. I think the tags will be important to build reading lists so maybe I will try again tomorrow with a fresh brain!

I think reading groups, the Summer Reading program, and other Reader's advisory groups can use Wikis effectively. A staff member who doesn't read in a particular genre can use a wiki to find current lists of the books in VBPL that appeal to that type of genre reader -- the customers can also use that list and contribute their own titles -- that opens the shelves to our customers!

I see wikis and Reader's Advisory as a perfect match!

Wikis in the Library

Interesting things about Wikis…

• I enjoyed looking at the various Wikis – they were really good examples of what can be done with Wikis in the Library. The various looks of Wikis are also amazing -- From the familiar Wikipedia encyclopedic look which the Library Success: a best practices wiki shares to an eye-catching appearance like the Bull Run Library wiki the possibilities are virtually endless as to the content and style you choose to create for the Wiki.

What types of applications within libraries might work well with a wiki?

• For CS definitely I can envision our P&P Manual set up as a wiki. The collaborative editing of documents feature would enable us to instantly update the manual without going back and forth with emails and waiting for the information to get updated in the manual. Because it is specific to CS practices as an internal document, the wiki could be set up so that only CS staff members could edit and view the wiki.
  
• The Library P&P manuals could also be a wiki, with editing rights limited to the P&P committee, but the manual itself viewable to all library staff who would have the ability to comment on but not edit the policies and procedures.
• The Periodicals catalog which lists holdings could be a wiki, with editing rights for the staff who are responsible for the periodicals in each agency – instant updates!
• The Reader’s Advisory function is a perfect candidate for a wiki – readers telling other readers what they liked and didn’t like about the books they have been reading – that’s like pearls and cameos – a perfect match!!
• I could also see a wiki designed to solicit feedback from public service staff to CS about subjects and other access that would make life easier working with the public
• Training guides could also be created as a wiki with the help screens guiding the customer through the topic such as: self-checkout, how to renew a book, how to access the various online resources we have, etc.
• We tried a wiki for online collaboration on one of the committees I was on, but the process seemed cumbersome for that particular committee. Maybe because none of us were too familiar with wikis at the time! I would definitely try to create a wiki for future committee work. Having the collaborative editing ability for committee documents and being able to brainstorm new ideas I believe will work better than email for our future committees.
  

Given another year I think I will be amazed at the wikis created at VBPL to streamline work and interact with the customers!!

Wikis
Library 2.0
Libraries