"Database" ~ Wikipedia
Talk about taking things for granted! I work with a database everyday and I never think about the complexity of the concept. I found this article to be very interesting. One of the most interesting ideas was that terms such as query languages, DDL and DML can be viewed as "special - purpose programming languages, tailored specifically to manipulate databases". When I build a query, I generally do not think of it being a special purpose language. Perhaps I will in the future.
"Entity relationship model in database" ~Wikipedia
Seeing an entity as a noun, an entity type as a category and a relationship as a verb really helped me to visualize the concept. Chen's examples of relationships such as marriage relationship with husband and wife and song and performer relationships were concrete and helped me to relate the idea to how the relationships work.
"Database normalization process"
This tutorial was, in my opinion, well written and presented. the use of pictures and diagrams help me to understand the information. It is very interesting that it actually requires work to de- moralize a database. I am not sure I could sit down and construct a database after this tutorial but i do feel like I understand the relationship between the data better. Also having the text- text connections from the two previous articles helped to make this article clearer.
Sunday, January 29, 2012
Saturday, January 28, 2012
Sunday, January 22, 2012
Week 3 Reading Notes
"Introduction to Metadata"
Without having taken Organizing an Retrieving Information class, I am learning about metadata for the first time. It seems like a simple concept that can be made complicated. I like thinking about metadata as Gilliland put it, ""the big picture" way of thinking about metadata". He also said, "metadata is the sum total of what one can say about any information object at any level of aggregation". This does help me to understand the terminology better. The typology of data standards gave me a better understanding because it explained the type and gave specific examples.
I agree that structure is important for organizing and representing data. It would be nice to have a universal standard to explain all collection and materials.
"An Overview of Dublin Core Data Model"
This is very difficult for me to understand because the terminology is new to me. I do agree that there is a need to standardize the way metadata is used. In Modularization / Extensibility, it says "there would never be one "true" declarative set of semantics to represent all resource descriptive requirements". Hopefully in the future there will be a way to define concepts that can be understood by many languages.
"Working with Endnote"
This software program can be very useful when writing papers. However I do think it would take some practice. I really like the way you can create your citations. I also think the search for literature tool could be very helpful. It sounds like once you learn the program, it will save time.
Without having taken Organizing an Retrieving Information class, I am learning about metadata for the first time. It seems like a simple concept that can be made complicated. I like thinking about metadata as Gilliland put it, ""the big picture" way of thinking about metadata". He also said, "metadata is the sum total of what one can say about any information object at any level of aggregation". This does help me to understand the terminology better. The typology of data standards gave me a better understanding because it explained the type and gave specific examples.
I agree that structure is important for organizing and representing data. It would be nice to have a universal standard to explain all collection and materials.
"An Overview of Dublin Core Data Model"
This is very difficult for me to understand because the terminology is new to me. I do agree that there is a need to standardize the way metadata is used. In Modularization / Extensibility, it says "there would never be one "true" declarative set of semantics to represent all resource descriptive requirements". Hopefully in the future there will be a way to define concepts that can be understood by many languages.
"Working with Endnote"
This software program can be very useful when writing papers. However I do think it would take some practice. I really like the way you can create your citations. I also think the search for literature tool could be very helpful. It sounds like once you learn the program, it will save time.
Saturday, January 21, 2012
Friday, January 13, 2012
Week 2 Reading Notes
"Computer Hardware"
It blows my mind to think about how much computer hardware as evolved and continues to evolve. The ability to increase data storage and simplify operations so that the average child can adequately operate while simultaneously finding less expensive hardware amazes me.
Reading through the article, I found there were many terms that I am familiar with even though I would not consider myself to be a technological genius. It seems I know more than I think I do simply by using technology daily.
However, some of the terms were foreign to me and I needed to spend more time reading and rereading about these devices.
"Computer Software"
Computer software reflects how I remember high school computer class to be. In computer class we learned about programing and how to set programs and procedures as well as algorithms. Oh how I wish I would have taken more of an interest then and learned all the "new" technology as it emerged. Of course what exactly is "new technology"? It evolves minute by minute. Instead of looking back and saying I should have, I can keep current now and be a part of the future of technology and the future of computer software.
"European libraries face problems in digitizing" NY Times
Looking at the fact that these libraries will not receive much government funding to digitize and the fact that they are considering a deal with Google interests me from a development point of view. I found it inviting and interesting that Google would offer so much funding initially. But after some contemplation, it sounds like the library is "for sale" and no One should own the library. Caution should be taken so as not to compromise the service for the patrons for the prestige of the collection. There are better ways to get the funding. I think Google is only looking out for Google. Someone has to keep in mind the needs of the patrons.
"Digitization: Is It Worth It?" Stuart D. Lee
As I read "Digitization: Is It Worth IT?" I felt there was a text - to - text connection between this article and "Lied Library @ four years" article from week 1. It is important to take caution before purchasing because of how quickly technology can become outdated. As stated in "Lied library @ four years", "technology is fluid and constantly changing". It comes down to knowing your readers and their needs as well as trying to predict and project what the needs will be in the future. Finding that balance is the ultimate challenge.
It blows my mind to think about how much computer hardware as evolved and continues to evolve. The ability to increase data storage and simplify operations so that the average child can adequately operate while simultaneously finding less expensive hardware amazes me.
Reading through the article, I found there were many terms that I am familiar with even though I would not consider myself to be a technological genius. It seems I know more than I think I do simply by using technology daily.
However, some of the terms were foreign to me and I needed to spend more time reading and rereading about these devices.
"Computer Software"
Computer software reflects how I remember high school computer class to be. In computer class we learned about programing and how to set programs and procedures as well as algorithms. Oh how I wish I would have taken more of an interest then and learned all the "new" technology as it emerged. Of course what exactly is "new technology"? It evolves minute by minute. Instead of looking back and saying I should have, I can keep current now and be a part of the future of technology and the future of computer software.
"European libraries face problems in digitizing" NY Times
Looking at the fact that these libraries will not receive much government funding to digitize and the fact that they are considering a deal with Google interests me from a development point of view. I found it inviting and interesting that Google would offer so much funding initially. But after some contemplation, it sounds like the library is "for sale" and no One should own the library. Caution should be taken so as not to compromise the service for the patrons for the prestige of the collection. There are better ways to get the funding. I think Google is only looking out for Google. Someone has to keep in mind the needs of the patrons.
"Digitization: Is It Worth It?" Stuart D. Lee
As I read "Digitization: Is It Worth IT?" I felt there was a text - to - text connection between this article and "Lied Library @ four years" article from week 1. It is important to take caution before purchasing because of how quickly technology can become outdated. As stated in "Lied library @ four years", "technology is fluid and constantly changing". It comes down to knowing your readers and their needs as well as trying to predict and project what the needs will be in the future. Finding that balance is the ultimate challenge.
Thursday, January 12, 2012
Subscribe to:
Comments (Atom)