First Rotation: Educational Projects Division

One of the first people I ever met at George Mason was Kelly Schrum, the Director of Educational Projects at the Roy Rosenzweig Center for History and New Media (RRCHNM). At the time, I was visiting George Mason as a potential school at which to pursue my Master’s degree in History. After meeting with Dr. Schrum, witnessing her enthusiasm for what she did, and hearing about the diversity of engaging projects being created not only in the Educational Projects Division, but across the entire Center, I thought, “I HAVE to be a part of this!” Three years later, I am excited to finally join the Center in my role as a Digital History Fellow.

Naturally, I was delighted to begin my journey at RRCHNM by spending my first four-week rotation in the Educational Projects Division. While I have had little formal training in classroom-based education (educational theory, lesson plan writing, etc.), I have always been passionate about history education and have held several jobs and internships executing museum-based history education. Also, my interest in using digital tools to help create resources for classroom teachers had been piqued while taking a class called “Teaching and Learning in the Digital Age” as part of George Mason University’s Digital Public Humanities Graduate Certificate (which, coincidentally, is partially administered by the Educational Division at RRCHNM.)  

While the Educational Division is somewhat separated from the rest of the Center by a hallway, it was clear right away that it is an integral part of what the Center does. There are multiple different projects that the division juggles at the same time, from creating education websites with partner organizations, to teaching and managing online courses in history and digital tools for classroom teachers and learners of all ages. The Educational Division keeps itself organized with a giant whiteboard, where progress is reviewed in a weekly staff meeting, and with To-Dos, messages and comments through project management software like Basecamp. Because of these organizational methods, it was easy for the DH Fellows to see the status of each project and know what needed to be done next. This allowed us to jump right in and start completing tasks that helped the division move forward on their projects. During what seemed like a short but productive four weeks, we focused on two main projects, Understanding Sacrifice and Eagle Eye Citizen.

Understanding Sacrifice is an ongoing program through the American Battlefield Monument Commission (ABMC) that allows teachers to research a fallen U.S. military hero buried in one of the ABMC cemeteries, write a short biography and eulogy for the fallen hero, travel to the cemetery where that hero is buried, give their eulogy at the hero’s grave, and then write a lesson plan for their students based on what they have learned through the process. This year, the teachers focused on fallen heroes from World War II in the Pacific. Therefore, the cemeteries they visited were in California, Hawaii and the Philippines. For this project, we worked directly with Jennifer Rosenfeld, the Associate Director of Educational Projects.

This project gave me experience doing a wide variety of tasks, as we worked to get this year’s lesson plans, source materials, educational resources, fallen hero profiles, and eulogy videos formatted correctly and uploaded online. Since this project uses a Drupal interface and required us to write basic HTML code, I was thankful for my previous internship at the Smithsonian Institution Archives, where I learned these skills.

Tasks for this project included transcribing audio interviews to be used in some of the teachers’ lesson plans, using YouTube to add closed captions to the eulogy videos and other content videos, inputting and uploading content to the ABMC Education website (images, hero profiles, lesson plans), double checking the sources for each lesson plan, and making sure sources were cited properly and linked to the correct websites. In addition, each online lesson plan also includes a printable PDF version of the lesson plan and applicable handouts. Once these PDFs were created by other GRAs in the division, we were tasked with proofreading them, not only for grammar, but also for content, formatting (spacing, bold, italics, font size, etc.), and consistency between what the teacher originally wrote, what had been added into the website, and what was in the printable PDF. Then we offered suggestions for improvement, which had to be sent back to the teacher for their response and approval before the necessary changes were made on the PDFs and on Drupal.

Out of all the tasks for the ABMC project, I most enjoyed adding the captions to the eulogy videos. First of all, it was a lot like video editing, with which I have previous experience  and which I enjoy. Secondly, it allowed me to learn a lot about the fallen heroes–their lives and the sacrifices that they made for our country. Because I know little about WWII in the Pacific, this was very insightful. Thirdly, through the videos of the teachers reading their eulogies at the fallen heroes’ gravesites, I could hear in their voices how much they felt for the the fallen heroes’ families and see how much hard work they had put into recognizing their hero’s sacrifice. This made me want to work even harder to do what I could, to make sure that the teachers’ work in honoring these heroes and teaching their students about them would be ready and available to others.

The second project we worked on is Eagle Eye Citizen. This website was developed by RRCHNM in partnership with the Library of Congress. It teaches civics to middle and high school students by allowing them to solve and create challenges in a game-like environment using primary sources provided by the Library of Congress. As the students solve and create challenges, they earn points, badges, and can even level-up. All the while, they are learning about topics such as voting, political parties, rights and civic responsibilities. The site also offers students a chance to reflect on each challenge at the end, telling how they solved the challenge or giving rationale for their selections when creating a challenge. For this project, we worked primarily with PhD candidate Sara Collini.

