My comments from Week 4:
http://magpie-maggiemagpie.blogspot.com/2010/09/week-4-readings-data-compression.html?showComment=1285441492647#c3462572571925146573
Comment: I agree with you that the Imaging Pittsburgh project is absolutely fascinating! Just to imagine, all of that valuable and historic information compiled into one main location and organized in such a way that people can access it with ease. That's a true accomplishment, and I think it's also a wonderful example of the positive side of digitizing and joint efforts among local organizations to made information more readily accessible for the public.
http://kel2600.blogspot.com/2010/09/reading-notes_21.html?showComment=1285441918807#c1999784109565130149
Comment: I agree with you on the use of YouTube...the possibilities really are endless. YouTube is such a familiar thing with such a wide range of people, and so I think it can be used in some pretty neat and interactive ways. If people see the public library as a place that promotes and utilizes technology to better reach people and serve the community, the chances of survival (I think at least) are quite good. It's amazing how far-reaching something as simple as a short video can be in our world today.
-Rachel Nard
Saturday, September 25, 2010
Unit Four: Reading Notes
Data Compression (wikipedia)
So basically, my understanding of data compression is this: a complicated process of encoding information so that it takes up less hard disk space and is less to store in general. In the end, compressed data takes up less space because it uses fewer bits, or units of information, than an unencoded piece of information. It might seem like I am repeating the wikipedia entry, but I'm really just trying to wrap my mind around this concept and the process of data compression. This is all very new information for me, so I am hoping it makes a bit more sense and becomes more of a concrete concept post-lecture. One core question I have about this would be: is most data actually compressed? What kinds of resources are needed to compress and decompress data? Right now, this just seems like some sort of abstract concept, and something I am having difficulty understanding fully, because I really have no previous knowledge with which I can contextualize the process.
Data Compression Basics:
This article I found to be very, very helpful in understanding the ins and outs of data compression. While some sections are a bit confusing (i.e. when the author goes into specifics about pixels and compressing data for certain colors) his likening the concept of compression to examples of this is everyday language, really helped clarify data compression significantly. An example of this would be RGB as an acronym for Red Green Blue. Like data compression, the person reading the acronym cannot be translated into the uncompression version just using the acronym. Like data compression, the person reading the acronym cannot translate it into its uncompressed version just by using the acronym itself. This would make no sense. Rather, the person must match the acronym with the uncompressed version(s) in order to discern the meaning of the acronym itself. So, you have to know a little bit about what the acronym stands for, or be able to match the acronym with the origninal data to figure out the actual meaning. These sections of this article make a lot more sense than the wikipedia article (though some parts are still unclear) because the language is much more accessible and less technical. The information on dictionary algorithms is also very clear, and the examples using the phrase "The Flying Spaghetti Monster" that uses length-distance pair (sliding window algorithm) further illustrated this concept. Lossy compression is also made clear here: the concept that we are focusing on preserving meaning, not actual data in its original form. This essentially reduces the amount of data needed to convey specific meaning.
Imaging Pittsburgh, by Edward. A Galloway:
What a great project with such potential to provide the public access to rich information. I had heard of this initiative, but was not aware of the depth and breadth of this project prior to reading more about it here. What's particularly interesting and really great about the organization of the images, is just how user-friendly it appears to be. It has been set up in such a way that keyword searches are possible, and one can also sift through the different collections according to theme, place, etc. This at least seems to be a good example of the positive outcomes of digitizing, and the good things that can result when collections are pulled together and synthesized. Likewise, it is easy to detect the inherent challenges that come with collaboration among such a diverse group of institutions and organizations. Identifying metadata that represents what each insitutions wants and needs is also quite perplexing. I'd be interested in hearing more about this process specifically, because even something as seemingly simple as selecting vocaulary to use for subject headings, would quickly become a complicated discussion.
Youtube and Libraries:
I think many types of libraries have really taken advantage of the communication benefits of Youtube. Using these kinds of Web 2.0 tools makes for a very interactive online environment for library users to enjoy and learn from, making the library an appealing and information-rich space. An example of this would be a public library using a Flipcam to review picture books, uploading these videos, and embedding them on the library's children/youth services blogspot. Kids and adults alike can view the videos, and maybe discover an interesting title that they'd like to check out in more depth. Really, the potential of YouTube and other web tools to make the library an exciting, interactive, and user-friendly space is huge.
-Rachel Nard
So basically, my understanding of data compression is this: a complicated process of encoding information so that it takes up less hard disk space and is less to store in general. In the end, compressed data takes up less space because it uses fewer bits, or units of information, than an unencoded piece of information. It might seem like I am repeating the wikipedia entry, but I'm really just trying to wrap my mind around this concept and the process of data compression. This is all very new information for me, so I am hoping it makes a bit more sense and becomes more of a concrete concept post-lecture. One core question I have about this would be: is most data actually compressed? What kinds of resources are needed to compress and decompress data? Right now, this just seems like some sort of abstract concept, and something I am having difficulty understanding fully, because I really have no previous knowledge with which I can contextualize the process.
Data Compression Basics:
This article I found to be very, very helpful in understanding the ins and outs of data compression. While some sections are a bit confusing (i.e. when the author goes into specifics about pixels and compressing data for certain colors) his likening the concept of compression to examples of this is everyday language, really helped clarify data compression significantly. An example of this would be RGB as an acronym for Red Green Blue. Like data compression, the person reading the acronym cannot be translated into the uncompression version just using the acronym. Like data compression, the person reading the acronym cannot translate it into its uncompressed version just by using the acronym itself. This would make no sense. Rather, the person must match the acronym with the uncompressed version(s) in order to discern the meaning of the acronym itself. So, you have to know a little bit about what the acronym stands for, or be able to match the acronym with the origninal data to figure out the actual meaning. These sections of this article make a lot more sense than the wikipedia article (though some parts are still unclear) because the language is much more accessible and less technical. The information on dictionary algorithms is also very clear, and the examples using the phrase "The Flying Spaghetti Monster" that uses length-distance pair (sliding window algorithm) further illustrated this concept. Lossy compression is also made clear here: the concept that we are focusing on preserving meaning, not actual data in its original form. This essentially reduces the amount of data needed to convey specific meaning.
Imaging Pittsburgh, by Edward. A Galloway:
What a great project with such potential to provide the public access to rich information. I had heard of this initiative, but was not aware of the depth and breadth of this project prior to reading more about it here. What's particularly interesting and really great about the organization of the images, is just how user-friendly it appears to be. It has been set up in such a way that keyword searches are possible, and one can also sift through the different collections according to theme, place, etc. This at least seems to be a good example of the positive outcomes of digitizing, and the good things that can result when collections are pulled together and synthesized. Likewise, it is easy to detect the inherent challenges that come with collaboration among such a diverse group of institutions and organizations. Identifying metadata that represents what each insitutions wants and needs is also quite perplexing. I'd be interested in hearing more about this process specifically, because even something as seemingly simple as selecting vocaulary to use for subject headings, would quickly become a complicated discussion.
Youtube and Libraries:
I think many types of libraries have really taken advantage of the communication benefits of Youtube. Using these kinds of Web 2.0 tools makes for a very interactive online environment for library users to enjoy and learn from, making the library an appealing and information-rich space. An example of this would be a public library using a Flipcam to review picture books, uploading these videos, and embedding them on the library's children/youth services blogspot. Kids and adults alike can view the videos, and maybe discover an interesting title that they'd like to check out in more depth. Really, the potential of YouTube and other web tools to make the library an exciting, interactive, and user-friendly space is huge.
-Rachel Nard
Friday, September 24, 2010
muddiest point for 9/20
The information in the lecture was very clear, and so I really have no muddiest point for the lecture on 9/20. Thanks!
Thursday, September 23, 2010
URL for Assignment 2, flickr project
Hello--here is the link for assignment 2, flickr project. :)
http://www.flickr.com/photos/rachelcatherine87/
http://www.flickr.com/photos/rachelcatherine87/
Saturday, September 18, 2010
Blog comments: links, due 9/18/10
Comment:
While I was able to take away a basic understanding of Mac OS X from this article, I still feel (like many!) that I am missing a lot of information about Macs. I suppose if I were more familiar with Macs in general, I would be able to pick up on more of the details presented in the article. I still found the information helpful, though, and I'll be curious to reread the article after listening to the lecture on software. Understanding technical language and details often takes a few reads, and I've noticed that diagrams do really make a significant difference as they provide helpful visual representation.
Link to above comment:
Comment:
Aimee, I had a similar reaction to the article on Linux. While I had heard of this operating system, I had no idea just how complicated its history is and how popular the operating systems seems to be among a fairly large population of users. The whole idea of an open-source software initially seems like a really remarkable one that has the potential to generate lots of terrific ideas and launching points for discussion among computer users. However, I also wondered about the possible safety/security issues surrounding open source software programs...are there any security risks surrounding this type of software? I'm not especially familiar with this topic, so I am anxious to learn more about the details surrounding open-source software in general. The article makes Linux sound quite safe, but I'm still curious to learn more about this and what (if any) risks exist.
Link to comment:
Comment:
Doug, I also got a similar impression about Bill Veghte's attentiveness to customer service and overall satisfaction. As a Windows user, it was helpful to read this letter and understand a bit more about the operating systems themselves, including the efforts to have the different systems share a similar, basic structure upon which to build different functions for the user's convenience. I'll be curious to hear how others felt about his customer service tone in this document. This letter is a good example of the importance of individual customer satisfaction, and how this ultimately affects so many different facets of a company.
Link to comment:
Comment:
Anthony, I'm curious to hear a bit more about Windows 7. I am currently using Vista, and I have yet to explore this most recent update from Windows. What are the advantages of Windows 7? Are there specific aspects you find to be more user-friendly? I'd be interested in hearing more about this, if there are any details you'd like to share!
Link to comment:
-Rachel Nard
Friday, September 17, 2010
Reading Notes, Unit 3: Computer Software
Introduction to Linux
On many occassions thus far in library school, I have heard of Linux and its many advantages over systems such as Microsoft Office. Tuly, up until reading this document, I did not fully understand the history of this software or the significance Open Source software has on present-day software building companies. I'd be curious to hear more about this current day scenario, and the future of software creating with the seemingly endless flexibility and opportunity to wok on Open Source initiatives.
Mac OS X
The articles/wiki pages for Mac OS X were quite interesting. Their contents opened up a whole new subject to delve into more deeply after this next class, as I am interested in learning more about operating systems and software, but have very little background in this area. I plan to return to these articles and re-reading them after class, because some of the more technical language was difficult to understand completelly, since I have limited prior knowledge of this subject. On another note, the "Layers" diagram in "What is Mac OS X?" provided a good visual sense of the different pieces of software that form Mac OS X. Visuals such as this one really help to explain concepts that are unfamiliar and at times difficult to understand. I am not especially familiar with Macs, so I found the information on available software (i.e. Aqua) and similar aspects to be very engaging and informative. The speech interface is something about which I'd be interested in learning more in the future. I think much of the terminology and language will be clearer after the next lecture.
An Update on the Windows Roadmap
The core idea I pulled from this article is the issue of incompatibility of operating systems. Windows 7 is made to reflect much of the design of Vista, so as to avoid problems with compatibility and function. Does anyone have any thoughts of Windows 7 in relation to Vista?
-Rachel Nard
On many occassions thus far in library school, I have heard of Linux and its many advantages over systems such as Microsoft Office. Tuly, up until reading this document, I did not fully understand the history of this software or the significance Open Source software has on present-day software building companies. I'd be curious to hear more about this current day scenario, and the future of software creating with the seemingly endless flexibility and opportunity to wok on Open Source initiatives.
Mac OS X
The articles/wiki pages for Mac OS X were quite interesting. Their contents opened up a whole new subject to delve into more deeply after this next class, as I am interested in learning more about operating systems and software, but have very little background in this area. I plan to return to these articles and re-reading them after class, because some of the more technical language was difficult to understand completelly, since I have limited prior knowledge of this subject. On another note, the "Layers" diagram in "What is Mac OS X?" provided a good visual sense of the different pieces of software that form Mac OS X. Visuals such as this one really help to explain concepts that are unfamiliar and at times difficult to understand. I am not especially familiar with Macs, so I found the information on available software (i.e. Aqua) and similar aspects to be very engaging and informative. The speech interface is something about which I'd be interested in learning more in the future. I think much of the terminology and language will be clearer after the next lecture.
An Update on the Windows Roadmap
The core idea I pulled from this article is the issue of incompatibility of operating systems. Windows 7 is made to reflect much of the design of Vista, so as to avoid problems with compatibility and function. Does anyone have any thoughts of Windows 7 in relation to Vista?
-Rachel Nard
Wednesday, September 15, 2010
Muddiest Point for 9/13
All of the information presented in the lecture on September 13 was very clear, and so I do not have many questions for this week's muddiest point. However, I would I could use some clarification on backup of one's computer. Is it generally better to back up information using a device such as a flashdrive, or an external hard drive?
-Rachel Nard
-Rachel Nard
Wednesday, September 8, 2010
Week 2: Moore's Law, PC hardware, etc.
Personal Computer Hardware (Wikipedia)
I found this Wikipedia entry to be extremely helpful and informative. There are lots of great details covered in the information presented, and it is all very user-friendly and easy to understand. There were many components of a PC that were very familiar, and there were also those detailed workings that I had never heard of prior to reading this entry. It seems as though this would be a rich resource to use when finding supplemental materials for a program, workshop, or lesson plan (i.e. at the high school library level).
Moore’s Law (Wikipedia) and What is Moore’s Law? (video)
I found all of the information presented here to be very helpful and insightful. I had heard of this law before in another course, but I was not aware of the amount of detail surrounding it. The rapidity of obsolescence and the rate at which technology is growing is both intriguing and a bit unsettling for libraries already in a budget crunch. It seems almost impossible to keep up with, but I’m sure we’ll continue to see how this all pans out in the very near future. Also, having access to other, related laws as posted on the Wikipedia page was also very useful for comparison points. Still, there was a lot of information to process, and a great amount of detail as well. I’ll be curious to hear more about this during class.
Computer History Museum
What a neat initiative! I thought this was really interesting and conveyed lots of very engaging information. I think this website could be used to effectively supplement a lesson on the topic since the content is presented in such a fun, interactive manner. For example, the “This Day in History” calendar section could be used in an online scavenger hunt or web quest. I do have to wonder, though, about the rapidly changing nature of technology and how it will impact museum updates. Any thoughts?
-Rachel Nard
I found this Wikipedia entry to be extremely helpful and informative. There are lots of great details covered in the information presented, and it is all very user-friendly and easy to understand. There were many components of a PC that were very familiar, and there were also those detailed workings that I had never heard of prior to reading this entry. It seems as though this would be a rich resource to use when finding supplemental materials for a program, workshop, or lesson plan (i.e. at the high school library level).
Moore’s Law (Wikipedia) and What is Moore’s Law? (video)
I found all of the information presented here to be very helpful and insightful. I had heard of this law before in another course, but I was not aware of the amount of detail surrounding it. The rapidity of obsolescence and the rate at which technology is growing is both intriguing and a bit unsettling for libraries already in a budget crunch. It seems almost impossible to keep up with, but I’m sure we’ll continue to see how this all pans out in the very near future. Also, having access to other, related laws as posted on the Wikipedia page was also very useful for comparison points. Still, there was a lot of information to process, and a great amount of detail as well. I’ll be curious to hear more about this during class.
Computer History Museum
What a neat initiative! I thought this was really interesting and conveyed lots of very engaging information. I think this website could be used to effectively supplement a lesson on the topic since the content is presented in such a fun, interactive manner. For example, the “This Day in History” calendar section could be used in an online scavenger hunt or web quest. I do have to wonder, though, about the rapidly changing nature of technology and how it will impact museum updates. Any thoughts?
-Rachel Nard
Friday, September 3, 2010
Muddiest Point, week 1
There were lots of interesting points brought up during the first class, and in the first blog posts. Discussion about technology always seems to bring up interesting conversation. I suppose keeping up with the latest technology despite budget cuts and financial troubles would be the point I'm most curious to exlplore right now. It's really a quite complex issue, because on one hand, technology can make information seeking/retrieval so much more convenient. And yet, investing in the latest technology is usually incredibly expensive and might provide immediate gratification, but isn't always the best long-term investment since products and tools are constantly changing. So, how do we implement tech advances in ways that aren't detrimental to a library's already slim budget? Should we keep to more basic technology, or should we incorporate the latest tools into programming/library services?
Subscribe to:
Posts (Atom)