Sunday, November 23, 2008

Comments on other blogs

https://www.blogger.com/comment.g?blogID=986394955087168146&postID=2561384677214888667&page=1

https://www.blogger.com/comment.g?blogID=4619180577856147392&postID=852355562292541971&page=1

Friday, November 14, 2008

Muddiest Point #10

While we discussed Z39.50, I wondered why these things look so complicated. I understand that they are trying to account for everything, but I think a lot of work has been done in other fields, like computer science, to make things like this logical, simple, and relatively easy to use. Take XML and HTML for example. Even though these may not be completely intuitive, once you get the basics the logic is very simple to follow. It seems to me that many systems used in library science cannot decide if they want to be very specific or extremely flexible, or even where they want to fall in between. Perhaps because of my computer science background, this stuff often looks like a terribly unorganized mess to me. What work has been done to fix this? Or do you think that they really cannot be improved in these ways?

Reading Notes #11

Digital Libraries: Challenges and Influential Work
This is a decent little overview of some of the work that has been done in recent times to connect libraries with the digital world. There did not seem to be much content to it, though, and it seemed almost thrown together. I think a good bulleted list would have been more helpful.

Dewey Meets Turing
This article helped me to be aware of the challenges involved in combining people in the library field with those in the computer field. It also gave an idea of the attitudes of those involved in the process. I hope that librarians and computer scientists will continue to work together in the future, and I especially hope that they continue to improve HOW they work together. I am not quite so sure why, but it seems that working together for the two has been far more complicated and inefficient than necessary.

Institutional Repositories
This article was informative, but also very dense. Like the first article, but for different reasons, I wish this had been presented in a structured list or something similar, rather than as a long article. But regardless, the article does give a good overview of what an institutional repository is, how it functions, and where they are going in the future.