When we started our rotation, the site was mostly complete, leading up to soft-launch and then the official launch a few weeks later. Therefore, one of our primary jobs for this project was to “break” the site. We spent hours testing, making sure that all of the interactive elements worked, that students could not move on without completing each task, that the audio clips played, and that all of the links worked. One of the features of Eagle Eye is a “Look Closer” button, which gives students a larger view of each primary source. We checked if that was working. We also changed roles, logging in as a student and then as a teacher, checking to see if teachers could create and manage a class of student users, as well as review their students’ reflections and challenges they had created. We tested the site on different operating systems (Mac vs. PC) and browsers (Chrome, Firefox, Internet Explorer, Safari, etc.) to see how it might respond. Through doing this work, I realized how hard it is to describe with words what, where, why and how something is not working correctly. In the end, I eventually reverted to taking screenshots of issues and then annotating them with text, arrows and circles to point out the irregularities. Finally, at the end of the testing, we even had a chance to create challenges of our own that would be used when the site launches.

Although I only got to spend four weeks in the Education Division, I feel like I did and learned a LOT! Not only did I learn new content (information about ABMC heroes, how a lesson plan is formatted) and skills (how to create bulleted lists in HTML), I also learned about the workflow of a digital history center and how to balance working on different projects at the same time. While I had read a lot about how centers like RRCHNM function (both during the Certificate program and at the beginning of the semester), it has been really beneficial for me to see how the Center’s work is carried out on the ground, on a day-to-day basis, and to be a part of it.

It is also exciting to feel like the small role I played was actually useful for these projects, and that I was doing something that really mattered. Even as we move on to the next division, I am excited to see both of these projects launch and to hear what feedback the division gets from the teachers who are incorporating both projects in their classrooms.

Behind the Screen: Working in the Education Division

Before becoming a Digital History Fellow here at Mason, I taught American History to students in grades 7-12 for fifteen years. In planning lessons over those fifteen years, there were some online sources I returned to repeatedly, such as Herbert Hoover’s “Success of Recovery” campaign speech in 1932. Students liked being able to both hear and read the President’s words: “…the gigantic forces of depression are today in retreat.” It wasn’t until I began my fellowship that I learned that the site I bookmarked—History Matters—was created here in the Education Division of RRCHNM, the product of a collaboration between the center and the American Social History Project. As I continue this transition from full-time teacher to full-time student, I appreciated beginning my work in this division.  

The first project, Understanding Sacrifice, has two components. The first is a professional development program for teachers across subjects, who conduct research and develop lesson plans using the resources of the American Battle Monuments Commission. The second is an online repository of these lesson plans, as well as supplemental teaching resources for teachers. During my rotation, my work focused on the online repository, inputting images and sources into the project website; proofreading and editing lesson plans and associated materials; and captioning both eulogy videos honoring fallen service members and short PD videos for teachers. Inputting the images and sources on Drupal gave me an opportunity to use HTML, which gave me a flashback to the days when I used Adobe PageMill. I was able to lean on my classroom experience to effectively proofread and provide feedback on the lesson plans and materials. Having shown many a YouTube video clip in classrooms filled with a wide range of learners, I know how important having accurate captions are; captioning the eulogy and PD videos allowed me to learn more about the individual service members’ lives and develop a new skill. 

The second project, Eagle Eye Citizen, is an interactive designed for middle and high school students which encourages them to explore civics and history by way of primary sources at the Library of Congress. I found myself moving toward almost exclusively using primary sources in my classes in the last few years, so I was eager to see and use this interactive as it moves toward going live. I worked on testing Eagle Eye Citizen for functionality–Does this link work? Does the link open correctly? Does the image open in a new tab?–using different operating systems and internet browsers. This was a time-intensive task, but I enjoyed exploring an interactive and investigating it for possible issues. It also reminded me of how much we take for granted that when we click on a link that it will take us to the correct place. In testing, I had the opportunity to create various challenges within the student portal, which allowed me to review Library of Congress resources and design questions. I appreciated this functionality of Eagle Eye Citizen, because it places students in a position to both apply what they already know and create new knowledge. 

Supporting the production of two online projects utilizing primary sources, designed to encourage civic and historical understanding in classrooms over the last few weeks has been insightful. I look forward to seeing both go live in the weeks to come. 

 

Fall 2016 – Research Division

