DH Evaluation: Do you FEEL it?

I will admit, without shame, that I’m still not 100% what digital humanities is supposed to be. To be fair, I know it’s a complex topic that can’t be easily defined by a picture next to some words in the dictionary. But I feel that DH consists of so many ideas, tactics, technologies, etc. that defining it becomes nearly impossible – because how can you define something that is always changing, to the point that by the time the definition has been expressed, it suddenly must change again?

I keep this in mind as I look to my DH evaluation project, and think to myself “how the hell am I going to judge this thing?” I can’t help but reflect on an assignment I just completed in my other class with Dr. Heba (Visual Rhetoric, if anyone else here is in that class). That assignment involved reading about “visual social semiotics,” which is essentially the method of analysis one can use to critique images in similar ways as critiquing words and language. I am pretty well versed in editing the written word (and the verbal, which is often harder), so I related a lot to what the author was contending about how the visual has earned its place in professional communication. She also spoke a lot about how intricate an image is – the angle, color, focus, space, all the things that make an image strong enough to impart a certain feeling or claim on the reader/observer. Visual social semiotics, even the author admits, is not a perfect analysis method, as all the details and combinations that communication requires (such as the combination of images and text) to evoke different responses can hardly be perfectly analyzed – there’s just so much possibility.

That is why, for our DH project evaluation, I intend to look at my selected project from a critical but flexible point of view. Rather than comment on every detail, point out every flaw, and tally every success, I will use a general outline that answers the ultimate question: “Did this project do its job, and do it well?”

The first step in this, for me, is gauging the purpose of the project. This isn’t something I need to know from the author’s mouth; indeed, we rarely get the chance to converse with the creator of a work anyway. No, the project should speak for itself, and so I will look for purpose in its content – what does this project, as a whole, seek to do? Inform, persuade, entertain? For whom is this project created (as in, what end-game audience, rather than the obvious answer of a professor or authority for a grade)? The next step is analyzing execution: does the content bear weight? Is the interface being used easy to navigate and understand? Is the design effective; is the programming performed in a way to draw in the user and make him want to engage in the content? My final step will be a “recommendation” of sorts. From a user point of view, I will point out not just the details but the overall feeling I have that results from my interaction with the project: did I feel like I got something out of the project, and would I recommend it to others as a worthy example of DH work?

This last step may be a red flag, as it is very subjective and hard to qualify or quantify. But at the end of the day, most analysis is, to some degree, subjective – in the humanities, at least. Going back to the idea of visual social semiotics, can one really look at an image objectively and still walk away having understood or absorbed that image’s message? Can we look at topics in humanities and comment on them without influence of feeling or experience? No, I don’t think so. And that’s not necessarily a bad thing. To me, DH is where technology and humanity intersect – it is where tangible advancement and intellectual growth walk hand-in-hand. To take the humanity – the feeling – out of it, and make it only about what’s right or wrong, good or bad, in a digital context would be insulting to the field. If we are to embrace DH, we must be willing to accept that the analysis of DH will involve not only a critique of the technical, but the intelligent integration of the experience and passion held by those who participate in DH creation and studies.

images

Evaluating Digital Humanities

Evaluating Digital Humanities has proven to be a difficult undertaking for me. As we’ve read about Digital Humanities for the past few weeks, I think we all have seen how ambiguous and nebulous the field is. I think this is due in part to the relative infancy of the field in comparison to other realms of the humanities, and I think this ambiguity and vaguery is freeing to the field as it allows for the field to take on many different shapes rather than be tethered to one singular set of standards, it also makes the process of legitimizing and evaluating products of the field to be somewhat of an arduous task.

 

One reason this is such a difficult task, as  Dr. Schocket mentioned, is the myriad of Digital Humanities projects that exist. As I began reviewing the lists of DH projects to evaluate, there seemed to be a little bit of everything listed from things I have familiarity with like EverNote and Tumblr, to things I had never heard of (but wish I had!) such as Cornell Notes PDF Generator and QuarkXPress. While all of these products are very unique, useful for humanities in a variety of ways, promote and illustrate the scholarship of their creators, and have some connection to politics, or social power of users and creators– just some of the categories for DH as discussed in Debates in Digital Humanities— these projects are so widely different it’s difficult to be comparative of them with any objectivity to truly and fairly evaluate them.

Continue reading “Evaluating Digital Humanities”