My collection contains books about booktalking. Here is the link to my Koha collection:
http://upitt01-staff.kwc.kohalibrary.com/cgi-bin/koha/virtualshelves/shelves.pl?viewshelf=63
My login is KDH29. The name of the list is "Huth_2600_Booktalking."
Saturday, October 30, 2010
Wednesday, October 27, 2010
Week 8 notes
1) W3schools HTML Tutorial: http://www.w3schools.com/HTML/
This was awesome to play around with! I know next to nothing about HTML, so pairing this with the cheatsheet below, I was able to play around and get a little more comfortable with it. I still couldn't figure out a number of things, such as how to make a table. But I think I have the basics. I have used W3 Schools to look up some other things about using computers, and I've always found the site helpful.
2) HTML Cheatsheet http://www.webmonkey.com/reference/HTML_Cheatsheet/
I didn't know there were so many HTML codes! This was helpful for when I was on he W3 school site. I kept referring to it the whole time. If I had to do any kind of HTML project, I would print this out and put it beside my computer for easy reference. It makes me wonder if anyone knows every single code, like a language. I guess if you build websites for a living you would. Did anyone see "The Social Network"? The people in that movie were coding like maniacs; they probably didn't need a cheat sheet. But I do!
3) W3 School Cascading Style Sheet Tutorial: http://www.w3schools.com/css/
This got more confusing that straightforward HTML, but if you really knew how it worked, it would save a ton of time. It makes me wonder if anyone uses just HTML to make websites anymore, or if pretty much everything is CSS. When would be a time you wouldn't want to use CSS? This article went way too in-depth for someone like me, who has only a basic knowledge of CSS, but I can tell it would be an excellent source if you wanted to learn CSS (as most of the W3 school sites are).
4) Goans, D., Leach, G., & Vogel, T. M. (2006). Beyond HTML: Developing and re-imagining library web guides in a content management system. Library Hi Tech, 24(1), 29-53.
Much of the language in this article was over my head, but it was interesting. It sounds like it was a huge project involving many people. It sounds like it was a big step up from the original FrontPage that had one "network coordinator" librarian in charge of it, and then the more than 100 guides -- what a searching nightmare. It was interesting reading about the reasoning behind adopting CMS technology. It also went through the process of implementing such a system, which is helpful for anyone looking to do so.
Kristen Huth
This was awesome to play around with! I know next to nothing about HTML, so pairing this with the cheatsheet below, I was able to play around and get a little more comfortable with it. I still couldn't figure out a number of things, such as how to make a table. But I think I have the basics. I have used W3 Schools to look up some other things about using computers, and I've always found the site helpful.
2) HTML Cheatsheet http://www.webmonkey.com/reference/HTML_Cheatsheet/
I didn't know there were so many HTML codes! This was helpful for when I was on he W3 school site. I kept referring to it the whole time. If I had to do any kind of HTML project, I would print this out and put it beside my computer for easy reference. It makes me wonder if anyone knows every single code, like a language. I guess if you build websites for a living you would. Did anyone see "The Social Network"? The people in that movie were coding like maniacs; they probably didn't need a cheat sheet. But I do!
3) W3 School Cascading Style Sheet Tutorial: http://www.w3schools.com/css/
This got more confusing that straightforward HTML, but if you really knew how it worked, it would save a ton of time. It makes me wonder if anyone uses just HTML to make websites anymore, or if pretty much everything is CSS. When would be a time you wouldn't want to use CSS? This article went way too in-depth for someone like me, who has only a basic knowledge of CSS, but I can tell it would be an excellent source if you wanted to learn CSS (as most of the W3 school sites are).
4) Goans, D., Leach, G., & Vogel, T. M. (2006). Beyond HTML: Developing and re-imagining library web guides in a content management system. Library Hi Tech, 24(1), 29-53.
Much of the language in this article was over my head, but it was interesting. It sounds like it was a huge project involving many people. It sounds like it was a big step up from the original FrontPage that had one "network coordinator" librarian in charge of it, and then the more than 100 guides -- what a searching nightmare. It was interesting reading about the reasoning behind adopting CMS technology. It also went through the process of implementing such a system, which is helpful for anyone looking to do so.
Kristen Huth
Week 7 muddiest point
Do we know how many libraries use Koha? It seems like a standard ILS system, and it's free. I went to their website and they had updates about site that recently chose Koha, but I was wondering just how prevalent it is. What types of libraries would find it most useful?
Monday, October 18, 2010
Assignment 4: Zotero and CiteULike
Here is my CiteULike library. My three collections in Zotero were Intellectual Freedom, Newspaper Archives and Weeding as they relate to libraries.
http://www.citeulike.org/user/kdhuth
http://www.citeulike.org/user/kdhuth
Thursday, October 14, 2010
Week 7 notes
1) Tyson, Jeff. http://computer.howstuffworks.com/internet-infrastructure.htm/printable
It is strange that we think of the Internet as a single thing, but it really is a lot of small connections. I never thought about how every computer online connects to every other.
I liked reading about routers because obviously I own one but I never really thought about its purpose. I knew it send the information where it needs to go, but I didn't know it made sure that information didn't go where it's not needed. I guess that is really important when there is such a large amount of information (as we saw illustrated in the Google video below).
I did know what an IP address and URL were (which was a relief, because a lot of the acronyms we read about for this class are new to me!). But this was a good review. I am continually, happily surprised at how concise and helpful the readings are for this class.
2) Andrew K. Pace (2004). Dismantling Integrated Library Systems. Library Journal, 129(2), p.34-36.
This article was a little bit technical for me, but I thought the CEO made an interesting comment: When building a new system, you should use the "same intellectual logic" from the original. I think that's a good rule of thumb; you can constantly tweak systems to meet the current technological needs, but the purpose and logic still have to be there.
I thought the "better costs more" part was interesting, too. Libraries do need to realize that these systems cost a ton if they expect them to do all these things. You get what you pay for! Unfortunately, libraries are dealing with a crunch on their budgets just as these technologies become more important.
3) Sergey Brin and Larry Page: Inside the Google machine.
http://www.ted.com/index.php/talks/sergey_brin_and_larry_page_on_google.html
The world graphic at the beginning of the video was awesome. It also showed the awesome reach of Google. Only Africa was mostly dark. He said that even the international space station would have a dot if it were in the map. Then the map showed the links of where in the world information was traveling -- all over. And the flash of one second of Google traffic showed the amount and variety of searches.
I think it's awesome that when one of their developers wants to do something, Google "pretty much lets them do it." You never know what the next big thing will be, and Google is making a smart move in letting its workers explore. It also keeps them happy. They "try things out for fun and see where it goes." Larry Page said something like many useful things come out of hobbies. I didn't know Google News came about that way. (I use it almost daily.)
Also, as an aside -- Brin and Page are funny! I guess I should have expected that from the guys behind Google, which is such an innovative company.
It is strange that we think of the Internet as a single thing, but it really is a lot of small connections. I never thought about how every computer online connects to every other.
I liked reading about routers because obviously I own one but I never really thought about its purpose. I knew it send the information where it needs to go, but I didn't know it made sure that information didn't go where it's not needed. I guess that is really important when there is such a large amount of information (as we saw illustrated in the Google video below).
I did know what an IP address and URL were (which was a relief, because a lot of the acronyms we read about for this class are new to me!). But this was a good review. I am continually, happily surprised at how concise and helpful the readings are for this class.
2) Andrew K. Pace (2004). Dismantling Integrated Library Systems. Library Journal, 129(2), p.34-36.
This article was a little bit technical for me, but I thought the CEO made an interesting comment: When building a new system, you should use the "same intellectual logic" from the original. I think that's a good rule of thumb; you can constantly tweak systems to meet the current technological needs, but the purpose and logic still have to be there.
I thought the "better costs more" part was interesting, too. Libraries do need to realize that these systems cost a ton if they expect them to do all these things. You get what you pay for! Unfortunately, libraries are dealing with a crunch on their budgets just as these technologies become more important.
3) Sergey Brin and Larry Page: Inside the Google machine.
http://www.ted.com/index.php/talks/sergey_brin_and_larry_page_on_google.html
The world graphic at the beginning of the video was awesome. It also showed the awesome reach of Google. Only Africa was mostly dark. He said that even the international space station would have a dot if it were in the map. Then the map showed the links of where in the world information was traveling -- all over. And the flash of one second of Google traffic showed the amount and variety of searches.
I think it's awesome that when one of their developers wants to do something, Google "pretty much lets them do it." You never know what the next big thing will be, and Google is making a smart move in letting its workers explore. It also keeps them happy. They "try things out for fun and see where it goes." Larry Page said something like many useful things come out of hobbies. I didn't know Google News came about that way. (I use it almost daily.)
Also, as an aside -- Brin and Page are funny! I guess I should have expected that from the guys behind Google, which is such an innovative company.
Wednesday, October 6, 2010
Week 6 notes
1) Local Area Network: http://en.wikipedia.org/wiki/Local_Area_Network
I am sure we have all worked on LANs. I know I have in schools and work. This article was very brief, so I was glad to get a broader overview with the next article ...
2) Computer network http://en.wikipedia.org/wiki/Computer_network
This article showed the differences in many kinds of networks. Now I will be able to differentiate what kind of network I'm using at school, work and home. I am glad it went into intranets, because I've used those at jobs I've had but never quite knew how they worked. I also liked seeing the Internet described as a network: global!
3) Common types of computer networks http://www.youtube.com/watch?v=1dpgqDdfUjQ
I didn't know that many LAN connections can now do what wide area networks used to do; things have become that advanced. I also liked how he mentioned "MANs," or metropolitan area networks. This is an interesting but useful configuration. Some small cities have tried this, and a lot of residents are probably happy. When I was getting my undergraduate at Penn State, the State College borough council discussed doing this in the downtown area. I'm not sure how far they've gotten with that plan, but I know a lot of students would appreciate it.
The video links provided so far for this class have been great: short and straightforward. I look forward to more like them!
4) Coyle, K. (2005). Management of RFID in libraries. Journal of Academic Librarianship, 31(5), 486-489.
The intro to this article was helpful for explaining exactly what RFID is. I knew what it did, but I didn't know how. (I also watched the video under the RFID discussion board, which helped, too.) The author brings up a good point about even if libraries don't embrace RFID right away, we can't ignore it. We have to educate ourselves, especially because RFID may promise a way to speed up operations. (They don't have to be scanned individually, like barcodes -- you can do stacks at a time! And I really liked the idea that the book drop can check in books automatically.) Libraries converted to barcodes eventually, and RFID adds a security measure that barcodes don't have.
I mentioned what I thought some uses might be in my discussion board post, and she hit on some of them, such as advantages in the stacks and shelving. Incorrectly shelved books may no longer we the same as losing a book.
Her problems are valid as well. Obviously privacy is an issue, but so is cost. And if not all items are deemed worthy of that cost -- like flimsy magazines -- it will be a hassle to keep the other barcode method in place.
I am sure we have all worked on LANs. I know I have in schools and work. This article was very brief, so I was glad to get a broader overview with the next article ...
2) Computer network http://en.wikipedia.org/wiki/Computer_network
This article showed the differences in many kinds of networks. Now I will be able to differentiate what kind of network I'm using at school, work and home. I am glad it went into intranets, because I've used those at jobs I've had but never quite knew how they worked. I also liked seeing the Internet described as a network: global!
3) Common types of computer networks http://www.youtube.com/watch?v=1dpgqDdfUjQ
I didn't know that many LAN connections can now do what wide area networks used to do; things have become that advanced. I also liked how he mentioned "MANs," or metropolitan area networks. This is an interesting but useful configuration. Some small cities have tried this, and a lot of residents are probably happy. When I was getting my undergraduate at Penn State, the State College borough council discussed doing this in the downtown area. I'm not sure how far they've gotten with that plan, but I know a lot of students would appreciate it.
The video links provided so far for this class have been great: short and straightforward. I look forward to more like them!
4) Coyle, K. (2005). Management of RFID in libraries. Journal of Academic Librarianship, 31(5), 486-489.
The intro to this article was helpful for explaining exactly what RFID is. I knew what it did, but I didn't know how. (I also watched the video under the RFID discussion board, which helped, too.) The author brings up a good point about even if libraries don't embrace RFID right away, we can't ignore it. We have to educate ourselves, especially because RFID may promise a way to speed up operations. (They don't have to be scanned individually, like barcodes -- you can do stacks at a time! And I really liked the idea that the book drop can check in books automatically.) Libraries converted to barcodes eventually, and RFID adds a security measure that barcodes don't have.
I mentioned what I thought some uses might be in my discussion board post, and she hit on some of them, such as advantages in the stacks and shelving. Incorrectly shelved books may no longer we the same as losing a book.
Her problems are valid as well. Obviously privacy is an issue, but so is cost. And if not all items are deemed worthy of that cost -- like flimsy magazines -- it will be a hassle to keep the other barcode method in place.
Tuesday, October 5, 2010
Week 5 muddiest point
Thanks for answering my question in class, Jiepu!
I was going to ask a question about getting updates on our blog grades, but you answered that, too. So I have no muddiest point for this week. Thanks!
I was going to ask a question about getting updates on our blog grades, but you answered that, too. So I have no muddiest point for this week. Thanks!
Saturday, October 2, 2010
Assignment 3: Jing
I did a tutorial on how to order a book from the library.
Video:
http://www.screencast.com/t/ODZkMjQ1NWIt
Annotated, screenshot instructions (the entire set is here):
1. http://www.flickr.com/photos/kdhuth/5044745302/in/set-72157624954942899/
2. http://www.flickr.com/photos/kdhuth/5044754224/in/set-72157624954942899/
3. http://www.flickr.com/photos/kdhuth/5044134843/in/set-72157624954942899/
4. http://www.flickr.com/photos/kdhuth/5044138139/in/set-72157624954942899/
5. http://www.flickr.com/photos/kdhuth/5044768894/in/set-72157624954942899/
Video:
http://www.screencast.com/t/ODZkMjQ1NWIt
Annotated, screenshot instructions (the entire set is here):
1. http://www.flickr.com/photos/kdhuth/5044745302/in/set-72157624954942899/
2. http://www.flickr.com/photos/kdhuth/5044754224/in/set-72157624954942899/
3. http://www.flickr.com/photos/kdhuth/5044134843/in/set-72157624954942899/
4. http://www.flickr.com/photos/kdhuth/5044138139/in/set-72157624954942899/
5. http://www.flickr.com/photos/kdhuth/5044768894/in/set-72157624954942899/
Subscribe to:
Posts (Atom)