This semester I worked with the Research Division on Digital Humanities Now.  I was tasked with inventory and assessment of the over 500 subscribed feeds.  These feeds were/are primarily personal or institutional blogs related to the digital humanities.  Since DH Now lives here at CHNM, there were a lot more history blogs than there might be if it lived somewhere else, but there were many entries in literature, anthropology, cultural studies and perhaps most active recently, libraries, museums and cultural heritage institutes.  I cleanup up the site by removing a couple hundred broken and abandoned blogs, and moved 50 or so to their new homes.  I also categorized the entries by discipline and organized the sites by frequency.  There was a meeting to see if folders would be helpful to the editors, but it seemed that it wouldn’t really be of much help.

If I were to make some cursory observations from the DH Now feeds, I would say that it seems like personal blogs are not as popular as they were five years ago.  Most of the ‘big’ names if you will can publish on larger audience platforms – online journals, news sites, etc.  This is a great opportunity for graduate students to work with original scholarship into the blog post medium, since it might a bit harder for them to get ‘DH’ thought pieces onto HuffPost.  I fear however, that microblogging takes up a lot of time.  I also saw a lot of blogs that lasted as long as grad school and then were abandoned or turned into personal sites with links to syllabi and monographs.  At any rate, if the quantitative trends in digital humanities are to serve as guideline for making assertions, it really isn’t right of me to make these kinds of generalizations without a real data set.

Third Stop: Public Projects

On February 08, 2016, we started our time in Public Projects working with Sharon Leon, Megan Brett, and Alyssa Fahringer. We began by taking a look at the work the public projects division had done so far in order to have an understanding of the kind of work the division did.

The next task was a familiar and welcome one for me, testing. I have had a lot of fun testing the various projects for all of the divisions this year. In public projects, I did some testing for Omeka.net, Omeka S, and Liberian Journey. I particularly enjoyed doing the testing for Liberian Journey because it was a new experience for me: testing the mobile capabilities of the site. I found myself looking for issues I had not previously needed to look for in a site such as how easy it is to move around, if content runs off the screen, how different does the page become depending on how the phone is held? However, I also felt limited on what I could test as I was only able to test its functionality on an iPhone.

Another task I had was to review pieces for Mall Histories and go on a hunt for a photo for a Mall History biography piece. I did broad searches in engines and through digital collections such as the Library of Congress and was not able to find anything. However, through a Google search for the individual I found a pdf of a finding aid from a law school, the individuals alma mater. The finding aid allowed me to see that they had multiple photos of him. However, they were not digitized so I wanted to see what I could find before emailing the institution. Luckily, the archives had digitized many of their yearbooks, so my next step was to find him in them. With only being able to estimate when he would have graduated from the law school, I looked at about ten yearbook before I found him. The picture would be small, but it was definitely better than nothing. I emailed the institution to ask if the yearbook photo could be used for Mall Histories and, unfortunately, they have yet to give an answer.

The remaining, and majority, of my time was spent preparing for and advertising the five year anniversary of Paper of the War Department. First, Andrea and I sat down to brainstorm on the audience we would like to reach and how we could go about it. After meeting with Megan and Alyssa, the four of us created a plan and divided up the audiences; I was assigned the Native American studies crowd. Before any groups could be contacted, though, we needed a press release. Over the course of a week, Andrea, Megan, Sharon and I wrote a general press release. I then edited the release to target the Native American studies crowd. Knowing my name, as a new scholar, would not have any pull in the community, I contacted Dr.Joseph Genetin-Pilawa to post the targeted press release to his Facebook page as well as on the Ethnohistory and NAISA Facebook pages. I personally posted the targeted press release on H-Net in the AmIndian, West, and FedHistory channels. Lastly, I created tweets using #Indigenous and #NativeAmerican to be scheduled on Twitter with the PWD account.

Overall, I am highly satisfied with the work I accomplished with working in Public Projects. I took a look specifically at the amount of accounts created on PWD from March 17-April 4 (after the initial anniversary outreach) and out of 23 new accounts, 7 were created with a motivation of Native American studies; this is more than any other motivation with specific research and genealogy tying for second at 5. After looking at all of the data, I would have to say that the 5 year anniversary outreach was a success.

Second Stop: Research

The second rotation at RRCHNM was research for Andrea and I. We worked with and were supervised by Stephanie Westcott. Although the first assignments had us working with Stephanie, the majority of our time in Research had us working along-side the graduate research assistants Mandy ReganAmanda Morton, and Josh Catalano.

