For this assignment, playtime was a lot of fun, if not a challenge to GET to. Google and Explorer were not playing nicely and not letting me into Blogger to view the 23 Things page NOR this blog, so I had to...get creative. Haha, I have persevered over technology with the help of a kind coworker, and here I am. Again, go me.
Ok, playing in the sandbox WAS fun. I liked reading what the others have added to the Learning 2.0 Wiki, especially the Favorite Restaurants. Now, I will make the small complaint that I didn't see detailed instructions on the Favorite Blogs page to tell me how to add my blog to the list, and only figured it out because, thankfully, the editing page is very similar to other types of editing pages, including the one I'm typing on right now. I made additions to the Favorite Restaurants page bc I actually had one to rec, and to the very lonely and EMPTY Favorite Wikis.
It was all very easy to do, and went much more quickly than I'd anticipated. I can see where a collaborative project like this can run so much more smoothly when you don't have to rely on one person to do all the updating, or to wait for meetings for a consensus to form before moving forward.
Come on, SPPL! Let's get some more links on that wiki!
Showing posts with label wikis. Show all posts
Showing posts with label wikis. Show all posts
Saturday, December 22, 2007
Friday, December 21, 2007
Thing #19: Wikis!
This was one of the most informative "Things" I've done in this project--I really learned a lot, and also realized that I was greatly under-informed about what exactly wikis are, who uses them, and how.
I'd also like to give my appreciation to the Wikis in Plain English video from commoncraft.com. I love the style of these little vids, and it really helped me to visualize and understand the concepts behind both wikis and back in the social bookmarking exercise. Good choice!
I really like the idea of a wiki, particularly in a library environment. For the staff, it provides an easily-accessible way for staff to communicate and collaborate on projects, staying up to date, and can be done from any location in or out of the library. It could be a huge benefit for system-wide committees or project, reducing the number of face-to-face meetings.
In the public realm, I LOVE how a wiki could bring a sense of investment in the library to patrons--where they feel not only like they are being heard, but that they are actively and positively contributing to the success, function, and mission of the library. An annotated catalog--as mentioned in Using Wikis to Create Online Communities--makes SO much sense! What a great tool to develop collaboratively between patrons and staff, and perhaps more manageable and meaningful than Amazon. (And hey, while I love Amazon, and use it often enough at work, I think anything we can do to make our catalog the FIRST--and BEST--place for patrons to look for books, the better.)
And of course, the fact that wikis are easy to use, to edit, makes them a great access point for the technologically-challenged patron and library staff member alike. In a previous position, I spent two entire summers creating web pathfinders using an annoyingly complicated web design software that required checking-in and checking-out documents, and nevertheless we never seemed to know just WHICH document was the "real" document. And the software didn't work half the time, and we had to have licenses and all that--my word, making wikis of them would have been SO much easier!
Oh, and because I'm me, I have to add in here that my favorite wiki? Wookieepedia, naturally. :-) You don't know how often I have consulted this. But man, I learned the hard way to watch out for book spoilers! I so did not want to know about a major character death 4 books ahead of where I was. *frowns*
I'd also like to give my appreciation to the Wikis in Plain English video from commoncraft.com. I love the style of these little vids, and it really helped me to visualize and understand the concepts behind both wikis and back in the social bookmarking exercise. Good choice!
I really like the idea of a wiki, particularly in a library environment. For the staff, it provides an easily-accessible way for staff to communicate and collaborate on projects, staying up to date, and can be done from any location in or out of the library. It could be a huge benefit for system-wide committees or project, reducing the number of face-to-face meetings.
In the public realm, I LOVE how a wiki could bring a sense of investment in the library to patrons--where they feel not only like they are being heard, but that they are actively and positively contributing to the success, function, and mission of the library. An annotated catalog--as mentioned in Using Wikis to Create Online Communities--makes SO much sense! What a great tool to develop collaboratively between patrons and staff, and perhaps more manageable and meaningful than Amazon. (And hey, while I love Amazon, and use it often enough at work, I think anything we can do to make our catalog the FIRST--and BEST--place for patrons to look for books, the better.)
And of course, the fact that wikis are easy to use, to edit, makes them a great access point for the technologically-challenged patron and library staff member alike. In a previous position, I spent two entire summers creating web pathfinders using an annoyingly complicated web design software that required checking-in and checking-out documents, and nevertheless we never seemed to know just WHICH document was the "real" document. And the software didn't work half the time, and we had to have licenses and all that--my word, making wikis of them would have been SO much easier!
Oh, and because I'm me, I have to add in here that my favorite wiki? Wookieepedia, naturally. :-) You don't know how often I have consulted this. But man, I learned the hard way to watch out for book spoilers! I so did not want to know about a major character death 4 books ahead of where I was. *frowns*
Subscribe to:
Posts (Atom)