Goal: Create a Library Advisory WIKI as accessible location to post information, policies, programming news, discussion and collaboration around library issues. Contributors will be Library Advisory Board, and Administrators, and information resources will be marketed to and available for all staff.
Rationale: Increased workflow issues [e.g. difficulties finding compatible time for all parties to meet]for staff collaboration around library programming and policies has precluded regular meetings of the Library Advisory Board this year. A WIKI may provide a forum needed to ensure that our facility and staffing is meeting the needs of the school community.
Tool: Wikispaces or PBWiki. Both of these social software tools are free online, and permit hyperlinking to additional pages, uploading of files and images, creation of subpages for various topics. ?are they searchable?
Steps:
- Investigate pros and cons of both tools – experiment with set-ups
- find specific examples and screen shots
- Design the format and explicitly state objectives
- Propose and discuss with administrators – show examples of use of software
- Invite membership
Challenges:
Finding the time to set up and frame this endeavor will be a challenge, but I hope to have the site up and running by the beginning of January. Persistence in engaging committee members in participation may be problematic. Finding time to maintain and create a dynamic compelling space will also be a challenge.
I used the following examples of successful use of wikispaces when I did an inservice on wikis earlier this month:
Follow-through and maintenance: This project is experimental, but it may have a side benefit of creating a certain comfort level among participating staff, so that they begin to see the possibilities for student use of social software for collaboration and creating new knowledge.
Comments (1)
Michelle said
at 8:54 am on Dec 18, 2007
This is a wonderful use of a wiki. Wikis are great for staff collaboration. I like that you have already included the thought that this may reduce some technology anxiety among staff that use the tool. Then, they can be your advocates, and spread the word about wikis to other teachers in your school.
You worry about the committee finding time to contribute. If contribution is seen as an expectation, like attending a regular meeting would be, this may be less of a problem. You can present it in such a way that they will see this as a benefit. Not having in person meetings means that they can do committee work on their own time.
You don't have permission to comment on this page.