There are lots of different ways that libraries can use podcasts, some of which I have direct experience in.
Over the summer, I worked at the Consumer Electronics Association (CEA) as a reference librarian. Every day, a newsletter was published of the top electronic stories, called Smartbrief, and was e-mailed to internal and external customers. The library, along with other departments, took turns making audio posts of these newsletters for those unable to read the print-version. It involved taking all of the stories and figuring out which to keep, and which to take out. It also required you to prepare a script and decide exactly what you were going to say before you started recording. Luckily, CEA had lots of professional equipment, so the podcasts came out sounding very nice – although we did use Audacity, as well, to edit them.
Libraries can use podcasts for other things too, such as a spotlight on a new database/resource or a list of upcoming events. They can also do interviews with other librarians and staff members. The possibilities are endless. I do think that whatever information is presented in the podcast should be duplicated somewhere else in written form. For instance, if a library did create a podcast of upcoming events or highlighted a database, they should also put these somewhere on the website for others to see. While podcasts can help reach a larger audience, it is important to remember that not everyone is able to (or wants to) play audio files to listen to information.
Podcasts are definitely beneficial to libraries, but it is important to recognize that they take a LOT of work. A podcast may only take 3 minutes to listen to, but at the minimum, may take an hour (or more) to create when you factor in researching, scripting, recording, and editing, and publishing. The podcasts for CEA were about 4-7 minutes in length and took me about 2 hours from start-to-finish to create. Management must understand that podcasts are valuable, but take a lot of time and are not just a “five minute procedure”. I compare it a lot to technical writing, which I used to do. Instructions may take someone two or three minutes to read through, but a document could take hours or days to write!
Another drawback/consideration to podcasts is that audio files take up a lot more space than a basic webpage. It is important the library understand their resources available and understand if they are able to host the files without a problem.
Another drawback/consideration to podcasts is that audio files take up a lot more space than a basic webpage. It is important the library understand their resources available and understand if they are able to host the files without a problem.