Week 5 - comments

http://jordanmoorelis2600.blogspot.com/2009/09/week-5-readings.html

http://brandonlocke.blogspot.com/2009/09/readings-week-five.html

Week 5 - notes

Data Compression:

I never realized how much there was to data compression. I knew a little about it - for example, with audio files, I've noticed that I don't have to copy them to my computer at the highest quality for them to sound good. I didn't know about the different methods, or the difference between "lossless" and "lossy" compression (or that they even existed, really).


DVD-HQ: Data Compression Basics:

This was pretty interesting, actually. It seemed to basically be expanding on what the Wiki article said, but I enjoyed seeing some of the things illustrated - it helped me really understand how the different compression methods are done.


Edward A. Galloway, “Imaging Pittsburgh: Creating a shared gateway to digital image collections of the Pittsburgh region” First Monday 9:5 2004

This article seems to show why data compression could be important to libraries. Basically, if data is compressed, and thus stored more efficiently, then there is room for more content, meaning projects such as this are easier to accomplish.


Paula L. Webb, YouTube and libraries: It could be a beautiful relationship C&RL News, June 2007 Vol. 68, No. 6 0

This was pretty basic - it just suggested a few ways libraries could use YouTube to reach the public.

Week 4 - The Muddiest Point

I have no muddiest point for this week.

Week 4 - comments

Here are the places where I've commented:

http://cac160.blogspot.com/2009/09/week-4-reading-notes.html

http://brandonlocke.blogspot.com/2009/09/readings-week-four.html

Week 4 - Notes

Database

It's interesting how much a DBMS does (development/interrogation/maintenance/development). I don't usually think of a database doing anything, aside from sitting there and holding the information. There are also a lot more types of databases and models than I realized. There are also a lot of safeguards in place, both for security purposes and to prevent computer troubles. One doesn't tend to realize that databases have the potential to cause these things - again, I typically thought of a database just being there. Judging from this, though, there are a lot of little things that they do that never occured to me.

Metadata

This is a term I'd heard before, but I never really gave it thought. I think what made it click is the mention of dates on websites, to know when the information is from - in a computer class I took, one of our assignments was to judge how reliable some websites were, and it being up-to-date was a criteria. I can see how it applies to libraries, though, as adding metadata to something makes it easier to categorize, and thus easier to access.

Dublin Core Data Model

The main thing I got out of this, basically, is that it combines the other two articles for the week. That is, they're trying to make a database of metadata.

Week 3 - The Muddiest Point

I'm mainly wondering what exactly the FAT file system was? Why was it bad, or at least, what makes NTFS a better system? I see from the Powerpoint that it's more efficient and secure, but what makes it so?

Assignment 2 - flickr

Here's the link to my digitization/flickr stuff:

http://www.flickr.com/photos/42525296@N08/

I have several pictures that show the different stages of a costume I'm making, plus a few of things around the house.