Blog Post 3: Metadata and Database Design
In my understanding metadata is the application of organizing, describing, and classifying data. It is often used when trying to summarize large amounts of information. One needs to understand metadata to become sufficient in the humanities search because metadata is one of the sole factors in finding a topic or idea. I liked the example they provided in chapter four and page 53 of The Digital Humanities Coursebook when describing metadata. They say to imagine the data as “information in any form sitting on shelves, in drawers, or boxes (objects, numbers, or files)” and to think of the metadata as the label maker. The metadata organizes everything and provides a structure to all the information. Specifically, my project was organized in multiple ways, the most prominent being organized by year. Yet the timeline is also separated by the British monarchy's royal houses, such as the House of Denmark, the House of Godwin, etc.
As for understanding database design, it is the idea of ‘sorting’ in the way that databases sort through information and decide where it goes and why it does. Database designs and sorting into tables must be done logically to reduce errors and increase efficacy. In chapter five and page 70 of The Digital Humanities Coursebook, I found the quote “data can be deep without being big” very interesting. In the coursebook, they gave the example of a spreadsheet containing links to various points of information. Where the spreadsheet appears to be very small and easy to read yet each link goes to a separate site, thus showing that the spreadsheet is not big but the data within the spreadsheet runs deep. This metaphor relates to the timeline website in the way that each of the monarchs on the timeline has its unique identifier and a link that will bring the audience to a separate page containing further information and images of the specific monarch. This database design has been proven to be very helpful and easy to use for any audience. Regarding future projects that will be completed in class metadata and database design highly correlate to the UNH library. The UNH library website and physical building both use metadata and database design in the form of structuring, organizing, and compacting their information and resources for the ease of the students at UNH.
Here is the link to my project: https://www.chronoflotimeline.com/timeline/shared/11043/Kings-and-Queens-of-England-and-Great-Britain/
Great quote, “data can be deep without being big” and how it's applicable to your Timeline project. Remind me to show you the Maine MILL example. And, yes, libraries love cataloguing and structuring! :)
ReplyDeleteYou used very excellent quotes in order to further explain your thinking, and to dig deep onto the ideas of metadata and database design. I very much liked the quote about data and how you can visualize it as, "information in any form sitting on shelves, in drawers, or boxes (objects, numbers, or files)." I feel this quote can generally relate to all the work we are doing within our Digital Humanities Projects right now considering a lot of us are working with things like files. I am very much looking forward to your presentation tomorrow to learn more about the project you choose. Just by this post I know it will be very interesting!
ReplyDeletePersonally I feel this quote from chapter five relates to my project, "Database and database management systems are intellectual instruments that pass as technical ones. Is there such a thing as a “feminist” table? Or a “racist” form for data entry? Can format embody bias, or only content? The structure of data is always fraught with values and the very act of defining categories can create exclusionary results. Data collection is often shaped by biases and data can be constructed to support almost any position on the ideological and political spectrum. Lack of differentiation or nuance can be equally damaging" (Drucker, 70). My Digital Humanities Project is about The Salem Witch Trials, and I have noticed possible biases within the data provided in my project, and I can't make out if it was intentional or the data that was provided was just the only data they had to go of off, and so that is what they provided.
I liked your summery and understanding of Metadata. I too thought their usage of the "books and shelves" metaphor was very helpful. It gave better context to a topic that I originally found very daunting, and sort of esoteric. I originally thought metadata was a form of "sorting" rather then a labeling process for pools of data. The sorting is more database design. For my project, a virtual tour, I didn't realize how important metadata is. Metadata can be used to tag and link different parts of the virtual tour, making it easier for users to navigate through the tour. For example, it can help in creating hotspots or interactive elements that users can click on to explore more information or move to another part of the tour.
ReplyDelete