https://www.blogger.com/comment.g?blogID=4736393327020365268&postID=2203647811983901997&page=1
https://www.blogger.com/comment.g?blogID=5522596475792783454&postID=843628908685937135&page=1
Friday, September 26, 2008
Thursday, September 25, 2008
Week 6 Readings and Muddiest Point
Wikipedia: Local area networks
Once again, having little knowledge in this area, I found this Wikipedia piece on LANs rather helpful. I now know what type of computer network I use on a regular basis.
Wikipedia: Computer network
This was also easy to understand, which I appreciate. I do think I was a bit confused about MANs still. I guess I don't understand who uses MANs.
YouTube:
This video on common types of computer networks was short and easy to process. I thought the guy did a nice job explaining things. Watching this was a nice change as opposed to reading another article.
RFID:
I was excited to read this article because RFID's have been a hot topic with my circle of friends for years now. I never considered the use of RFID's in libraries before, but being opposed to their use, when I was reading this article, I often found myself cringing. I can see how they could be useful though in some aspects. And the author is right, despite our personal viewpoints, we probably have very little say in whether we use these devices or not. Since libraries would need RFID's for very specific purposes, and since they would get used repeatedly, I wonder how much such technology will cost libraries in the end.
Muddiest Point:
My experience with streaming is that often the video or song or whatever has to stop several times until it receives the rest of the information. Is this something that can be improved upon, or is it something viewers have to deal with?
Once again, having little knowledge in this area, I found this Wikipedia piece on LANs rather helpful. I now know what type of computer network I use on a regular basis.
Wikipedia: Computer network
This was also easy to understand, which I appreciate. I do think I was a bit confused about MANs still. I guess I don't understand who uses MANs.
YouTube:
This video on common types of computer networks was short and easy to process. I thought the guy did a nice job explaining things. Watching this was a nice change as opposed to reading another article.
RFID:
I was excited to read this article because RFID's have been a hot topic with my circle of friends for years now. I never considered the use of RFID's in libraries before, but being opposed to their use, when I was reading this article, I often found myself cringing. I can see how they could be useful though in some aspects. And the author is right, despite our personal viewpoints, we probably have very little say in whether we use these devices or not. Since libraries would need RFID's for very specific purposes, and since they would get used repeatedly, I wonder how much such technology will cost libraries in the end.
Muddiest Point:
My experience with streaming is that often the video or song or whatever has to stop several times until it receives the rest of the information. Is this something that can be improved upon, or is it something viewers have to deal with?
Sunday, September 21, 2008
Assignment #3
Here's the URL to Assignment #3. My three subjects were: digital libraries, open access, and preservation.
http://www.citeulike.org/user/dsouthwo
http://www.citeulike.org/user/dsouthwo
Thursday, September 18, 2008
Comments Week 5
https://courseweb.pitt.edu/webapps/portal/frameset.jsp?tab_id=_2_1&url=%2Fwebapps%2Fblackboard%2Fexecute%2Flauncher%3Ftype%3DCourse%26id%3D_9047_1%26url%3D
https://www.blogger.com/comment.g?blogID=271112965323219834&postID=1460070060082134105&page=1
https://www.blogger.com/comment.g?blogID=271112965323219834&postID=1460070060082134105&page=1
Week 5 Reading Notes & Muddiest Point
Wikipedia:
This definition of data compression was difficult for me to get through. Perhaps if you had a more clear view of what was being discussed first it wouldn't be so hard to follow.
Data Compression Basics:
I found this piece, while extremely lengthy (as the warning indicated), was much easier to digest than the Wikipedia definition. The wording was much easier to get through. I thought the lessy data compression was interesting. How it's more preserving the meaning, than the data.
Imaging Pittsburgh:
This article was interesting to me. I really enjoyed reading about some of the difficulties they experienced. The idea of despite the e-mail set-up, website for posting, and monthly meetings, they still had difficulty communicating. The was likely due to several factors, but I wondered if maybe it wasn't because they were doing most of their communication via the Internet. While an amazing tool, I'm not sure how well I could work with a variety of people over emails and postings. I guess I'll find out in some of my classes, but I think more face-to-face time may have improved the communication problems they experienced.
UTube and Libraries:
I don't disagree that UTube could be used to draw more patrons to a library, but I'm not sure the author of this article actually came up with anything very exciting or different to try. It wasn't very convincing of how necessary UTube is, probably because at this point, it's not. If there had been a truly unique idea, I may have agreed with her.
Muddiest Point:
What I found interesting and a bit confusing was that there is no metadata standard schema. I would think there would be one basic schema that all or most metadata schemas were based upon. Is there one that exists and I took notes wrong, or are there multiple schemas that metadata can use?
This definition of data compression was difficult for me to get through. Perhaps if you had a more clear view of what was being discussed first it wouldn't be so hard to follow.
Data Compression Basics:
I found this piece, while extremely lengthy (as the warning indicated), was much easier to digest than the Wikipedia definition. The wording was much easier to get through. I thought the lessy data compression was interesting. How it's more preserving the meaning, than the data.
Imaging Pittsburgh:
This article was interesting to me. I really enjoyed reading about some of the difficulties they experienced. The idea of despite the e-mail set-up, website for posting, and monthly meetings, they still had difficulty communicating. The was likely due to several factors, but I wondered if maybe it wasn't because they were doing most of their communication via the Internet. While an amazing tool, I'm not sure how well I could work with a variety of people over emails and postings. I guess I'll find out in some of my classes, but I think more face-to-face time may have improved the communication problems they experienced.
UTube and Libraries:
I don't disagree that UTube could be used to draw more patrons to a library, but I'm not sure the author of this article actually came up with anything very exciting or different to try. It wasn't very convincing of how necessary UTube is, probably because at this point, it's not. If there had been a truly unique idea, I may have agreed with her.
Muddiest Point:
What I found interesting and a bit confusing was that there is no metadata standard schema. I would think there would be one basic schema that all or most metadata schemas were based upon. Is there one that exists and I took notes wrong, or are there multiple schemas that metadata can use?
Monday, September 15, 2008
Saturday, September 13, 2008
Friday, September 12, 2008
Readings & Muddiest Point Week 4
Readings:
Wikipedia Database:
Having spent little time dwelling on anything computer related, I found the Wikipedia definition of a database fairly easy to read. It does often surprise me that computer terms have been around for as long as they have. The idea that the term "database" existed in 1963 blows my mind. I also find it amusing how things we have in physical formats, like indexes, are often made in electronic format to simplify computers. So now indexing actually increases a databases speed.
Intro. to Metadata
Metadata is a term that I was unfamiliar with until reading this article. Personally, I thought this piece was quite interesting. It seems like metadata makes the lives of information professionals quite a bit more easy. I like the idea that it reaffirms how important it is to maintain collections in digital libraries and virtual museums.
Dublin Core Data Model
This brief overlook of the Dublin Core Model was at times overwhelming. I really liked how they broke down what they were trying to say and gave examples. I'm still not sure I understood exactly what I was reading about, but the examples made it seem like I had some idea. Sometimes, especially with this subject matter, an idea is all I can hope for.
Muddiest Point:
For me the muddiest point this week was what an embedded operating system is. I understand that they're usually on PDAs and other small devices and that they're considered a scaled-down version of Windows, so I guess I'm wondering are they just searching devices for PDAs? The same thing that a PC has, but on a much smaller scale, or am I off track completely?
Wikipedia Database:
Having spent little time dwelling on anything computer related, I found the Wikipedia definition of a database fairly easy to read. It does often surprise me that computer terms have been around for as long as they have. The idea that the term "database" existed in 1963 blows my mind. I also find it amusing how things we have in physical formats, like indexes, are often made in electronic format to simplify computers. So now indexing actually increases a databases speed.
Intro. to Metadata
Metadata is a term that I was unfamiliar with until reading this article. Personally, I thought this piece was quite interesting. It seems like metadata makes the lives of information professionals quite a bit more easy. I like the idea that it reaffirms how important it is to maintain collections in digital libraries and virtual museums.
Dublin Core Data Model
This brief overlook of the Dublin Core Model was at times overwhelming. I really liked how they broke down what they were trying to say and gave examples. I'm still not sure I understood exactly what I was reading about, but the examples made it seem like I had some idea. Sometimes, especially with this subject matter, an idea is all I can hope for.
Muddiest Point:
For me the muddiest point this week was what an embedded operating system is. I understand that they're usually on PDAs and other small devices and that they're considered a scaled-down version of Windows, so I guess I'm wondering are they just searching devices for PDAs? The same thing that a PC has, but on a much smaller scale, or am I off track completely?
Friday, September 5, 2008
Week 3 Readings
The intro to Linux was actually fairly easy to read. I'm not at all well-read in computers, so it was a nice surprise to actually understand the majority of what it said. Also, I think it's pretty neat how a college student decided he wanted something made, and he actually made it.
As far as the MAC OS X information, that section was completely over my head. I have no background with Macs and was completely lost on what was being said. The Wikipedia section was more easy to comprehend, but it was a lot of information to digest.
I like the letter about Windows Vista. Having used this, it was reassuring to see that they are listening to user complaints and attempting to correct them. The part about enhanced security was especially nice to read about.
As far as the MAC OS X information, that section was completely over my head. I have no background with Macs and was completely lost on what was being said. The Wikipedia section was more easy to comprehend, but it was a lot of information to digest.
I like the letter about Windows Vista. Having used this, it was reassuring to see that they are listening to user complaints and attempting to correct them. The part about enhanced security was especially nice to read about.
Muddiest Point- Comments on Classmate's Blogs
Links to Comments on Classmate's Blogs:
https://courseweb.pitt.edu/webapps/portal/frameset.jsp?tab_id=_2_1&url=%2Fwebapps%2Fblackboard%2Fexecute%2Flauncher%3Ftype%3DCourse%26id%3D_9047_1%26url%
https://www.blogger.com/comment.g?blogID=1128670142701200699&postID=1115614067049066208&page=1
Muddiest Point Week 2:
I was a little miffed about what a binary system is. Is it just something that reads codes? Or does it make codes up?
https://courseweb.pitt.edu/webapps/portal/frameset.jsp?tab_id=_2_1&url=%2Fwebapps%2Fblackboard%2Fexecute%2Flauncher%3Ftype%3DCourse%26id%3D_9047_1%26url%
https://www.blogger.com/comment.g?blogID=1128670142701200699&postID=1115614067049066208&page=1
Muddiest Point Week 2:
I was a little miffed about what a binary system is. Is it just something that reads codes? Or does it make codes up?
Subscribe to:
Posts (Atom)