My time in the research division started a little differently than my time in Education. The first thing we did was familiarize ourselves with documentation for PressForward. We read over all posts from its conception to PF3 in order to prepare us help Stephanie do some research for a white paper. The experience research for a white paper was interesting. When I have done research in the past it had never been on something related to the digitl realm where all sources will be online. However, for the whitepaper we were researching information about Creative Commons Licensing, what people say about it, and the best ways to use it. Additionally, Stephanie wanted us to keep our eyes out for anything that may work better. I discovered that Creative Commons has a Science Commons they created for online science publications. It is not as well publicized, but there was a lot written about it when it started up so it was interesting to be able to compare the two.

The rest of my time was spent mostly doing different sorts of testing for Mandy and working in DHNow. With DHNow I worked as editor-in-chief for two weeks before the start of the spring semester. Sitting by Josh every week, who I have seen be editor-in-chief many times, I had an idea of what to do. Also, my work nominating content each week prepared me for knowing what kind of content I was looking for. However, it was still the beginning of the year and not much was being posted on the digital humanities. I also experienced how helpful editors-at-large were because each week there was only one nomination waiting for me. With a lot of searching through the content and Twitter along with some reassurance from Stephanie that the posts would work, I was able to get two editors’ choice pieces up each week along with four news pieces (which I was surprised ended up being even harder to find).

Also for DHNow I drafted some blog posts to explain the upcoming user management system, answer some questions in a FAQs format, and explain the two methods for nominating content through (Pressforward and bookmarklet).

Lastly, I tested the Turnkey theme for Mandy and the new user management system. The testing of the new theme allowed me to start getting used to Github, a website I had watched tutorials on in September before starting in Education but had no experience in. Mandy showed me some basics on getting around and where to report any issues. By the end of the testing I was fairly comfortable with Github which I imagine will keep coming up the more work I do at the Center.

That’s all for now, next up on the rotation is Public Projects!

Education Rotation

It was a busy start of the year in the Education Department at CHNM.  I worked on data cleaning for the American Battle Monuments Commission (AMBC) War Dead Database, transcribed Sacrificing Freedom eulogy videos, prepared/uploaded Lesson Plans for ABMC’s new Education Site, and did a content inventory for the National History Day redesign.

Working the war dead database I came to understand that optimizing search and sorting for large data sets involves strategic efforts to ensure proper data importing and input, detailed taxonomies, multiple testing stages and checks for uniform outputs.  My job was primarily searching, sorting and testing cross-browser functionality, but in the process I was able to come gain some insights into how the data set was moved from the old to new system, that could be of benefit if I work on any other data migration projects.  I also was able to get to know a bit more about the different ranks and divisions in the U.S. military.

By transcribing eulogy videos, I was reminded of the importance of accessibility to digital work.  Furthermore, the people in the database entries came to life . The Understanding Sacrifice project works with teachers to develop lesson plans on WWI, by researching individual soldiers and eulogizing them at their overseas resting places.  I was moved by the teachers attachment to their subjects.

I also helped CHNM’s filmmaker Chris Preperato identify selections from project leaders and teachers interviews for the Understanding Sacrifice intro video.  This helped me understand the goals of the project facilitators and see that they were met by the reactions of the teachers.  Teachers were reinvigorated as working historians by doing primary source research on the First World War.  They made lasting connections with the families of fallen heroes.  Perhaps most importantly, they were able to channel the power of place, connect it the lives and stories of individuals on the battlefield, and bring that knowledge back to the classroom with renewed vigor.

In a time when middle and high school teachers are sometimes treated like little more than pre-packaged content distributors and assessors, projects like these seem to make them feel like experts again, with unique experiences to share with students.  Jennifer explained to me how impressed the teachers were that their final lesson plan products were professionally designed and distributed.  When marking up the lesson plans with some html, and uploading documents, I was able to see the great variety of ways that the history teachers approached their lessons, which could be helpful in my own teaching.  However, the painstaking detail to each minute process and attention to national standards, reminded me that a career in secondary education will likely not be in my future.

One of the major takeaways from this experience would be the importance of close collaborations.  Understanding Sacrifice is a collaboration between CHNM and National History Day (NHD).  During my work tenure, NHD had trouble putting together a birthday video for one of their major donors.  On short notice, Kelly was able to step in.  I helped by taping the directors message while Chris was on vacation.  (Note:  the WWII memorial is windy and loud, so if you tape there, be prepared)  Despite my bad audio collection, Chris was able to get together tons of other footage and testimonies and Kelly hired a professional musician to score the video and help with other audio layovers.  I hear that the major donor is really thrilled with his video and shows it to all of his friends.

In sum, I think that the flexibility of working relationships,  i.e. going outside the box with professional development like Understanding Sacrifice and being able to solve partner problems on the fly without huge administrative hurdles, shows how the Education Department at CHNM knows how to make things happen and is dedicated to serving the needs of partners and teachers in unique ways.  It is a model example of how to develop dynamic working relationships and lasting professional collaborations.

