Weekly Readings: RSS and Mashups
I don’t have many comments on this week’s readings but some interesting things that popped up that were new or interesting to me were:
In 7 Things you Should Know About RSS it was pointed out that it is almost impossible to gauge the impact that the syndication of materials through RSS feeds is having because it is very difficult to track the usage of RSS feeds. I know when I add a feed to my Bloglines reader, it will tell me how many subscribers there are to that feed, but I’m sure that is only those who subscribe through Bloglines. As we know, there are many other feed readers out there. As librarians we want to measure the impact we’re having but this is an area where we cannot yet do that in a quantifiable way.
I liked some of the uses for RSS feeds outlined by Randy Reichardt in Success Story: RSS Moves into the Mainstream at the University of Alberta Libraries. A professor getting an entire list of new books at the library would be quickly put off, but the fact that he or she could limit their feed to the second level of an LC classification is a great feature. The worst thing we could do is add to people’s information overload. We need to, as Reichardt did, allow customization so that people can get just the information they need. This leads me to the intriguing idea of Yahoo! Pipes . I know that Amena has given them a try and Amanda has warned us that they can be tricky, but idea behind them is so exciting to me. Customization is the weapon we can use against information overload!
Another article on ease of use, Melissa Rethlefsen’s video of how to add RSS feeds to library websites, made the process seem very simple. The promise of Web 2.0 technology is that it should be simple to use. Sometimes that is true, but often it is not. This is a case in which is seems it might be.
In Programming Skills Could Transform Librarians’ Roles, David Stuart tells us we need to not only be familiar with new technologies, but that we need to go beyond that and learn programming skills. Either I haven’t taken the right technology courses, or the MLIS program has not yet bought into this idea because this is not a skill that I am going to possess by the time I finish this program (in a few weeks time). My philosophy has been that I want to learn how things work and what is possible so that I can interact with the IT department at my library in an intelligent way. I will know what is possible, but not have to do it myself. Now, it’s debatable if I’ve achieved that skill, but that is still a far cry from what Stuart is advocating.