I am not sure what I was expecting when the first year fellows were assigned to the Research division. I came with a preconceived notion of what Digital History research is and what historians do with it. It turned out that the scope of my understanding was actually quite limited. My time in the division has taught me a lot about the vast applications and possibilities of Digital History. We (the first year fellows) were given chances to get our hands dirty and it proved very rewarding. Sadly, this blog post marks the end of our rotation through the Research division.
Our first assignment was to PressForward. We started from the ground up by familiarizing ourselves with the project. We installed the plugin on the sandbox server and got to bang around on it. We explored the PressForward.org site as well as the digitalhumanitiesnow.org site. I must admit that my initial reaction was that PressForward was a glorified RSS reader with some added features of promoting articles. I use Feedly (a RSS reader) on my phone to follow various history blogs and I, at first, did not see a big difference between the two. It wasn’t until someone explained “gray literature” that the full purpose of PressForward came into view. Until that point, I had been ignorant to the issue of online scholarship. The PressForward site explains “gray literature” to be “conference papers, white papers, reports, scholarly blogs, and digital projects.” Online scholarship is being under-appreciated and forgotten in a discipline that has focused so heavily for so long on printed material. My assignment as an Editor-at-Large and then as an Editor-in-Chief brought this issue into focus for me
Working as an Editor-at-Large and Editor-in-Chief really solidified the importance of PressForward. As an Editors-at-Large, we worked through the live feed of articles and websites coming into Digital Humanities Now. I learned that it can be labor intensive to sift through the various websites and articles to find important, relevant material. It is not always easy to find the scholarship and pertinent information. I also learned first hand about the limitations of the software. On a couple of occasions I fell victim to the browser’s back button instead of closing a window. I then found myself back at the beginning of the feed instead of where I was before I had clicked on the article. After shadowing Amanda and Mandy when they were Editors-in-Chief, the first year fellows were able to make decisions on what would be published to DH Now. It was a very fun experience that helped me begin to grasp the extent of online scholarship and publishing. In addition, reading through the articles helped us to be informed an the various projects in the field. I even found articles that did not qualify for DH Now but were of interest to me. I bookmarked more than a handful that I wanted to return to later.
The final part of Programming Historian were the lessons on APIs, more specifically the Zotero API. I had never used Zotero so these lessons introduced me to both Zotero and the Zotero API. Before I began the lessons I played around on Zotero, starting my own library and learning to love the program. From the beginning, I wanted to use my personal library in the lessons and not the sample one provided. By doing this, Spencer and I found a problem in the lessons when my program couldn’t access my library. Alyssa has since reported it and a problem she had to GitHub. After finishing the API lessons, I wanted to do things that the lessons did not delve into. With help from Spencer I was able to bang around on the API in an attempt to add/edit the author field of an item. While we did not find a solution we did make headway and it really piqued my interest in working on the Zotero API.
I am leaving a much improved Digital Historian. The Research division had to help the first year fellows through a learning curve that, in some ways, Education and Public Projects don’t. We now know the Center and feel comfortable in it.We got our feet wet and our hands dirty. The Research division was a great place to do that.