Collaborative Second Year Post

We’ve reached the end of our two-year stint as Digital History Fellows at RRCHNM. The time we’ve spent at the center has introduced us to various tools and techniques, provided the opportunity to work with scholars, given us insight into the process and progress of grant-funded DH projects, and enabled us to build a supportive cohort of students across the program that will continue to serve each of us as we move into the next stage of our programs. Below, each of us will expand on the experiences we’ve had at the center and reflect on the work we’ve done.

Anne

The structure of the DH fellowship helped me to gain knowledge and skills of digital history in a meaningful way—one that assisted me in learning more collaborative ways of doing history, achieving more skills to accomplish creating digital history, and understanding the reasoning behind doing DH. During my first year, we were able to travel between the divisions, which allowed for a relatively quick overview of the different ways that digital history is done. In the second year, I was placed into two divisions—one each in fall and spring—and I was able to delve further into particular projects within these divisions and work more closely with the members of each division.

The Center for History and New Media is structured in such a way that open collaboration and communication is possible. Although there are three divisions, there are open discussions for ideas, collaboration amongst the members, and many people that are very willing to help if needed. Through my work here, I’ve learned that many people in the Center use different tools to create their work, and this has helped me to become exposed to new methods. There are also several meetings in which ideas are discussed, and these meetings are productive for learning new ways to do Digital History.

I had a much easier time with my trio of Clio classes due to my time as a DH Fellow. When I came in, I had some experience with certain tools, but I did not feel confident in my ability to actually do digital history. Our classes have changed that, and my time at the Center was very complementary in that it seemed whenever we were doing work for the Clio classes, we were also working on something similar within our CHNM work. It also was a great establishment of skills for taking Clio 3, which involved much more programming. Because of my time at CHNM, I had previous experience with some programing languages, and it made the process of taking Clio 3 much easier so that I was able to produce a meaningful piece of scholarship in the end.

In the future, I plan on taking the ideas of collaboration, communication, and the skill set that I have gained from CHNM into my career as a historian. Since I plan on working in a public history setting, I feel that the ability to utilize these skills will further my ability as a historian.

I believe that one of the most meaningful activities of my time at CHNM was the building of relationships with my colleagues through our mentoring and support space. Although we were all working on different projects throughout the two years of our DH Fellowship, the availability of mentoring—first with the third years mentoring us and then us doing the same for the first years—allowed us to communicate, collaborate, and to learn from each other. I believe that this is one of the most important aspects of the DH Fellowship, as it fosters an environment that promotes this type of dialogue for our future careers and work, whether inside or outside the academy.

Mandy

The second year of the fellowship, for me, has been incredibly useful.  I’ve really enjoyed being positioned on PressForward in the Research division. My work in this division has allowed me to further develop my programming skills, stay current with the latest DH scholarship through DHNow and the Journal of Digital Humanities, and participate in the development cycle for an open access piece of software.  Our first year of the fellowship was focused on testing various tools and becoming familiar with different platforms and approaches to Digital History.  This year I’ve moved into more of a building role and have had the opportunity to draw on the programming skills I’ve developed to contribute to the PressForward plugin. The structure of both the first and second years of the fellowship compliment each other well and has provided me with a broad knowledge of the centers organization, various digital history tools and approaches, as well as a chance to implement and build on what I’ve learned.

When I began this fellowship, the structure of the center was very unclear to me. However, through our rotations and experience in each division, I’ve become familiar with the current structure of the center, its origin, history, and its position in the larger field. CHNM has a long history of collaborating with teachers and schools, museums and libraries, as well as individual scholars and researchers to produce tools and projects that are innovative and sustainable. Participation in the Open Source community has been important to projects like Omeka or Zotero and has created a group of users who are active in testing and developing for these projects.

The digital history coursework we’ve been required to complete has often complimented our work at the center and helped to shape my views on digital history. Our practicum at RRCHNM provided practical hands-on experience while our coursework often provided a theoretical and sometimes historical perspective on Digital History methods, tools, and projects. I think taking these courses as a fellow gave me a unique perspective and some unique experience in Digital History.

Looking forward to the next year, I am planning to finish up prepping for my comprehensive exams and prepare my dissertation prospectus in order to advance to candidacy. Over the summer, I’ll be working on developing my dissertation prospectus and working to develop a proposal and plan for a digital component. My experience as a Digital History Fellow has shaped the way I’ve conceptualized using digital methodologies and techniques in my dissertation and has helped me to develop some of the skills that will be necessary. Because of the work I’ve been involved with at the center and my digital coursework at GMU, I have a realistic idea of what will be required to build a digital component.

