Data & Digitization

In reading chapters 2 and 3 of Johanna Drucker's The Digital Humanities Coursebook, my understanding of digital humanities was certainly furthered (as to whether or not it became more clear is up for debate... it seems as though the more you learn about DH, the more ambiguous the definition becomes).

Chapter 2 of the text was centered around the topic of data modeling, which provided insight as to how data is embedded in a digital format. To paraphrase the book, data modeling is the process in which information is abstracted to produce data in a new way. To directly quote Drucker, "Humanities 'data' are produced by taking documents or artifacts and abstracting from them certain features that can be represented explicitly" (Drucker, 19). Furthermore, the process of consuming said content means extracting the data by "analyzing the categories into which the information has been organized" (Drucker, 21). This really put my own definition of DH into perspective by explaining how data modeling channels data so it can be consumed in a number of different ways. 

Something else mentioned in the book that challenged what I had previously thought about DH was the clarification that not all DH projects are inherently "networked." Rather, "many analog and digital forms of data in the humanities are used for non-networked purposes" (Drucker, 34). Drucker also explores the topic of HTML within chapter 3 (among other formatting topics) which increased my awareness of the intricacies in digitization, however the discussion of HTML admittedly went completely over my head. I was able to retain the idea, however, that file formatting is quite important in creating an effective digital project.

Specifically in terms of how and where the content within these chapters relates to my own project analysis, I was able to draw several parallels. First, I was able to determine that the project I am analyzing comprises of "unstructured data," as it involves textual-renditions of stories, recalled events from a subjective source, audio files, images, and so on. Further, the project's purpose is to preserve stories and history of Maine in a broadly consumable way. As opposed to being a list of data, data modeling plays a role in making the information on the site more accessible and draws in an audience that may not be strictly historians and others of the like. Reading these chapters brought a new understanding and appreciation for me to the project I am working to analyze. 

Comments

  1. Hi Jordan! I absolutely loved the quote you chose for chapter 2 - I found analyzing the explicit representation of data to be a perfect way of looking at what data truly is. I also very much agree to the sentiment that file formatting is crucial for any digital project! Reading how the excerpts apply to your project made me just as excited to dive into my project as well!

    ReplyDelete
  2. Love: "the more you learn about DH, the more ambiguous the definition becomes." And, yes, file formatting is terribly important (as is metadata if you are passing your project on at some point). When dealing with html it's all about pointing to files, images, etc., and organization tells the code where to find things that are included. Hopefully this gives you more terms for your analysis. I thought about your project (and the Museum L/A one) when reading about the implications of cultural data--who it is portraying, how it was collected, who "owns" these stories, etc.

    ReplyDelete

Post a Comment

Popular posts from this blog

Maps & Virtual Spaces

What is digital humanities?

Blog post 2: Data & Digitilzation