Collection CommunicationPosted: July 5, 2011 | Author: Steven Harris | Filed under: Collection Philosophy | Tags: communication, information overload | 1 Comment »
I’ve been thinking about an issue for library collections recently. I might like to do a research project on this topic but have not pushed through the inertia to get working on it. The topic is: communication about collections. There are so many issues about library collections that require communication with a wide variety of constituents both within the library staff and in the user community. The number of issues that require communication is almost never ending. And the variety of constituents is daunting.
- Product trials
- New products
- Vendors visits
- Vendor training announcements
- New approval titles
- Renewal notices
- New product requests
- Order problems
- Fund problems
- Orders or requests (from librarians or users)
- Invoice (received or to be paid)
- Connectivity problems
- Service Outages
Some of those are entirely internal. Some are issues that we communicate outward to library staff and users. Some are issues that users communicate to us. ERMs were designed to handle some of the internal communication issues (although even at those, they don’t do a very good job), but ERMs were never intended to be the means of pushing out the entire gamut of communication elements to a library community.
What can we use to meet all these communication needs? I’ve been pondering that for my own library and not come up with a good solution. Probably no one tool is right for everything. But we do have a lot more options now days. We use a lot of email discussion lists in my library, but, personally, I’d rather eat a bag of glass than be added to another listserv.
So, the number of communication tools is equally daunting:
- Text message
- Personal email
- Group email list
- Newsletter (print or electronic)
- Face to face
- Local network drive
- Course management system
- Adobe Connect
- Other Social Media
And probably 500 other things. Ideally, it would be nice if we could integrate all of this into a single system. A blog platform like WordPress might begin to do the job, but I haven’t figure out how to sort out the internal and the public. So many puzzles to solve.
What is your library using for internal and external communications about library collections issues? Help me out here!
Very Large Array: Rick Ortiz (Flickr)
telephone: FrÃ©dÃ©ric BISSON (Flickr)