The projects I have found most valuable during this fellowship have been projects like our THATCamp Topic Modeling project where we generated a data set about a center project and mined it. This project, in many ways, was a productive failure and I benefited greatly from it. Looking back on the project now, a year later, I realize many of the assumptions we made were flawed and we could have extracted and cleaned the data in both a reproducible and an easier manner. Projects where the fellows are given creative license to draw on techniques and concepts discussed in our coursework in order to create something based on a center project (or on center history) is, I think, extremely valuable for Digital History Fellows. These types of projects are also ideal for fostering and promoting mentorship among the fellows.  Spencer Roberts was such an important resource for us during the THATCamp project and we couldn’t have completed the project without him.  He offered advice on how to approach the project, explained programming concepts, and worked with us for several days on troubleshooting our python script.  Through this project, as well as projects like creating the RRCHNM Omeka Archive for the 20th Anniversary, I gained valuable insight into what it takes to accurately and realistically conceptualize a digital project as well as experience thinking through critical choices like information architecture with the user in mind. We were often faced with unexpected challenges and messy data along the way. I’ve taken a lot away from these projects and I think they are a valuable and unique aspect of the fellowship that should be continued and implemented in a thoughtful way for future cohorts.

Jannelle

Recently the next cohort of PhD students visited GMU. As we sat with them and described the fellowship track and digital coursework, I began to reflect on my own experience along these lines. It is surprising how quickly we were incorporated into the activities of the center. The structure of the fellowship was remarkably useful in this regard- we were introduced to people and projects in a six week cycle that provided a low barrier to entry. As we moved across the center, we were able to identify the projects and skills that appealed to each of us. The second year took this process further. Moving into a single department meant that each of us was able to take a larger part in the work. Each of us was able to explore subjects of interest and work more extensively with others within that division. In my case this meant a fall semester in the Education division working on the 100 Leaders project and a spring semester in the Public Projects division working on the Mall project. Working more extensively in one division meant that each of us had to balance the responsibilities of the fellowship with our tasks in each division, but in most cases we were able to manage these well.

Working as a DH Fellow has definitely guided the direction of my coursework. I entered the program here at GMU with very little technical experience. Working at the center enabled me to build skill and confidence in these areas. It definitely gave me the confidence to enroll in Clio 3; Programming for Historians without these valuable experiences. I also found the Support Space to be a valuable aspect of my time at the Center. Bringing my challenges to the table and helping others with their work allowed me to create and build relationships with other students in the program. Oftentimes, we would spend time talking a problem out together and I found this type of collaboration particularly edifying. Last spring, Mandy Regan led a group of students in our Clio 2 class in a tutorial on 960 grid. This impromptu tutorial was a great example of the way that we were able to bridge our coursework with the fellowship. These activities have fostered collaborative relationships that continue to encourage us to share techniques and digital work with one another.

I’ve written on this subject in the past, but the preparation we did for the 20th anniversary was particularly meaningful for me. We started this work as a group and over the course of the summer I expanded the repository to include the many projects in the Center’s history. The process enabled me to read each one of the grants in the center’s history. Quickly I gained a better understanding of how the field has changed in 20 years. The project forced me to reconsider tools like Zotero as part of a larger vision. To think about projects like History Matters in terms of the other work the center has produced. To put them on a timeline and to view them not as discrete but connected by a thread or an idea. I learned more about iterative projects and the complexities of collaboration. Considering these things while I was working through my coursework enabled me to make connections with readings and class discussions. The experience encouraged me to see these projects from multiple perspectives.

When I reflect on my time as a fellow – this project encapsulates the value of the fellowship for me. It encouraged me to think about the legacy of digital history projects while also considering what is to come from the field. It is a project that will be difficult to duplicate, but one that would serve future Fellows in a meaningful way.

Next year, we all move on, either as a Graduate Research Assistant at the center or as a Teaching Assistant in the Department of History and Art History here at George Mason.  Although our stint as Digital History Fellows is over, we all agree that it was a beneficial experience and we look forward to seeing what future cohorts will do.

 

A Tale of Two Projects

In a week’s time, the semester and by extension the DH Fellowship will come to an end. As such, it is time for the end of the semester blog post. IN the time since my last blog post, I have had divided my time into two projects associated with Digital Humanities Now. The first project (Web Scraping) was focused on the content published by DHNow while the second (Web Mapping) focused on DHNow’s Editors-at-Large base.

Web Scraping

