How-To Guide: Why Screencasting Should Be Used
I thought screencasting is a great way to provide reference services at a library because it pulls together so many elements that would occur in a face-to-face reference interaction. I really enjoyed doing my screencast with Jing. I thought it was pretty intuitive and a worthwhle experience. To be fair, I regularly do screencasts for my job and find that they do help, especially since we only provide remote support (phone and email). Screencasts are perfect for a mostly digital environment and may be one of the closest things to having a person stand behind your computer while a process is explained.
1) If you are making a screencast about a topic, chances are it isn't the first time that question is asked. Nor the last time.
2) If you are not paying to host the screencast on your server and there are volunteers to make one, it is worth trying. The most that'll happen is that those who do the screencasts will do one experimental one that may or may not be shown to wide audiences.
3) If screencasts take to long, make them in shorter bits. If they are too short, make them longer. As long as the screencast clearly demonstrates the task at hand, the screencast is serving its purpose.
4) If you aren't that confortabe controlling a computer and speaking, you can have someone else man the controls while you control the audio portion of the screencast.
5) If you don't want to sound like you are talking normally during the screencast, write a script for it. Or visa versa.
6) Screencasts may reach audiences that will never walk into your library because they live too far or do not have time, but need help right away!
7) Screencasts may reach audiences that normally walk in your library--they are just audio-visual learners.
8) Screencasting is a great technology that seems a lot more "technological" than it is. It might even impress your colleagues, bosses, or help get grants.
