Reflection #1: Revised Post

Over the past few weeks, we have been reading many works on hyperlinked libraries and foundational readings. One of the things that caught my attention during the reading was Library 2.0 A Guide to Participatory Library Service. In the book, the authors, Casey and Savastinuk, discussed how the library needed to change to meet the user’s current and potential needs, and one way to that was through the available applications. They introduced several concepts that I thought were pretty cool:

• One concept was creating a wiki for library staff. If a staff member could not perform their duties for whatever reason, they could create a list of their responsibilities that would teach their replacement how to do their jobs. What is also great about this is that as roles and responsibilities change, the staff members could also update their lists so that other staff members are adequately informed.
• Another concept had a library blog that anyone–staff or user–could use to communicate with each other. This blog could be used externally so that the public got to know the library better and kept informed on the comings and goings around the library. Furthermore, library users can “be notified of new information or content” (Casey & Savastinuk, 2007, p. 85) with a blog’s RSS feed, making it easier for them to stay informed even if they do not revisit the blog. This blog could also be used internally, allowing staff members to be able to communicate with each other on an asynchronous basis–so, while two of them may work in different departments, at different times of the day/week, they will be able to communicate with each other, forming connections, and sharing ideas through the comment sections or blog posts.
• The final concept I would like to discuss is having a Top-Down blog between library staff and their boss. According to Casey and Savastinuk, “Administrators often underestimate the power of their words when it comes to workplace morale”, and a blog between the staff and their administrator would “play a very important role in improving vertical communications” (2007, pp. 81-82). It would allow the staff to send their thoughts and concerns to their superiors and would let the staff know that “their concerns are the director’s concerns, and that the issues staff are talking and worrying about are being addressed by the director” (Casey & Savastinuk, 2007, p. 82).

As far as where this reading took my thinking about library and information works, it made me think of how valuable those applications could be for the libraries in my area. While I think that the libraries are fine right now, with the applications Casey and Savastinuk mentioned, they would—in my opinion—help both them and current and potential users. With blogs, users can let staff members know what they think about the library and allow them to participate and provide any feedback they may have. Internal wikis and blogs would strengthen communication between staff, which would help keep the library operations running smoothly and efficiently. Finally, a Top-Down blog between the staff and administrator would allow staff to voice their concerns to their superior without worry and allow the administrator to keep staff up to date on current proceedings and updates.

Reference

Casey, M. E., & Savastinuk, L. C. (2007). Library 2.0: A guide to participatory library service. Medford, N.J: Information Today. https://287.hyperlib.sjsu.edu/wp-content/uploads/2019/07/Library2.0Text.pdf