We continue on our journey through the horrors. Is there anything more terrifying than the realization that you have been going about this all wrong? That you are not as well guarded from the monsters than you thought? That something has been lurking in the shadows this whole time…
That you’ve done stuff in a weird order?
“What do you MEAN most people actually have a plan for their terrifying quests and don’t just roll up to a haunted house they find to look around and go from there?”
Let’s take a step back for a moment and get into the context. Last semester’s Intro to Digital Humanities class ended with a final project – to create a proposal for a larger project that we could then build on further this semester. Alternatively, we could just write a paper instead, and then just jump on someone else’s project when the time came. Pretty simple, right? Except- well, last semester, for the first time ever, there was a secret third option – the dataset. Last semester, people had the option to put together a dataset, along with some documentation, with the idea that this data could be used for future research. The dataset wasn’t a formal project proposal but it was still a piece of a project – a piece of many potential projects, even, considering that the same dataset can be used for numerous purposes.
This new option ended up getting a lot of mileage – two out of the three teams this semester, including the team I’m on, have started not with a proposal, but with a dataset. We’re in brand new territory for this methods and practices class.
Usually, I would imagine, with a project starting from a proposal, you have a pretty exact idea of what you’re creating. Natalia’s Lunfardo dictionary for example, this semester’s one project that did emerge from a proposal, has a clearly defined output: an online dictionary to serve as a learning resource. My own project proposal from last semester was similar: its planned output would have been a digital timeline of a particular historical event. Based on my experience last semester, the “pre-work” for proposal-based projects mostly consisted of doing just enough research to refine your initial idea into something that you could be sure would work, then focusing the rest of your energy on planning out the process, on how exactly you will get it to work. Once you actually do the project, you’re filling the empty vessel you created, by doing further research, creating the content you planned to create, and presenting that to your audience.
But what happens when you start with the filling but don’t have the structure to contain it yet? Well, I guess what happens is what I described in last week’s post. But it did take me until this week to realize that wasn’t actually the intended progression. Which was admittedly a little alarming. Sometimes horror is about establishing clear rules… and then punishing even the people who follow them perfectly. In those cases, the fear comes from this idea that you can’t escape the terrible thing no matter what you do. But other times, horror establishes the rules so that when someone breaks them…
You immediately know they’re doomed.
Thankfully, this is not the case for digital humanities projects. In fact, one of the main ideas I took away from last semester’s class was that everything is worth questioning, including the rules themselves, and the conventional wisdom that goes with them. Breaking a rule may cause a few headaches – in our case having to put together a proposal relatively quickly when we would have already had one had we gone down the traditional path – but it’s still completely workable. And things also balance out down the line- for example, later on, we won’t need to compile a dataset for our project since we already have one.
It seems like this is the way our project will continue, diverging from the prescribed path in places, sometimes requiring more work, sometimes giving us more breathing room. From the technical side, this is already something I’m thinking about as I plan my work. Because we’re still figuring out the exact form of our output, any digital tools I start setting up at this stage would need to be flexible enough to support a range of final products, until we pare things down and decide the details of our project more firmly. Which means right now my best bet is preliminary research for the basic structure and hosting of the site. Thankfully, I already had a lead on this. I’ve been wanting to look into Jekyll since I first learned about it in a discussion of minimal computing in my first class in this program. And this is finally my chance. A data vis project that doesn’t require a lot of social networking seems a perfect use case for creating a static webpage that can stand on its own. This is way easier to preserve in the long term, and also allows us to retain control over our project – we can keep our own copies of it so as to not be at the mercy of whether some faraway server shuts down.
Also, it’s called Jekyll, and we’re doing a project about horror, so that’s fun!
Getting familiar with some options for a basic framework for this project by looking into tools like Jekyll and GitHub Pages is a technical step I can take now. But beyond that, anything more specific will have to wait. Maybe as our ideas about the exact nature of our data visualization solidify, I can take a look at what data visualization tools exist for things like graph theory and network analysis, since that looks like the direction things may be headed, based on our discussion around seeing how themes in the games link to each other.
So hey, we aren’t doomed or cursed or anything like that, we just… entered the haunted house through the back door, I guess! Doesn’t mean we can’t still explore it just as well as if we’d come the conventional way. The flexibility of being able to break the rules to some extent and not be punished for it is something I really appreciate about DH.
Of course, when doing something official like filling out grant proposals… well, if you break the rules there, you really are doomed. Good luck! 🙂