1.
I appreciate Ramsay’s comment regarding the ability to code or “build something” as a key consideration in one’s acknowledgement that they are a DH scholar. This struck me as useful in drawing a line in the sand in a field where a “definitional dilemma” seems to rear its head regarding the field from time to time. The problem with this, however, is that the scope of projects available to burgeoning scholars intending to code from the ground up in my view are limited. One could create a “collaboratively built tool that enables other scholars to add descriptive metadata to digitized manuscripts” but would another project really be necessary to practitioners when there is already Hypothesis and Manifold?
And with so many useful text analysis (Voyant), geo-spatial mapping, and data viz tools (Tableau) readily available, why the emphasis on knowing a computer programming language? Maybe the point is to have a working-knowledge of coding. In the same way a Literature major might need to know how to compose a sonnet. They may not be experts in the achievement of this goal, but can create one from the “ground up”. Alternatively can a Philosophy major be considered a scholar if they are unable to write a paper incorporating symbolic logic? It may not fit the end goal of their research which relies perhaps more on the merits of literary value rather than math and an Analytical style.
Maybe the issue of ground-level working knowledge of a skill? Wittgenstein famously came to Cambridge without having read Aristotle, which is very much in line with Keats’ Negative Capability. In the Humanities we don’t have a distinction between working knowledge and technical knowledge the same way other faculties like Social Science might have. A social scientist who can’t run a lab or has difficulty with statistics, seems to fail the tenets of the field, but what does that look like in the Humanities? Would it be one’s ability to mention at the drop of a hat five major themes from Songs of Innocence and Experience? Is a Literature major’s scholarly status docked for not having read Blake?
2.
So DH is a “motley of effort” (Krauss) and since I’m also taking a Pedagogy course this semester I’ve been made aware of two big sectioned off areas of DH. One in which the field makes a commitment to grappling with the fine points of online and hybrid learning in a way that is equitable and caters to the needs of students; the other is one which leans towards public scholarship: “addressing our work not simply to ‘the public’ but also… to specific communities” (Brennan). With social, racial, historical concerns to the fore. Its the explanation and pedagogical utility of DH projects that I feel could benefit from a reevaluation.
At least two of the projects offer an “explore” tab which breaks down the crucial elements of research and offers up the historic reasons for why a project is so vital. These explore tabs are inherent to most DH projects I’ve seen online and go a long way towards reckoning with the issue that ”scholarship that is not always fully legible to those not versed in the particular methods or conversations taking place in that domain”.
If this breakdown of core concepts is such a common occurrence, then it seems to me that; in the same way that there are just a few standards of notation software available that most people have agreed to use, can’t there be a software that organizes these Archive-heavy projects for people? The problem I run into is that, I know that project which perform archival work: gathering documents and organizing them across a timeline are set up the same way. That is, they have sections organized into: Explore, Find out More, Dig Deeper, Outline View modes, etc… Sometimes when I want to quickly switch from one to the other to compare the two, the UI is set up in such a way that I have to flip through pages and pages or differently organized and color-coded navigation views just to have the two side-by-side. I wonder if there isn’t room for a more Unified Approach to Archival Projects.

