Parvin – Digital Past

Learning Digital History Through Technical Problems

My first technical assignment for the course was much more difficult than I expected. It involved working with Shared Hosting and setting up a website through my hosting account. At first, I assumed that once I had access to cPanel, creating and managing the site would be relatively simple. But even when I followed the instructions, things did not always work as I expected. In the end, rather than continuing to struggle with the new site, I decided to return to an older blog I had already been using.

At first, I considered this a failure. The purpose of the assignment seemed to be learning how to use a new technical environment, and I felt that I should be able to make it work. But the experience also made me think differently about what it really means to work in digital history.

Reading William G. Thomas and Douglas Seefeldt’s What Is Digital History? helped me see this experience in a larger context. The authors emphasize the importance of collaboration among historians, programmers, librarians, designers, and information specialists. My much smaller experience with cPanel gave me a sense of why this collaboration is necessary. Even creating a platform on which historical material appears can require considerable technical knowledge.

Thomas and Seefeldt also describe digital technology as a means of historical research and interpretation rather than an end in itself. A digital history project still needs a historical question and an argument. As they put it, digital history is more than simply digitizing the past; it creates a framework through which people can “experience, read, and follow an argument about a major historical problem” (Thomas and Seefeldt).

I was also interested in their idea that digital history can give readers a more active role. Instead of simply reading an article from beginning to end, readers can search materials, follow connections, examine primary sources, explore maps, and sometimes develop their own interpretations. This changes the relationship between the historian, the evidence, and the audience.

From Patrick Lewis’s review of Adam Crymble’s book, I learned that Crymble adds another perspective. He shows that digital history is not completely new. Technology has mainly changed how quickly and easily historians can find, organize, analyze, and share information. I especially found his discussion of blogging interesting. Crymble writes that “the real story of blogging was social rather than technological” (14). Blogs created spaces where more people could participate in historical discussion outside traditional academic publishing.

Digital history is more than putting historical sources online; it is the use of digital tools to research, interpret, organize, and present the past in new ways.  Historians still ask questions, examine evidence, and build arguments, but computers and the internet have made research faster, more searchable, more collaborative, and more accessible. In this way, digital history changes how historians do research more than it changes the basic purpose of studying history.

4 responses to “Learning Digital History Through Technical Problems”

  1. Alexa Koeckritz Avatar

    (I also realized that my comment did not post last week…)

    Hi Parvin, I relate heavily to the title of your post. Most of my DH work has involved learning new software I didn’t understand and trial-and-erroring my way through issues to a serviceable final product, usually with plenty of questions to tech support along the way. Thank you for opening up about your experiences and struggles–I will no doubt have to voice my own in the coming weeks. As I understand them, our group projects will adhere to Thomas and Seefeldt’s views on collaboration in the DH field: each member will have their own specialized contributions to the project, be that research, content writing, creating the technological platform, managing data, or creating metadata. We don’t all have to be technical masters, and because DH is such a collaborative field, it’s important to determine and utilize group members’ strengths for the benefit of the final project.

    Also, I was similarly interested in the participatory nature of DH after this week’s readings; it seems to be a field inherently connected with audience interaction, and that should influence how we design final products, be those digital exhibits, searchable databases, or usable software.

  2. Christopher A Pfeifer Avatar
    Christopher A Pfeifer

    Speaking of technical difficulties, I got an error when I posted my original comment, so here I am rewriting it. I am glad you got through the technical problems of the first day of class.

    I look forward to seeing the types of tools we will have access to through this class and learning about other avenues of digital humanities. I am most interested in data mapping tools and how they can visualize connections in research, as well as how they can help streamline the research process.

  3. Denton Avatar

    With the advancements in technology over the last twenty years, people forget that things like web design used to be isolated to the work of expert coders. Go easy on yourself. Collaboration like digital history is not new in the field. Historians have always had to work with librarians, archivists, and fellow historians. Adding programmers, designers, and engineers is just the next step in the discipline’s evolution.

  4. Peter Whitman Avatar

    I had almost the exact same problem with the cPanel tab on Reclaim Hosting, even though I had set up the website several days before class. This is a good lesson on the vagaries of the campus IT system, as we had problems installing software but other class members did not. At least according to the Graham book, “Failing Gloriously and Other Essays,” solving technical problems is endemic to being a digital historian.

Leave a Reply


4 responses to “Learning Digital History Through Technical Problems”

  1. (I also realized that my comment did not post last week…)

    Hi Parvin, I relate heavily to the title of your post. Most of my DH work has involved learning new software I didn’t understand and trial-and-erroring my way through issues to a serviceable final product, usually with plenty of questions to tech support along the way. Thank you for opening up about your experiences and struggles–I will no doubt have to voice my own in the coming weeks. As I understand them, our group projects will adhere to Thomas and Seefeldt’s views on collaboration in the DH field: each member will have their own specialized contributions to the project, be that research, content writing, creating the technological platform, managing data, or creating metadata. We don’t all have to be technical masters, and because DH is such a collaborative field, it’s important to determine and utilize group members’ strengths for the benefit of the final project.

    Also, I was similarly interested in the participatory nature of DH after this week’s readings; it seems to be a field inherently connected with audience interaction, and that should influence how we design final products, be those digital exhibits, searchable databases, or usable software.

  2. Speaking of technical difficulties, I got an error when I posted my original comment, so here I am rewriting it. I am glad you got through the technical problems of the first day of class.

    I look forward to seeing the types of tools we will have access to through this class and learning about other avenues of digital humanities. I am most interested in data mapping tools and how they can visualize connections in research, as well as how they can help streamline the research process.

  3. With the advancements in technology over the last twenty years, people forget that things like web design used to be isolated to the work of expert coders. Go easy on yourself. Collaboration like digital history is not new in the field. Historians have always had to work with librarians, archivists, and fellow historians. Adding programmers, designers, and engineers is just the next step in the discipline’s evolution.

  4. I had almost the exact same problem with the cPanel tab on Reclaim Hosting, even though I had set up the website several days before class. This is a good lesson on the vagaries of the campus IT system, as we had problems installing software but other class members did not. At least according to the Graham book, “Failing Gloriously and Other Essays,” solving technical problems is endemic to being a digital historian.

Leave a Reply

Discover more from Parvin - Digital Past

Subscribe now to keep reading and get access to the full archive.

Continue reading