If you are taking these courses, chances are you are a student or academic working in the Humanities who believes that you need coding skills to complete a project or analyse your data. Because most lessons one finds online are geared towards people from STEM backgrounds, we believe it is important to provide here some guidance and opportunities for reflection about how to conceptualise of your project in terms of digital tools, and how to see where code could potentially help your work grow.
💡 It is probably helpful for you to read the following section even if you already have a clear idea of what you want to achieve, because this section is designed to challenge you to think about your research in different ways.
Digital Humanities is a broad umbrella term for multiple areas of enquiry and research, all of which are connected by the presence of ‘digital’ things: digital concepts, digital methods, and digital material. While today all scholars, whether they be in the Sciences or the Humanities, use digital tools, you may not think of yourself as a ‘Digital Humanist’. Fortunately, you don’t have to be in the field of Digital Humanities to make use of its advancements. This course takes the very practical perspective that code can be accessible and useful to any scholar who needs to use it, regardless of their affiliations.
Whether or not you are a Digital Humanist, it is possible that your research could benefit from code. One of the challenges that scholars in the Humanities face is that they often don’t know what is possible with code, and so they don’t know if they should learn it or try to use it in their research. The easiest way to navigate this impasse is to think about your project in very practical terms:
For example, you may have the following (hypothetical) scenario: you have research aims which do not involve digital analytical tools, but in order to meet them, you have to process a lot of files of text in the same way, over and over. This is a prime candidate for a digital tool, because you can automate repetitive tasks using some code.
The answers to these questions vary infinitely by one’s project, but there are general guiding principles! While not covering all cases, the following principles can help you identify whether your project could benefit from automation:
[DO WE WANT A GRAPHIC FOR THIS LIST?]
These are indicators that you either have data which can be handled with digital processes, or you have tasks which can be automated. If this is the case, your project can likely benefit from code, and there probably already exist software packages (organisations of code) which can be used to manage your data.
There is also a second potential scenario: the research questions or aims which you have could be either achieved, or enhanced, through the use of digital tools. We can use my own PhD thesis as an example. My fundamental research question was: within a large corpus of medieval manuscript material in Hebrew, are there verifiable patterns of codicology (physical format of the manuscripts) and linguistic features? People have attempted answers to similar questions in my field without the use of automation, but they were only able to do so either on a very small number of manuscripts at a time, or in projects which span decades and involve large groups of researchers. I decided to look for methods which would enable me to find patterns quickly and reliably in a larger number of manuscripts. Thus, my PhD became a ‘Digital Humanities’ project.
Again, while not covering every case, the following principles can be of assistance:
[AGAIN, WE MIGHT CONSIDER MAKING GRAPHICS OF LISTS]
These are some (and certainly not all!) indicators that your research project could be enhanced, achieved, or even transformed with the use of digital tools.
A major theme appears here, which you may have already caught: a large part of Digital Humanities is making sense of and managing data. Many Humanities researchers think that they don’t have data, or that they don’t have a lot of data. In the vast majority of cases, this is simply untrue. Enlightening statistical tests can be run on small datasets of around 30 pieces of data, and anything that one describes, and even how they describe it, count as pieces of data which can be analysed by a computer in some way. Moreover, small datasets which are complex (involving multiple known or undiscovered relationships between entities) are also prime candidates for the use of digital tools.
This section of today’s lesson is, unavoidably, generalised, simply because there are infinite iterations of research questions which one may have and to which one can apply digital methods. However, there are a few guidelines for finding methods:
How might you integrate coding into your own research project? Would it play a central role? Would it support peripheral things, like basic data management or analysis? Could it enable central things, like the analysis itself?
Written by Estara Arrant, 2025-04-16
Licence: CC BY-SA 4.0