This is the second time that I have started working on this post. So while I am thinking of it, I encourage you all to write your posts in Word edit it and then copy it into the Blog post. I have lost several posts that were finished or nearly finished when I was typing them directly into the blog post. I can’t even tell you exactly how I lost them, but it is during the editing process. I hit the back space key, or the delete key, or something and then voila the post is gone. And the second time around is never as good as the first.
As for Wikis, I like the idea of creating a Technical Services tip-sheet as a wiki. Department staff could post tips on such things as how to use and what to program into PF keys, how to get to a subscription record in Aleph, etc.
I considered the idea of putting the department manual in a Wiki, but have decided that a webpage or a blog would be better. This is because all the staff in the department review the procedures before they are finalized and added to the manual. If we did the manual as a wiki, then we would run the risk of having procedures added before they were reviewed.
I also thought that the librarians in cooperation with the teaching faculty could create a wiki that lists suggested summer reading for our students. Faculty could choose popular titles in their field that would not necessarily be covered in a course, but that might invigorate a student to read more in the subject. The library could post the wiki with covers of the books. Everyone would be encouraged to submit reviews, including the students. It would also be good if the library would post the call number and allow students to check the book out during the summer. We currently do not allow this, but perhaps something could be arranged for students who have pre-enrolled for the fall. Otherwise, we might have to point them to the public library.
No comments:
Post a Comment