— UA Dept. of REL (@StudyReligion) October 23, 2017
You may have seen this tweet. As part of the Public Humanities and Religious Studies foundations course in our MA program, I collaborated with Sierra Lawson and Emma Gibson and helped to build AARtifacts. The project was built in Omeka and is meant to represent interesting artifacts gathered from people’s experiences of the annual American Academy of Religion (AAR) meeting. So why did we choose to do this project? And how did we make it happen?
We went in knowing two things: the AAR was our case study for the semester and Omeka would be our platform for this particular project. A couple of brainstorming sessions later, we had decided to collect items from the faculty in our own department and create collections based on what we received. Sierra took on the task of trawling YouTube and Vimeo for relevant videos. Emma took the lead on scanning all of the old bulletins of from the academy. I photographed all of the physical items — tote bags and buttons, mainly. Altogether we had more than 100 items to catalogue.
Then came the part that actually involved Omeka. Omeka has a plugin that, ideally, should be able to upload a CSV document and separate your items automatically. This means that instead of entering each of those 100 items by hand, we’d be able to enter them seamlessly from the spreadsheet we had all contributed to. Except it didn’t work.
Obviously this was a source of frustration for all of us. We had used the spreadsheet format trusting that it would upload with no or minimal problems. So as Sierra and Emma started entering the items individually (mad props to them for being willing to do that), I went digging. I needed an answer.
The first problem I had to address was that Mike (our professor and the host of the project) would receive a detailed error message and all I got was “Omeka has encountered an error.” After a few clicks and some light googling, I was able to 1) make some files appear in Mike’s file manager that were hidden for the purpose of being more user friendly and 2) fix a line of code that allowed Omeka to read error messages to me. Now I was able to at least find out what the problem was.
After another couple of hours of trying to make the plugin work, failing, digging to find out what the error was, and even more googling — it sounds much more straightforward than it actually was — I found the problem. All I needed to do was enter the right path for the command line in the right line of code of the right file and ta-da it would work. I went back to Mike, let him know, and asked him to find the path I needed to enter. A few days passed (I later found out it was because he was waiting for me to finish my thesis proposal) and he sent me the path. He had already had it for another error he had encountered earlier on in his domain configuration.
I fixed it. I entered the path in the right line of code and it worked! Sierra and Emma had already entered almost 70 of the items and I was able to get the rest in that afternoon. After some tweaking and cleaning up from Mike, we have the project you see now.
So here’s why I bring any of this up in the first place: I had no idea that the one computer science class I took a few years ago as a math major would help me with a project in the humanities in grad school. But it did. I don’t know PHP, but I know the basics of reading code and can identify errors with a little bit of work. Maybe the new triple threat is a student who can not only think critically, but also work collaboratively and fix broken code.
Cross posted on Sarah’s website.
Mike Altman: Sarah, for our first journal reading group you chose the article “Durkheim with Data: The Databse of Religious History” from a recent issue of JAAR. What’s the gist of the article and why did you think we should read it in our group of MA students and faculty?
Sarah Griswold: The article is basically an introduction (and justification) for the Database of Religious History. This database is meant to serve two purposes: to be a database for “religious groups” in the premodern world and to provide evidence for a theory of religious evolution. In effect, the database tries to play both fields of holding and providing both quantitative and qualitative data. The article mostly reads as an attempt to draw more scholars in in order to add data to the database.
As far as why I thought we should read it, there were a few reasons. First, as someone with a background in both the humanities and math, I think understanding how and why qualitative data is quantified is really important to understanding and critiquing the purpose and use of databases like this one. Second, as the humanities (and particularly religious studies) moves more and more towards digital projects, we need to be aware of what’s out there so we can emulate what is done well and improve on what is lacking. Finally, the article also offers us insight into the theoretical workings of the project itself. Although titled “Durkheim with Data,” it seemed as though the creators of this project have not critically considered or defined the very categories they have opted to work within, making the move from qualitative to quantitative data suspect. That, I think, can be quite telling of the ultimate success or failure of a project of this size.
MA: As a student in this new MA program that has an emphasis on digital and public humanities what can you learn from this article and what can we as a program learn?
SG: Personally, this article reinforced the importance of thinking through the categories you use when quantifying data. It can be easy to point to something you “know” is religion and label it as such without thinking about why you’ve decided on that label in the first place. It’s also interesting to think about the collaboration across disciplines that these projects require. It would be impossible for one or two scholars to gain all the skills needed to make these things even work. It turns out that group projects exist in real life too and not just in school.
As a program, I think the biggest take away is to pay attention to the developments of these projects. Because the DRH has a capacity to refine their methods, I don’t think they should be entirely dismissed as uncritical. There are positive and negative take aways from critically examining any digital project. Learning more about digital projects and examining their goals and functions can and will tell us a lot about how to move forward in our own individual and collaborative projects.
Have you heard about the Religions Studies Project? It’s a great website and podcast based out of the United Kingdom. This week they are featuring a podcast episode with Profs. Mike Altman and Merinda Simmons all about our new Religion in Culture master’s degree program.
Professors around the department often talk about their “research.” But what exactly is that? It’s something to do with books and articles, right? In hopes of showing how some of us work–or at least how I work–below is a day by day running journal of a five day research trip I took to the Bancroft Library at the University of California, Berkeley.
Our first RSSA Coffee Break last month was a huge hit, and our next one is fast approaching! Be sure to stop by the lounge in Manly 200 on Tuesday, March 1st from 1:30-3:00pm and enjoy a free cup of coffee, on the house! Mix and mingle with your fellow REL students, and maybe even a professor or two.
We’re also bringing back Live Tweets from the Lounge for this Coffee Break! Dr. Altman will be live-tweeting the event, so find him on Twitter and keep those tweets coming! Don’t forget to tag it #LoungeTweets.
One of the major themes in my REL 241: American Religious History course this semester has been “religious liberty.” What our class has seen over and over again is that religious freedom isn’t really about religion or freedom. More often, arguments over “religious liberty,” “religious freedom,” or “freedom of conscience” are really arguments about governance, structures, and the individual. Continue reading
John D. James is a senior at the University of Alabama majoring in Religious Studies and minoring in General Business. This book review was written for Dr. Michael J. Altman’s REL 370: Empire and the Construction of Religion course.
In Mother Earth: An American Story, Sam D. Gill begins to articulate and explain with physical evidence that the term “Mother Earth” is commonly misused and presented to audiences as some common knowledge involving Native American thought and belief. Gill takes an interesting approach when trying to carefully argue that Mother Earth is not an ancient central Native American figure. This book’s message is a radical rethinking of how the figure Mother Earth came to be used and ultimately misused by so many who failed to ask questions concerning Mother Earth’s origin.
We love Thai food around here. But how do you know the food on your plate is actually Thai? What makes it Thai? The sign in the restaurant window? The “Thai tea?” What is “authentic Thai food?”
Well, the government of Thailand is sick and tired of your sad excuses for Thai food and they have a plan to ensure you never settle for fake Thai food again. It’s not just a plan, it’s a robot. Continue reading