Tuesday, September 28, 2010
Muddiest Point for 9-27 - 10-1
My muddiest point for this week is more of a question than a misunderstanding. Since technology is always advancing, I wonder if the various formats (GIF, JPEG, TIFF, and PNG) will always be available in the future? If not, will they be able to be converted to newer forms so that the information stored in these files can be accessible to users in the future?
Readings for 10-4 - 10-8
Database - Wikipedia Article
I have known the concept of what a database is for awhile now (ever since I began my undergraduate career.) However, I never knew that they were as complicated as they seem to be, according to the Wikipedia article. I think the most interesting aspect of databases is how they can be classified by the types of their content, which includes: bibiographic, document-text, statistical, etc. It was also the first time I had encountered the concept of database management systems (DMS), which store database contents, allowing the creation and maintainence of data, and searching and other accessing. A final concept that was new to me was the three levels of database architecture: external, internal, and conceptual. The external level is for users and how they understand the organization of the data. The internal level consists of the physical storage of data and how it is processed in the computing system. Finally, the conceptual level seems to balance the internal and external levels.
Introduction to Metadata
I never knew what metadata was until I came to the University of Pittsburgh. In general, metadata is data about data. I thought the fact that all information objects have the three features of content, context, and structure was a very important theme in understanding metadata. Content relates to what the object contains, context relates to all the informational aspects of the objects creation, and structure relates to the associations of individual objects which can be contextual, content related, or both. Probably the most important thing to understand about metadata is that it identifies and describes the object, documents how the object behaves, the objects funtion and use, its relationship to other objects, and it has been managed over time.
An Overview of the Dublin Core Data Model
It seems to me that the Dublin Core Metadata Initiative (DCMI) is a large effort to discover diverse resources in an electronic environment that spans across many different disciplines. Since this is largely an international effort, I would expect that the funding of such a large initiative would be extremely difficult as it seems to be very expensive. Some functional requirements include: internationalization, extensibility, element identity, semantic refinement, identification of encoding schemes, specification of controlled vocabularies, and identification of structured compound values. These requirements seem difficult to develope, especially since there are many obstacles to get over when the international community is involved. I think this idea would take a long time to create, but hopefully, if it does succeed, it can bring other countries and cultures together in hopes of bettering communication and figuring out solutions to many problems.
I have known the concept of what a database is for awhile now (ever since I began my undergraduate career.) However, I never knew that they were as complicated as they seem to be, according to the Wikipedia article. I think the most interesting aspect of databases is how they can be classified by the types of their content, which includes: bibiographic, document-text, statistical, etc. It was also the first time I had encountered the concept of database management systems (DMS), which store database contents, allowing the creation and maintainence of data, and searching and other accessing. A final concept that was new to me was the three levels of database architecture: external, internal, and conceptual. The external level is for users and how they understand the organization of the data. The internal level consists of the physical storage of data and how it is processed in the computing system. Finally, the conceptual level seems to balance the internal and external levels.
Introduction to Metadata
I never knew what metadata was until I came to the University of Pittsburgh. In general, metadata is data about data. I thought the fact that all information objects have the three features of content, context, and structure was a very important theme in understanding metadata. Content relates to what the object contains, context relates to all the informational aspects of the objects creation, and structure relates to the associations of individual objects which can be contextual, content related, or both. Probably the most important thing to understand about metadata is that it identifies and describes the object, documents how the object behaves, the objects funtion and use, its relationship to other objects, and it has been managed over time.
An Overview of the Dublin Core Data Model
It seems to me that the Dublin Core Metadata Initiative (DCMI) is a large effort to discover diverse resources in an electronic environment that spans across many different disciplines. Since this is largely an international effort, I would expect that the funding of such a large initiative would be extremely difficult as it seems to be very expensive. Some functional requirements include: internationalization, extensibility, element identity, semantic refinement, identification of encoding schemes, specification of controlled vocabularies, and identification of structured compound values. These requirements seem difficult to develope, especially since there are many obstacles to get over when the international community is involved. I think this idea would take a long time to create, but hopefully, if it does succeed, it can bring other countries and cultures together in hopes of bettering communication and figuring out solutions to many problems.
Thursday, September 23, 2010
Tuesday, September 21, 2010
Muddiest Point for 9-20 - 9-24
I think the muddiest point from this week that I did not completely understand was the section on Graphical User Interface (GUI). I am not exactly sure what it does and how it works.
Readings for 9-27 - 10-1
Data Compression Basics
This was the very first time I have encountered the idea of data compression. I had no previous idea that anyone could compress data into smaller bits in order to have more room for more data. This article was very helpful in explaining some of the basics involved in data compression. It was also helpful that the author did not use technical language that I would not have understood. The author was also very helpful by illustrating his ideas with examples that made a lot of sense to me. The various algorithms (run-length encoding, Lempel-Ziv, entropy, and prediction and error) were somewhat confusing, but the author made sense out of them, for the most part. I think the run-length encoding made the most sense. For example, if you have this set of data: QQQRRSSSSSSSSSSTTTTTTTTTTTTUUV, the run-length encoding algorithm would be: 3Q 2R 10S 12T 2U 1V. Therefore, it went from 30 bits of information to 19 bits (including spaces).
Data Compression - Wikipedia
The Wikipedia articla for data compression was also very useful in explaining the various aspects of data compression. The difference between "lossless" and "lossy" was very nicely explained. Basically, if the information that has been decompressed after compression is the exact same as the original information, it is lossless. On the other hand, if the information that has been decompressed after compression is not exactly the same as the original information, it is lossy. I believe this is one of the fundamental aspects of data compression. I would also assume that lossless is a better scenario to have then lossy. I wonder if there is any way possible to get the identical information back if the decompressed information comes out lossy?
Imagining Pittsburgh
I found this article to be extremely enlightening for the sole purpose of having the community of Pittsburgh understand and actually see what their city was like in previous years. I wish that every city would have the opportunity to create a website that has thousands of photographs from the past. The collaboration between the Archives Service Center of the University of Pittsburgh, Carnegie Museum of Art, and the Historical Society of Western Pennsylvania produced a useful website filled with meaningful photographs that adds to the cultural heritage of the greater Pittsburgh area. Even though there were many challenges these "partners" had to overcome, including building a working dialogue between the institutions and coming up with meaningful and helpful metadata subject headings, they successfully completed a project that can be enjoyed by many generations down the road.
You Tube and Libraries
This article was eye-opening in respect to libraries using current technology to help further their usefulness to the general public. I never thought about using You Tube videos to help public users, students, and even faculty with various functions of the library. I think there would be a great advantage to libraries across the world by using instruction-based You Tube videos. They could have videos that deal with a number of important ares including: how to use databases, how to find books in the library's online catalog, how to request inter-library loans, etc. There could also be instructional videos that new employees of the library could find useful in learning their new job responsibilities. I think that You Tube videos are a good way to make the library more useful to those who do not know how to use the resources the library offers. Plus, the accounts are free!
This was the very first time I have encountered the idea of data compression. I had no previous idea that anyone could compress data into smaller bits in order to have more room for more data. This article was very helpful in explaining some of the basics involved in data compression. It was also helpful that the author did not use technical language that I would not have understood. The author was also very helpful by illustrating his ideas with examples that made a lot of sense to me. The various algorithms (run-length encoding, Lempel-Ziv, entropy, and prediction and error) were somewhat confusing, but the author made sense out of them, for the most part. I think the run-length encoding made the most sense. For example, if you have this set of data: QQQRRSSSSSSSSSSTTTTTTTTTTTTUUV, the run-length encoding algorithm would be: 3Q 2R 10S 12T 2U 1V. Therefore, it went from 30 bits of information to 19 bits (including spaces).
Data Compression - Wikipedia
The Wikipedia articla for data compression was also very useful in explaining the various aspects of data compression. The difference between "lossless" and "lossy" was very nicely explained. Basically, if the information that has been decompressed after compression is the exact same as the original information, it is lossless. On the other hand, if the information that has been decompressed after compression is not exactly the same as the original information, it is lossy. I believe this is one of the fundamental aspects of data compression. I would also assume that lossless is a better scenario to have then lossy. I wonder if there is any way possible to get the identical information back if the decompressed information comes out lossy?
Imagining Pittsburgh
I found this article to be extremely enlightening for the sole purpose of having the community of Pittsburgh understand and actually see what their city was like in previous years. I wish that every city would have the opportunity to create a website that has thousands of photographs from the past. The collaboration between the Archives Service Center of the University of Pittsburgh, Carnegie Museum of Art, and the Historical Society of Western Pennsylvania produced a useful website filled with meaningful photographs that adds to the cultural heritage of the greater Pittsburgh area. Even though there were many challenges these "partners" had to overcome, including building a working dialogue between the institutions and coming up with meaningful and helpful metadata subject headings, they successfully completed a project that can be enjoyed by many generations down the road.
You Tube and Libraries
This article was eye-opening in respect to libraries using current technology to help further their usefulness to the general public. I never thought about using You Tube videos to help public users, students, and even faculty with various functions of the library. I think there would be a great advantage to libraries across the world by using instruction-based You Tube videos. They could have videos that deal with a number of important ares including: how to use databases, how to find books in the library's online catalog, how to request inter-library loans, etc. There could also be instructional videos that new employees of the library could find useful in learning their new job responsibilities. I think that You Tube videos are a good way to make the library more useful to those who do not know how to use the resources the library offers. Plus, the accounts are free!
Sunday, September 19, 2010
Subscribe to:
Posts (Atom)