Over the years, Digital Humanities Now has published hundreds of Editor’s Choice pieces. For 2014 alone, roughly 165 Editor’s Choice articles from numerous authors were featured. Such a large corpus of documents provided a ready source of data about the publishing patterns of DHNow. In order to translate the documents into usable data we needed to format the Editor’s Choice articles into a usable format, namely machine-readable text. The task, then, was to go through each Editor’s Choice article and scrape the body text down into a .txt file. I had never scraped a website before, so this project was going to be a great learning opportunity.

I began the project by reading through the Beautiful Soup web scraping tutorial on Programming Historian by Jeri Wieringa. It uses a Python library called Beautiful Soup to go into a website and scrape the data. During my rotation in the Research Division last semester, the three first year Fellows had quickly worked through the Beautiful Soup tutorial but I needed a refresher. However, I made a switch from Python and to R. This change came from the suggestion of Amanda Regan who has experience using R. As she explained it, R is a statistical computing language and would be a better resource in analyzing the corpus of Editor’s Choices than Python. After downloading R Studio (a great IDE) and playing around with R, I found it to be a fairly intuitive language (more so for those who have some background in coding). I came to rely on Mandy and Lincoln Mullen when running into issues and they were both extremely helpful. Learning R was fun and it was also exciting as R is the primary language taught and used in the Clio Wired III course, which I plan on taking the next time it is offered.

In order to scrape the body text of each post, I relied on the class names of each html tags containing the text. I imported in a .csv file of all the Editor’s Choice articles and search each website for a specific class name. When found, R would scrape all the text found in that tag, place it in a .txt file whose name corresponds with the articles ID number. Finding the class name was a hang up, but I was able to use the Selector Gadget tool to expedite the process. It essentially makes your webpage’s css structure interactive allowing you to click on items to view their extent and class names. I learned a lot about website structures in while identifying each body text’s class name. In the end, I was able to scrape 150 of the 165 Editor’s Choice articles.

You can find my code on my Github account here.

Web Mapping

The second project I was fortunate to work on was displaying our Editor-at-Large spatially on a map. My undergraduate work is in Geographic Information Systems (GIS) so this project in part came out of my interests and prior experience. In association with this project I am writing two blog posts for the soon to be DHNow blog. The first will detail the process of developing and designing the map while the second will delve into what the map is “telling us.” For the sake of the Fellows blog, I will instead reflect on my experience in creating the Editors-at-Large map and will link to the other two blogs when they are published.

It had been almost a year since I devoted any real time to cartography. I decided to use the same model I went through in my undergraduate capstone class on web mapping. To being with, I needed a dataset that I could use on the web. During my undergraduate, I used ArcGIS to convert a .csv into a geoJSON file that could be used on the web. However, since coming to GMU and the Center, I have embraced Open Source (both by choice and by financial force) and instead relied on Quantum GIS (QGIS). I had no real experience with QGIS so this project provided me an opportunity to become familiar with the QGIS platform. This was an added benefit that I both appreciated and enjoyed. In the end, converting to a geoJSON format was fairly straightforward.

To render the web map, I used Leaflet, which I was introduced to in my undergraduate coursework. While as an undergraduate, I found Leaflet somewhat difficult to use but this is probably because I was simultaneously learning HTML, CSS, and Javascript while working with Leaflet. Returning to Leaflet, my impression was how easy it was to use and its fairly intuitive design. I attribute this change in attitude to the training in and supportive nature of the Research Division as I was exposed to Python and other coding languages. In the end the map turned out pretty good and my work on the project has reignited my passion for cartography and all things spatial.

In the final days of the Fellowship, I feel both excited and melancholy. I am sad that the fellowship is coming to an end and I am moving out from the Center. It has been a wonderful experience working with great people on interesting and engaging projects. Yet, it is exciting to think back to myself on the first day of the Fellowship and realize how far I have come in my digital work.

On Mentoring

Last year all of the second year fellows benefitted from the mentorship provided by the second year students. My mentor was Amanda Morton and throughout the year she offered assistance in the various divisions, especially when I began on the PressForward Project in the Spring and Summer of 2014. In addition, Spencer Roberts helped us on various projects and his support throughout the year was invaluable.

This year I’ve had the opportunity to mentor Stephanie Seal. We’ve jointly produced the Digital Campus Podcast several times and I’ve offered her assistance on projects when she has needed it. The new cohort’s first rotation this year was in Research and for the first few weeks they worked on PessForward. As the digital fellow positioned on the PressForward project, I assisted in helping them set up their own WordPress blogs on the dev server, showed them how the plugin worked, and guided them through being both Editors-At-Large and Editors-In-Chief.

During the second semester each fellow was placed in a division. Jordan Bratt came to research and worked with us on PressForward. One project he spearheaded was learning R to scrape and download some Editor’s Choice pieces for a mapping/text mining project. I was able to take some time this semester to work with him to write some “if” statements in R since I am somewhat familiar with the language. He’s done an amazing job on the project and its been fun to watch him further develop his skills and do some interesting things with the DHNow data.

