att16

Monday, September 27, 2010

Muddiest Point

As I looked through the required readings, I had noticed that there was one article on databases, one on metadata, and one on an example of metadata being put into use. Putting those circumstances into consideration, I think it would seem reasonable that there should have also been an article on one type of a database. Of course, I am aware that the article of the Dublin Core Data Model managed to cover the issue. However, I still believe there should have been one example of popular database program being explained so that we as the readers can get better acquainted with the concept of what a typical database in current use is supposed to resemble. It may even help to have other articles on different examples of database programs. The explanations that they all provide should allow the readers opportunities to make comparisons. As soon as the readers reach to the article about the Dublin Core Data Model, they are able to witness as to whether such a project can wield the potential of being universally embraced. Otherwise, if we are simply to read the article offhand, whatever promises it claims to deliver, we are in a situation where we can only accept the author’s word.

Week 5: Comments

Comment #1: http://jsslis2600.blogspot.com/2010/09/week-4-reading-notes.html

Comment #2: http://pratt2600.blogspot.com/2010/09/unit-5-reading-notes.html

Week 5: Information Organization by Database, Metadata

See this link: http://att16.blogspot.com/2010/09/week-4-information-organization-by.html

Assignment 3

Thursday, September 23, 2010

Muddiest Point

I sort of felt conflicted between the Wikipedia article on “Data Compression” and the DVD-HQ article on “Data Compression Basics.” Because both sources specifically mentioned about “lossy” and “lossless” formats in regards to this tool, I knew right away I had to focus my attention on that concept. Of course, this saved me a lot of trouble in terms of where to look, only to realize the path I took had another barrier of vagueness to confront. I later found myself in a situation where I was constantly looking back and forth between the articles, just for the sake of making sure I was interpreting those terminologies correctly. I started having a strange feeling the two sources felt like one and the same article. Whatever description I was able to conjure, I had to make it was not only brief enough to be compacted into a nutshell, but also able to establish a connection with the other two articles. Otherwise, I would have ended up needing to rewrite everything I had already provided, as well as to reread all the articles, in hopes of having better luck of trying to find another way all the required readings could possibly be related.

Week 4: Comments

Comment #1: http://guybrariantim.blogspot.com/2010/09/week-4-readings.html

Comment #2: http://pittlis2600.blogspot.com/2010/09/week-four-reading-notes.html

Wednesday, September 22, 2010

Week 4: Multimedia Representation and Storage

The benefit of being able to compress digital materials is that extra room can always be made for incoming storage. How much space can be made available often depends on the size of the compressed files put together and the amount of storage the hard-drive can handle. Nevertheless, by decreasing the size of the materials, more room is able to be made. However, the process is not exactly straightforward. People can always debate with themselves as to whether data should be compressed in a “lossy” or “lossless” manner. For the case of the former, although the data is compressed to a size smaller than to what the other does, it ends up disposing a bit more data. As for the latter, although it may take up a bit more room in comparison, it is more likely to keep the data intact. Which version is to be considered as suitable would have to depend on whether the individual is more concerned about the amount of storage available or the quality of the data. This sort of situation had to have placed the University of Pittsburgh’s Digital Research Library into a dilemma after the Institute of Museum and Library Services provided a two-year grant. The staff needs to think about not only preservation issues via digitization, but also financial. There is more to consider as to whether it is better to settle for a format that can save more space, yet ruin the quality, or vice versa. What also needs to be put into consideration is which one is cheaper. Fortunately, Paula L. Webb was able to explain that a compromise can be possible. If libraries can bring such technologies as what YouTube.com has to offer to their advantage, then they are able to create so much more room for making so much more material available and accessible without spending as much money or considering the necessity of sacrificing the quality of the data. By pursuing such an opportunity, infinite space can be made to store and organize sources of information at its best quality for free.

Although the compression of data certainly has its potential, just like any other technological breakthrough, it is important to never give in all at once. I can vouch for this based on a recent experience that is still posing as a problem on me. Since the very beginning of my studies at this master’s program, I cherished the information I was being given about this profession and I knew I was going to need it all for my career. Unfortunately, I also knew I was bound by timing constraints, which means I have been unable to savor and analyze the knowledge the way I had wanted. That is why I was taking the precaution of saving all the work, including my homework, reading materials, and video lectures. I later learned that there was too little space left on my hard-drive. Because the next semester, which is the one I am in right now, was coming up, I wanted to resort to some kind of a quick fix to organize and save space. I basically compressed the files, placed them in compressed files, and into another. I made some room, but it did not really make much of a difference. Now, whenever I try to access those files, I am simply barred out. The only way it is possible is if I empty my hard-drive of material I will not need. Since I am too busy with my school work, I simply do not have the time at the moment to look through my entire computer and carefully select what I should render as garbage. As a consequence, I am currently unable to look back at my work whenever I need reinvestigate certain issues of which I am reminded. If there is a valuable lesson to learn from this experience, it is to always have a clear understanding as of how a technology works before attempting anything. When it comes to compression, it is always important to preserve the original versions of the sources so in case anything goes wrong, a back-up will be available for an emergency. Otherwise, you will just have to end up dealing with data that is serving no purpose.