Showing posts with label Week 4. Show all posts
Showing posts with label Week 4. Show all posts
Friday, September 19, 2008
Muddiest Point Week 4
When talking about the Relational Model it was referred to as a "secure structure" in relation to Boolean operators such as "And" or "OR." Does this mean that the searches will provide a straight forward answer to the query given?
Thursday, September 11, 2008
Monday, September 8, 2008
Week 4 Readings
1.) An Overview of the Dublin Core Data Model
I felt the author could have written in plainer language, I had to get out a textbook from a previous class to refresh my memory of the Dublin Cores metadata standards.
The Dublin Core (hailing from Dublin, Ohio) brings together disparate information via their use of metadata. It is a system that works with different languages and cataloging systems to possibly have a unified catalog. There are specific pieces of information that each person creating the metadata needs to fill in. For example, Title, date, publisher, etc. Things like date are standardized because some people write the month first while other write the day of the month first. It is essentially a standard way to describe things. They are working to include other cultural definitions of things such as censorship with qualifiers.
The DCMI oversees the use of the standards made by the Dublin Core.
2.) Introduction to Metadata - data about data
I should have read this article first. . . it gives a good over of what metadata entails.
Metadata does not mean the same thing to everyone. It is a way to increase the access to the information a library has. Two examples: Library of Congress Subject Headings and MeSH - Medical Subject Headings.
3 features of an information object:
Content - what it contains, intrinsic information
Context - who, what, why, where - extrinsic
Structure - formal set of associations among info objects
Because metadata means so many different things to different people, systems are needed to make metadata interoperable. Such as the Dublin Core's system.
I felt the author could have written in plainer language, I had to get out a textbook from a previous class to refresh my memory of the Dublin Cores metadata standards.
The Dublin Core (hailing from Dublin, Ohio) brings together disparate information via their use of metadata. It is a system that works with different languages and cataloging systems to possibly have a unified catalog. There are specific pieces of information that each person creating the metadata needs to fill in. For example, Title, date, publisher, etc. Things like date are standardized because some people write the month first while other write the day of the month first. It is essentially a standard way to describe things. They are working to include other cultural definitions of things such as censorship with qualifiers.
The DCMI oversees the use of the standards made by the Dublin Core.
2.) Introduction to Metadata - data about data
I should have read this article first. . . it gives a good over of what metadata entails.
Metadata does not mean the same thing to everyone. It is a way to increase the access to the information a library has. Two examples: Library of Congress Subject Headings and MeSH - Medical Subject Headings.
3 features of an information object:
Content - what it contains, intrinsic information
Context - who, what, why, where - extrinsic
Structure - formal set of associations among info objects
Because metadata means so many different things to different people, systems are needed to make metadata interoperable. Such as the Dublin Core's system.
It was interesting to learn about the various definitions of metadata and their uses by different professions. The most important part of metadata is that it organizes information to make sure what it is describing is able to be retrieved and used.
3.) Database - Wikipedia Article
This article was over my head. While I understood the basic design elements behind setting up a database, eventually that was lost in all the discussion of rows and columns. After the Hierarchical model, which reminded me of an index or thesaurus, I was lost. If pictures or graphical representations had been used I might have had a better understanding all all the differences between the databases.
I didn't understand why each tuple in a relational model was given an atomic value.
Subscribe to:
Posts (Atom)