Aside from working with the first years on PressForward and with Stephanie on Digital Campus we’ve also used our roles as mentors to help out in the Support Space. During the fellows time in Clio II, I’ve assisted several students with things like learning the 960 grid (an easy way to quickly structure the layout of a site) and troubleshooting code. I think the mentorship program is very useful in the sense that it brings the two cohorts together across projects and promotes collaboration. Being stationed on one project has meant that I always have things to do aside from fellowship responsibilities. The mentorship program has allowed me to take time to work with Stephanie and the others through both the support space and collaborative projects like producing Digital Campus.

Reflections on Spring Semester

This semester I’ve continued my work on the PressForward project in the Research division. Throughout the semester I’ve served as editor-in-chief, helped troubleshoot and test the latest version of the PressForward plugin for public release, and continued to develop my php and web development skills by working on the TurnKey PressForward WordPress theme. In addition to working on PressForward, I’ve helped out in the support space, organized a brown bag, and spent some time mentoring Stephanie Seal. My time in the Research division on PressForward has allowed me to develop my programming skills and further acquaint myself with the software development process. I’ve learned so much about programming in general over the last two years, but I’ve also gained valuable experience in things like UI/UX design principals and about the workflow for developing/maintaining an open source piece of software.

The PressForward All Content page in 3.5 features improved navigation, filtering, sorting, and searching.

The PressForward All Content page in 3.5 features improved navigation, filtering, sorting, and searching.

In March, PressForward released version 3.5 which included some significant User Interface(UI) and User Experience(UX) changes. This version was the result of several months of work by the PressForward team and included a redesigned toolbar in ‘Nominated’ and ‘Under Review’ and some reorganization of tools and options in the plugin. Throughout the first months of this semester, I attended development meetings, tested new features, and helped to rewrite our documentation based on the new features. Releasing a new version of the software is a big task as it involves updating all our documentation, screenshots, and descriptions of the plugin. 

Output of the Subscribed Feeds Shortcode in the PressForward TurnKey Theme

Output of the Subscribed Feeds Shortcode in the PressForward TurnKey Theme

Building the PressForward TurnKey Theme allowed me to apply a lot of the concepts I was picking up through bug-testing and in the weekly discussions with our developer Aram. For example, I helped to write a shortcode that displays a list of the subscribed feeds and aims to allows PressForward users to further expose the metadata collected by the plugin. We came up with this idea after realizing how many of DHNow’s feed were broken and how poor the metadata that is associated with the feeds often are. Attributing credit to posts we feature when the author is not clearly listed in the metadata is often difficult and problematic. The shortcode allows users to highlight the RSS metadata pulled in by the plugin by providing options for displaying both active and inactive feeds. We hope allowing administrators to make their feedlist (as well as the feed title and author) visible outside of the plugin will prompt scholars to revisit the metadata contained in their RSS feeds. Participating in development meetings this semester, I have not only continued to further my understanding of the backend of the plugin but also have learned more about php and WordPress core. 

My work on PressForward has been immensely helpful in building my programming skills and as I look back at the last two years of this fellowship, I’m struck by how much my skills have grown. In addition to technical skills, I’ve also gained experience in managing an active publication and an open source project. Thanks to projects like our cohort’s THATCamp topic modeling experiment in Python, the Clio Wired sequence, the support space, and my time in Research my skills have vastly improved. As I finish up this fellowship and look towards beginning my dissertation and developing a digital component, the skill set I’ve cultivated through this fellowship will be immensely useful. At the very least, the skills I’ve developed her have given me a foundation in computational thinking and I feel confident in learning whatever new programming skills will be required for my own research.

Aside from our duties in our respective divisions, the fellows have also had some common projects we’ve worked on.  Stephanie Seal and I produced several episodes of Digital Campus this semester and continued to maintain the blog.  Producing Digital Campus involves finding stories for everyone to discuss, managing and scheduling the recording, and preparing a blog post summarizing the episode for the Digital Campus blog.

Additionally, each year the fellows are asked to host and organize a brown bag at the center.  This year I invited Micki Kaufman down from the City University of New York to talk about her dissertation research, entitled “Everything on Paper Will Be Used Against Me”: Quantifying Kissinger, A Computational Analysis of the DNSA’s Kissinger Collection Memcons and Telcons.” I had previously met Kaufman at the 20th Anniversary conference and the brownbag was an excellent opportunity for the fellows to invite down another graduate student and participate in conversations about digital methodologies and approaches as they apply to a dissertation.