In between working on other projects, like typesetting articles for Carleton’s Undergraduate Journal of Humanistic Studies and slowly filling a spreadsheet with lemma and definitions of Latin vocabulary, I’ve continued my Unity training. In this tutorial, I learned more about lighting, assets, and scripting. I also built my first game controller to manage score-keeping and UI (user interface) and added my first sound effects.
Adding the game controller created some logistical problems which, though I’m new to them in Unity, are very familiar to me as a programmer. Essentially the problem is that when different objects are separated out, their information and variables are private. Sometimes, for instance, the game controller doesn’t have a way of observing something that happened to the player object, but it needs to be able to act on that information. Setting up the objects so that they can communicate about events is essential, but it’s not always obvious in the beginning that they need to share information. Figuring out that aspect of scripting will be very important in scaling development from demo-sized games to the large Unity project for which I am training.
A significant part of my work continues to be for Team Workhouse, including the work I did over winter break forProfessor Susannah Ottaway ‘89. My earlierpost detailed my process for determining the locations of parishes in England in order to better understand the use of workhouses for poor relief in the late 18th and early 19th century. I continued to find locations over break, and then double checked those locations I had found to make sure I hadn’t missed any parishes and so I was confident in the new locations. Finally, though, I finished that and reached a point where I could leave the spreadsheet behind and begin mapping! Of course, I quickly learned that you can never really leave the spreadsheet behind.
A map showing all parishes with access to a workhouse in England and Wales.
I quickly ran into a problem: I was working from home, so I only had access to ArcGIS online, which, while a great tool, is not as powerful as the desktop version. The online version will only take up to 1000 entries in a CSV upload at a time, and the database has a little over 3300 entries! I was able to get around this by splitting the spreadsheet into four separate uploads, broken up along county lines to make my life a bit easier. I finally got all four CSVs into ArcGIS online, double checking that all locations were in fact in the map document.
Once I had all the locations in, I was finally able to step back and look at the data as a whole (insert my rough map of all the workhouses colored by county). I soon noticed what looked to be another problem. Since the parishes were colored by county, there were some obvious outliers. In addition, I had imported a layer that showed the 1851 county boundaries, and many of these outliers did not match the county boundaries of that layer. I went through the counties again, looking at parishes that were at least three miles outside of the county boundaries, recording those that fell outside those boundaries to later check to see if the location was correct, and potentially correct it.
An example of the 1831 English counties and exclaves.
While I did find some incorrect coordinates, many of them were actually correct. As I dug into the parishes I thought were incorrect, I learned that many county borders had changed, and many had even had parts of their counties that were not continuous with the rest! Fortunately, I was able to find a layer file of the English and Welsh counties in 1831 courtesy of the Cambridge Group for the History of Population and Social Structure , when many of these exclaves still existed. Using this layer, it was much easier to visually check that parishes seemingly outside their counties were in fact within their boundaries. Once again, the county layer made my life much easier – instead of going back through my spreadsheet, quicker visual checks were now possible for what I thought were incorrect – and many did turn out to be correct.
A map showing the number of parishes with access to a workhouse by county.
Now that I’m confident in the parish locations, my next steps are to really dive into the maps and cartography. The data for the maps is all there, but the task now is to create polished maps for both print and online publication. Despite some of my struggles with both the technology and the content (I had no idea that counties could have exclaves!), the use of GIS was a valuable tool, not just for the cartography, but also for the vital step of confirming that parishes were actually where they were supposed to be.
Most my work this term has been part of Team Workhouse, which is a research project that aims to create a digital reconstruction of the Gressenhall Workhouse in Norfolk, England during the 18th century in order to better understand the lived experience of workhouse inmates (my research this summer and presentation at the Midwest Conference on British Studies is also part of the Team Workhouse). This term, I’ve been working mainly on locating British parishes in the early 19th century. Our goal is to create maps and explore spatial relations of workhouses in England, based on an 1803 Parliamentary report. Professor Susannah Ottaway ’89 and others have already done significant work on finding the locations of the parishes and other places mentioned in the report. There are still many that don’t have locations, however, and that is what I’ve been working on. Although we ultimately want to know where the workhouses were, that information is not accessible to us at this time. We can find the location the churches, and often workhouses were very close to churches. In addition, the maps will be show larger areas, so individual parishes will be relatively small. As such, we have decided to use church buildings as approximations for the parishes and their poor relief.
My typical process looks like this: I would have a parish name (for example, Dowley, Magna, Wellington Division, Bradford Hundred in Shropshire), and would begin on a genealogy website to find out some preliminary information about the parish. I can typically get a church name (for example, Holy Trinity), and I then look to the Historic England pages for more information on the church building. This is the Historic England page for Holy Trinity, Great Dowley, from which I know that the current building is from 1845, although the site is older. I find the church on Google Maps (with the map on Historic England to help me), and use the coordinates for the parish.
A document of notes on parish locations for the Workhouse Project
Some places pose more challenges and require more investigation. In London, many of the parish churches of parishes listed in the 1803 report were destroyed in the Great Fire of London in 1666 and never rebuilt. For those parishes, I used this map, which shows London before the Fire. Even so, the streets have changed since then, so I had to estimate where the churches would have been. Another very common issue I have run into is name changes. “Warnslow” becomes “Warslow,” “Laytham” becomes “Layham,” and “Monythustoine” becomes “Mynyddyslwyn” (or “Mynyddislwyn” or “Mynydd Islwyn”). Some name changes are close enough that I am confident they are the same place, especially given the extra information, such as church name or county. Others, I find sources about the different names (especially that last one) to confirm that they are indeed the same place. For the most difficult parishes, I often had to resort to Google searches, old maps (there are many here!), and any other resources I could find on small parishes. I increasingly appreciate parish websites that have histories of their own parishes, which have been very valuable to me during this processes. It has taken many hours, but I have almost finished finding the unknown parishes, so before long we can move on to mapping the parishes and exploring the spatial patterns of 18th century poor relief.
Hello! The end of fall term is near and the time seems ripe for another blog post. For the past few weeks, most of my digital humanities time has been devoted to developing and revising CSS quote styles for Global Religions in Minnesota, a locally hosted Omeka project that documents the lived experiences of members of various religious communities in Minnesota.
Because the research and content creation is primarily done by students enrolled in a Carleton religion class, it’s important that we make the backend user interface as intuitive as possible so that they can focus on research and writing. Eventually, the quote styles I created will be integrated into the WYSIWYG (what-you-see-is-what-you-get) interface in Omeka so that applying the CSS only takes one click. So far, I’ve made some styles for varying lengths of block quotes, which are portions of texts quoted from other sources and contrast visually with the main text. Below are screenshots of sample styles I made for short, medium-length, and long block quotes. I tried to apply the most visually striking styles for the shorter quotes and used smaller font and minimal graphics for longer ones.
A short block quote:
A medium-length block quote:
A long block quote:
To get feedback on these styles, I used CodePen, which is a neat website that allows users to edit source HTML/CSS/Javascript code and see changes in real-time. Pens are shareable with other team members and with the general public, which makes collaborative web design and idea sharing really convenient. Even if you’re not currently working on a web development project, there is a lot of interesting animation and styling work to look at for design inspiration!
DHA Elizabeth and Professor Austin Mason presenting at MWCBS
Author: Elizabeth Budd
This past weekend I presented at the Midwest Conference on British Studies (MWCBS) at Iowa State University in Ames, Iowa, along with two Carleton faculty members and three other Carleton students. Our presentation is part of a larger Virtual Workhouse project which utilizes digital tools such as serious gaming and 3D modeling to gain an understanding of the lived experience of workhouse inmates in 18th century England during the Houses of Industry period of poor relief. This past winter, I took a class co-taught by Professors Mason and Ottaway called Bringing the English Past to Virtual Life that brought these ideas into a classroom setting and allowed the students to research, model, and creatively construct new ways of exploring the lived experience of the poor.
Professor of History Susannah Ottaway, with two more Carleton students, presented a paper that explored spinning work in the workhouse, and whether it was driven by moral or economic objectives. Professor Austin Mason, Brittany N. Johnson ‘18 and I presented our paper, “Locating and Representing the Material Culture of the Poor” in the same panel. Our paper focused on the challenges of digitally reconstructing the material culture of inmates in the workhouse, based on the limited textual and material sources that survive. This past summer, Brittany and I spent two weeks in Norfolk, England, excavating workhouse objects from an old rubbish heap at Gressenhall Farm and Workhouse Museum. We found mostly objects of mid 20th century date, but the processes that determine object survival also apply to objects from the 18th and 19th centuries. We examined archival and archeological evidence of the Gressenhall House of Industry, in Norfolk, England, and explored the value of digital tools in that reconstruction, including SketchUp, Twine, and Unity 3D. Since evidence is limited, reconstruction is hard. Despite this, our paper argued that new questions emerge when using these digital tools that may not have been asked otherwise: What color is the cloth produced in the workhouse? What is the texture? What did the furniture look like? Where was it placed? These questions allow us further insight into the lived experience of the poor during the 18th century, which is difficult to get at through traditional historical methods. All these questions and more are born out of digital reconstruction, and while we don’t have all the answers, the exploration of these questions ultimately deepen our understanding of the past.
A flowchart illustrating how objects survive into collections at museums, and how other objects are lost.
It was an incredible opportunity to present at a conference with my professors and fellow students. The challenge and reward of preparing and presenting a paper that incorporates my own research was invaluable, as well as the chance to hear about and engage with other historians and their research in the wider academic world.
The very first issue of the Carleton Undergraduate Journal of Humanistic Studies is officially out! To access the journal, go to go.carleton.edu/ujhs. We are very excited to present eight pieces of scholarship from across the humanities disciplines. This project was the result of many hours of hard work and collaboration.
As a digital humanities project, this endeavor taught me many lessons about organization, collaboration, and planning. This journal has been a long time in the making, starting in the middle of last summer. Since that time, the project has taken on new members and grown significantly. We are currently accepting applications for next year’s editorial board and planning for the future.
Some of the greatest lessons I have learned from this project are as follows:
1. Organize, organize, organize! All projects must walk that fine line between details and the big picture. However, keeping documentation and having consistent policies made a huge difference in our process. We created a Google drive folder for our journal and started taking weekly meeting notes. This makes it easy to review what we have discussed and find our old notes.
2. Know when to set details aside. There were times when discussions about very specific points set our meetings back and we ended up spending a long time thinking about a minor issue. It’s important to keep these issues in mind but sometimes necessary to abandon them in order to keep things moving.
3. Seek help. We had lots of extremely productive conversations with our faculty advisors and research librarians. These conversations helped us better understand the process and provided us with valuable insight.
4. Communication is key. We experimented with different ways of communicating with our guest editors and making sure that all of our papers were edited on time. We are still trying to figure out the best way to ensure that deadlines are met.
5. Delegate. When we divided the work amongst ourselves, we had much greater success. Particularly with the copy editing process at the end of the project, delegation proved extremely helpful.
This project has proved to be an exciting part of my undergraduate career and I am so excited to see where the journal goes in the future!
I have been part of an initiative on campus to set up an online research journal for the humanities and our website just recently went live! We are soliciting papers that present original, polished research. This is a fabulous opportunity for students at Carleton to get their work published, as well as to engage with and practice the peer review process. I recently spoke at the Language and Teaching Center lunch about our project and I thought I would share some of my presentation here.
We chose an online journal format because we want to ensure ease of access to our journal and we are also excited to eventually collaborate with other undergraduate institutions. We are currently working on the formatting and production of a standardized PDF template in LaTex. We are hoping to have high-quality, uniform PDFs that can be downloaded from the web site. But we also want to retain the online reading experience and keep full text of the articles online. Some of the biggest challenges I foresee in this project are dealing with citations and footnotes, particularly as we are accepting papers from a wide variety of disciplines.
Right now our team consists of six editorial board members. We are in the process of accepting submissions and are excited to produce our first issue. Our goal is to get out of the first issue by midterms Spring term.
Last week, I met with Ann Zawistoski to refine our search for articles on facial recognition software. From that meeting, I was able to find a couple sources that look very promising for giving us the techniques and tools we need for identifying and re-identifying faces. Then on Thursday, we met again with Nat Wilson to go over our findings and discuss the best tools and sources we’ve found so far. This week, we’ll be working on looking through and ranking those tools we discussed on Thursday, as well as any others we find online that look promising. We’ll be using a set of criteria established over the course of the past week (things like ease of use, ability to do batch imports/exports of data, ability to maintain privacy, etc.). That way, we should have a concrete way to quanititatively determine the best tools by next week, with any luck. We’re looking to narrow down the tools we have to about 5-7 finalists, and then we can further narrow it down from there.
Graham and I recently started working with History Professor Susannah Ottoway in hopes of starting a new 3D Workhouse project. From her experience, students tend to learn much more effectively through visual means, and accordingly, she dreams to create a 3D model of workhouses, incorporating her lifetime research on social networking in 18th century England.
An existing site containing 3D historical models is the Centering Spenser website (http://core.ecu.edu/umc/Munster/) made by East Carolina University. Viewing this site as a model example (pardon the pun), we decided to have a Skype call with the Spenser creators from East Carolina University, to learn about their process and timeline.
Unsurprisingly, setting up a website with 3D models is huge and daunting – Centering Spenser took five years to initially create, and is still undergoing continual changes. Compared to us, East Carolina University already had a ton of resources for 3D modeling projects, like a pre-existing animation program teaching Maya to students. Perfect. A selection of animation students then hopped on the Spenser project, creating 3D architecture and models. Their process in creating the site was more organic and unstructured, letting the project go its way.
Awesome. We, on the other hand, are starting from scratch – it’ll be difficult, but hopefully possible. We’ve narrowed the project down to starting off with modeling just one room, or one corner of a room. Considering different types of 3D modeling software (Maya, Blender, Inventor, Sketch-Up), we are currently experimenting with their usabilities and how they match with our skills, along with prices and our (little) funding. Looking at other nearby schools, St. Olaf and U of M may also have 3D programs or experience… so, possible collaboration! Exciting! In the meantime, we’re also compiling images and information of objects and artifacts in 18th century England, to use as texture in 3D models. We’ll see where things go from here!
Currently, Sahree and I are working with Nat Wilson in the archives department to review existing facial recognition software tools. The end goal of this project is to be able to use a tool to recognize and label pictures of alumni with much greater speed and accuracy than we currently have by doing the process manually.To that end, the three of us are reviewing some articles this week dealing with exisiting tools. In particular, Nat gave us a list of 50 or so facial recognition tools (the list was current as of late 2013), and I highlighted five or so that I thought would be particularly useful. I tried to focus on tools that were free, independent of outside software (so we don’t have to send private information to external networks), and simple to use products designed to work on their own (as opposed to being part of a code library for use in developing larger applications).