Segregation in so called diversity

When I was assigned this blog post: “How do we resist, in the sense of resisting the narratives you are working with, the tools you have been presented with, the challenges and biases you have faced as a student researcher/digital scholar, and even your own research?” Memories of everyone telling me I couldn’t do something because I was a girl or an undergraduate researcher flooded into my head all at once. I hoped to take the weekend to clear my head and find an answer because I didn’t think that just researching military subjects as a woman was an acceptable answer. Just existing can be a form of resistance in some cases, especially more extreme ones, but I don’t consider that my case. I thought about it over the weekend, especially as I went to two events with very different audiences: The Civil War Institute Conference, with a demographic of mainly older, white, straight, men; and D.C. Pride, a celebration of the LGBTQA+ community, with more diversity of races, ages, sexualities, etc. than I think I’ve ever seen. While I went to Pride and talked to people about what I was doing with research, I felt guilty. Why was I not covering these people? My people.

It’s been a constant debate in my mind: should I be doing something else? My project is literally following the cream of the crop of America, young white men with the privilege that got them into West Point in the first place. Many are from prestigious or rich families, others had fathers who had political or upper-echelon military connections. Am I resisting by merely being a woman doing this research? There are no women, no people of color, very little diversity in nationality or religion, and per many historians, LGBTQA+ did not exist until the sexual revolution in the 20th century. Am I continuing the Great White Man tradition of history?

Especially among higher up academics that I have talked with, there seems to be a discouragement from women doing any other history besides gender history, or more specifically women’s history. Especially in war. Because of the “new cultural history” there has been a focus on diverse scholars covering diverse topics, but only the topics that fit them. Women should focus on women’s history, black people should work on black history, and so on. Like the Civil War for example, women focus on Southern women, Clara Barton, mourning dresses, etc. That’s not diversity, that is segregation.

“Only a small number of female historians – notably Barbara Tuchman – have specialised in military subjects, while feminist academics have highlighted specific contributions made by women.” -Katie Adie (https://www.theguardian.com/commentisfree/2013/sep/23/first-world-war-women-remember-them)

Feminism is equality. Feminism in academia does not mean shoving women into a separate space in which they can just do women’s history. Feminism in academia means letting women go into whatever subfield of history they desire and integrating them with the existing community. Resistance in history can mean studying rights movements and telling untold narratives but it can also mean changing the community of history. Existence is not enough; normalization is the goal. When a fifteen-year-old girl isn’t mocked for going into military history, or a sophomore college student isn’t told that she should go into gender studies simply because it’s what women in history do, that’s when we’ll know.

“The gender of the scholar is beside the point and limiting our reading of a particular approach to one set of voices can only serve to diminish debate and, ultimately understanding. So dividing facets of the history of the war into men’s and women’s history is a pointless exercise.” – Jessica Meyer (https://armsandthemedicalman.wordpress.com/2014/09/16/on-being-a-woman-and-a-war-historian/)

Progress comes from the inside, the narrative will change when the community changes, and we have a long way to go.

-Julia

Why Resistance Matters

In their chapter, “Pedagogies of Race: Digital Humanities in the Age of Ferguson,” Amy Earheart and Toniesha Taylor discuss their project, White Violence, Black Resistance, which blends activism and digital scholarship into a cohesive entity. As I was reading the chapter, I recognized a number of similarities between Earheart and Taylor’s work and my own. One of the goals for my project has been to highlight the narratives of people who have been left out of mainstream campus histories–this is also a goal of What We Did Here–simultaneously, White Violence, Black Resistance is an attempt to “disrupt erasure.” Both projects, then, are projects of resistance. In their text, Earheart and Taylor write, “A focus on points of resistance is central to student learning. Just as we as faculty collaborators interrogate moments of resistance in our partnership, we encourage students to understand how points of resistance in their own work, in the historical narrative, or the technical interface reveal crucial moments of engagement and insight. Instead of following a lockstep approach to a text, we ask the students to creatively interrogate the text within a broader context.” In my opinion and experience, resistance is marked by three qualifiers: it is driven by need, strengthened by collaboration, and requires active participation. As Earheart and Taylor imply, this resistance extends past projects, and it opens possibilities–a phenomenon we have come into contact with a number of our responsibilities as senior fellows.

As alluded to earlier, I thought there were a number of similarities between White Violence, Black Resistance and the two projects I have been working on–This is Why We Fight, and What We Did Here. The projects are driven by a need to recover narratives that have historically been excluded, they are strengthened and made possible by a number of partnerships, (my project and What We Did Here would not have been possible without the support of Musselman Library and the Digital Scholarship Working group, and rely on group contribution, while White Violence, Black Resistance relies on Earheart and Taylor’s teamwork and the incorporation of their students), and they come to fruition because people put forth the action and effort they need to be completed.

Taylor and Earheart’s chapter also talks about lowering barriers of entry so that the greatest number of people possible can connect and involve themselves with their project. This is also an act of resistance as it disrupts a normal hierarchy of involvement within university and digital systems. As digital fellows, we are attempting to do the same thing with our OER. There is a need for making digital tools and projects more accessible to a greater number and range of people–this is something we discussed when we defined openness and accessibility as being one of our cohort’s DH values this summer. Our OER is a collaborative effort-we are all creating it together, and it will be reviewed by a number of people. We also have to make an active effort beyond simply making the project in thinking critically about our audience and what we hope that they understand from our lesson. By creating a source that is open to a general audience, we are resisting elitist and exclusive narratives.

In the digital humanities and other learning pursuits, resistance becomes an opportunity for education and enrichment because it requires that the learners define their needs, utilize collaboration, and actively engage with whatever situation they are placed in. Though resistance may be challenging, it is productive and influential, and I am excited to see it being incorporated into dssf17.

Digital Tool Review: SoundciteJS

SoundciteJS is a tool used to embed audio clips into a text. Powered by Knightlab, it runs similarly to the other JS sites. It is free, relatively easy to use, and open source. I have talked about this tool a few times before, but it deserves to be talked about again.

SoundciteJS is not an audio editing tool. It simply makes a clip that can play over text. The end result looks like this:

 

The audio file can be played if the play button in the highlighted text is pressed. Files can be made out of any mp3 or ogg file, can be made to be whatever length is required, and can be made to repeat.

To create a file, users need only to find an audio URL, load it to the site, and set the time codes for the clip. Now, shorter clips are better for this tool. It can be used to augment a piece of text, to create environment, to give auditory examples. Using it for pages upon pages of text as an actual audio file goes against what the tool was created for. It is not meant to edit audio, that must be done before the file even reaches the SoundciteJS page. A usable mp3 or ogg file must be available with a URL in order for the tool to work. If the file cannot load, the tool won’t work. SoundciteJS, like other JS sites, works better on some browsers than others. Firefox is recommended over ones like Chrome, as the tool will operate more smoothly.

The tool itself is not that hard to use. Knowledge of HTML is handy, but the site does a good job of explaining how to embed the generated code. The link van be made without in depth technical knowledge. However, if a user ever wants to save a file, they must make a SoundCloud account and register with that, or they risk the chance of losing their links. As far as privacy goes, they certainly exist. While users don’t have to register with an account, the openness of this tool and the other JS sites do have their privacy issues. As far as uses go, SoundciteJS  can create atmosphere in a piece of writing by stimulating more of the reader’s senses. It is not necessarily useful in answering research questions, but it was not necessarily designed to. The page for making a clip is simple and serves only one purpose- generate an embedable code to make pieces of text more interesting. There’s not much to it, but that makes it more user friendly.

I myself probably won’t use this tool. I had considered it to help create atmosphere in my audio tour, but the need for readers to click on the text to prompt the audio would distract from the narrative interpretation. I would be better off using an audio editor and incorporating what I would put in Soundcite into my larger audio file. All in all, this is a useful tool that can bring interest and life to digital projects- provided users know what they are doing.

Queer OS?

Wow. Most of the content of this article went right over my head. I took a 300 level feminist theory course which had difficult readings, but this is especially tough. To truly understand this article I think it needs to be read very slowly, annotated, and read over again. I would really like to hear the authors speak about this. I would hope it would be easier to understand. I understand that Barnett, et al. want to break down different hierarchies, but they are writing in such a way that only certain people with great educations can understand. I think I would really benefit from the Cliff notes version of this. I want to be able to get on board with the idea, but I can’t if I don’t understand it.

StoryMapJS, a Review

What are the key features of this digital tool? How is this digital tool distinct from other ones similar to it?
As RC mentioned in our Mapping with Esri StoryMaps and StoryMapJS session, StorymapJS is PowerPoint like which helps to make the tool user friendly. A user does not need to know HTML or CMS to use the tool, but a basic coding understanding is required to embed other maps into it. Because maps can be embedded, the user can choose what type of map to annotate. For example one user may use a map from the 15th century while another may use a current map of the United States. Images and pictures can also be embedded into StoryMap making them very easy to annotate. On the down side, other aspects of StoryMap are not easily customizable and a Google log-in is required.
Other similar interactive mapping tools include: Esri StoryMaps, Fabula Maps, and Google Tour Builder. There are also some data visualization tools with maps which include Carto DB, ArcGIS and QGIS. In our session we worked with Esri StoryMaps as well. The tool has a default map that is not customizable and there is a 99 map point limit. Storymap JS on the other hand can have an unlimated number of points plotted on the map. Esri StoryMaps is a paid tool, making it more stable, but less accessible.

What kinds of research questions might this digital tool help you answer?
There are several different research questions that this digital tool can help to answer. By creating points on a map someone’s life, journey, trip, ect. can be shown. Paintings, photographs, lithographs, ect. can be annotated to help understand the imagery and symbols.

Is the digital tool free, or is there a cost to use it?
StoryMapJS is free but a Google log-in is required. There is no monetary cost, but because a Google log-in is required StoryMaps can collect the user’s data. I personally see issue with this, but some people do not have a problem with it.
What kinds of data/input does the tool require?
-Text
-Variety of images, audio, videos.
-Location
-TimelineJS and other similar tools can be emended.

Could you use this digital tool for your project? Why or why not?
Yes. I am planning on using this tool to annotate the lithograph on the cover of the sheet music I am analyzing. I believe StoryMapsJS is a great tool and I am really excited to start working with it more.

Thinking About the Puzzle Pieces / DHSI Day 2

So music bingo is apparently a thing in Canada. Who knew?

But before that, today was an introduction to DHSI in the morning and a brief overview of everything planned. There’s a lot of social stuff going on, and the schedule is pretty much packed with classes. There are also unconference sessions being decided upon and general meetups being finalized, so no shortage of ways to connect with people. I’m pretty sure I’ll be ready to curl up into a little introverted ball at the end of this week.

Classes officially started this morning, with Angel David Nieves and Janet Simons from Hamilton College‘s Digital Humanities Initiative leading us for the rest of the week.  They started with an introduction to Hamilton College and the history of the DHi, but moved quickly into thinking about what makes DH, DH, and what makes DH, DH, at our institutions. There’s a lot of focus on the ideas of process and project, and what makes up the core components of DH. Process is hard to assess and quantify, but it’s what DH ultimately is, with the idea that your processes result in some sort of project as an outcome. But often there is little consideration as to the process, just the idea of getting to the project. Collaboration fits in there as well, and is another reason why DH is important, as it forces people working on DH to consider each other as equals in the research process. DH can’t be simply a service model, it collapses hierarchies and gets each member of a project team to contribute to the work in their own way. I have been fortunate to experience this during my time working with the Jack Peirs project (go #teampeirs) led by Ian Isherwood at Gettysburg.

We also talked about campus and institutional culture when doing DH work; DH work is experimental and risky, but institutions are often risk-averse and pass that mentality to those in it. Leadership is touted by institutions of higher education as a value they wish to instill in their students, yet those who are trying to lead change to support new initiatives run into roadblocks. What I hope is communicated is that those of us who are trying to lead the change are doing our best to be good stewards of the resources our institutions provide to us. We know budgets aren’t growing and there are fewer resources to go around. None of us want to fail (even if failure is simply part of the DH process) and let people down. That fear is huge, and I feel it.  But I think we also know that until we try new things, we won’t learn from doing the same things over and over again, and allowing for missteps and mistakes and even failure along the way is good for us as an institution. And while leading through failure really isn’t a good model, sometimes we may be behind the curve a bit until we can find a way to break through. Thankfully, we have supportive people at Gettysburg, and while we tend conservative, there’s been enthusiasm towards getting our student program up and running, and I’m hoping to find ways to leverage that into a more intentional campus-wide model that is more dispersed and equitable among all the units that support DH on campus.

In the afternoon, we spoke as teams about the state of DH on our campuses, and while Gettysburg lacks any centralized DH program or structure, we have a lot of the right pieces in place. In the nearly 2 years since #ILiADS15, it’s been a fascinating ride to see how digital scholarship has been evolving with our loose band of librarians, educational technologists, and faculty working on projects. While institutionally we still exist in a mostly ad hoc model in how we approach support for faculty research, classroom assignments, and student projects, things are changing for the better. We have a digital scholarship committee in the library that supports DH work and runs the DSSF program. The Johnson Center for Creative Teaching and Learning has sponsored new grants that allow faculty to update assignments, using our students in the DSSF program to support assignment redesign and incorporate digital tools and DH methods. We have a growing student summer fellowship program that has support from the library, Educational Technology, and the Provost. Educational Technology launched a partner program focusing on technology this summer. We seem to be doing a lot of stuff right. The pieces are there, but there’s no unifying theme right now. It’s like having a puzzle without the box to look at and having a lot of other puzzle pieces mixed in. Right now it’s trying to see the big picture and pull out the pieces that don’t fit.

So the big question, so far, is “Why?,” as in, “Why are we doing this at Gettysburg? Why DH?” And I’m not sure how I can answer that fully quite yet, other than what the answer has been so far, that we are trying to provide students with creative undergraduate research opportunities and we want to give students tools to be digitally literate. And by training students, we can show faculty that students are excited to learn these new things, and hopefully pass that enthusiasm along. DH work is transformational, not only in how students and faculty conduct and present their research, but it also transforms how librarians become part of the research process.

But yeah, about that music bingo …

Always Know Where Your Towel Is / DHSI Day 1

9 hours riding in planes, and 3 time zones away from Gettysburg, I am in Victoria, British Columbia, for week 2 of the Digital Humanities Summer Institute.

Cadboro Bay, Victoria, British Columbia
Cadboro Bay, Victoria, British Columbia

After getting to the University of Victoria campus, it took the rest of the day and a better part of the next to get acclimated; travelling is always difficult and this trip it was even more difficult to get adjusted, since I couldn’t rely on my mobile as a crutch to get around ($10 a day for international roaming, when the border is 20 miles away, no thanks). It’s amazing how we get attached to the Maps on our phones to get us to where we need to go. Trying to find open wifi hotspots is something of a challenge as well. Thankfully, Canadians and fellow DHSI-ers are friendly people, and there’s no shortage of advice and directions if you ask.

I will say that I immediately regretted not following the advice of Douglas Adams, as I didn’t bring my towel; thin and small dorm towels are enough of a reason to try to cram one more thing into your luggage, in this case, a nice soft towel from home.

Mystic Vale, University of Victoria
Mystic Vale, University of Victoria

Day 1 was a half day, spent in a small workshop (re)learning XPath, but much of the day was spent wandering around the campus and learning the lay of the land. Deer are everywhere, but bunnies are not quite as prevalent as I was led to believe. The campus and surrounding area are quite beautiful, with a large hill going down to town; in all, it reminds me of the DH experience that ultimately led me to here, the 2015 ILiADS institute.

Looking forward to getting started with the Models for DH at Liberal Arts Colleges course this week!

Resistance is futile??? or fruitful??

According to Google, the definition of the word resistance means the refusal to accept or comply with something; the attempt to prevent something by action or argument. Applying the definitions that Google has provided to digital scholarship, I believe that digital scholarship only applies to the first part of the definition. From everything I have learned throughout the year, digital scholarship seeks to not accept or comply with the standards of tradition. Rather, we digital humanists seek to break and “resist” the traditional narrative. However, digital scholarship does not completely fit the second half of the definition. Digital Humanities does not prevent arguments or actions but rather, welcome a diverse group of voices and narrative.

The reading “Pedagogies of Race: Digital Humanities in the Face of Ferguson” directly applies the idea of resistance to the field of Digital Humanities. The writers of this article resist a number of things throughout the text. The first part of the article sought to resist the current digital project model that required a very high degree of expertise and knowledge. They acknowledge the fact the DigitaHumanitieses can be very exclusive and even at times a privilege. To break the mold they decided to “select technologies with low entry points to encourage a range of participation”. The article also discusses using digital humanities to break down traditional narratives and topics. White Violence, Black Resistance is a collaborative project that resists the traditional historical narrative and strives to “digitize a broad set of primary documents related to interactions of race and power” and recover long forgotten histories of black towns and spaces in Texas and the University.The project definitely puts the idea of resistance into practice.

The article also challenges the readers to “encourage students to understand how points of resistance in their own work, in the historical narrative, or the technical interface reveal crucial moments of engagement and insight”. This quote does apply to the work we digital humanities do, but in a much larger context, this applies to all academic scholarship. As scholars, we are taught to interrogate and reflect on what we are learning. Being able to resist and challenge our own work, historical narratives, and technical interface makes us better scholars.

Throughout the entirety of the Digital Scholarship program at Gettysburg College, I think we have applied the idea of “resistance” to our own individual and collaborative projects. But I am not sure if the word “resistance”  is the correct word to use to describe what we have done here. Rather, I would like to use the word “challenge”. I think we have challenged our ideas of scholarship and even at times digital humanities, through open discussion and collaboration.  We have also challenged the traditional historic narratives through our individual research and projects.

Through my own work and experience, I have definitely been challenged and challenged others. By collaborating with multiple professors and students, I hope I have been able to challenge their view of digital scholarship and digital tools. My project this summer seeks to challenge and break the traditional historic narrative. I am working with a set of photographs of Native students from Carlisle Indian School. I specifically want to challenge the traditional narrative of the Native American History and the legacy of the Carlisle Indian School. Researching and planning this project has definitely had its challenges. My biggest concern is how to accurately and respectfully present these photographs and people. I definitely have my own set of biases and that I need to address and investigate.  But I hope to continue resisting and challenging my own work and scholarship.

Best Wishes,

Keira

QueerOS: Another platform, for… what, exactly?

So, this reading about QueerOS by Fiona Barnett, Zach Blas, Micha Cardenas, Jacob Garboury, Jessica Johnson, and Margaret Rhee is dense, weird, and kind of unapproachable. The purpose of the article is lost on me, hidden beneath jargon that requires a WGS and a computer science degree to understand (neither of which I have). If I’m missing the point of the article entirely when writing about this, please do not hesitate to engage with me and explain it to me, because I would love love love to learn more.

I see many issues within the queer community (ahem, biphobia?), and I take issue with the radicalization of the queer community that slips through the cracks of the few parts I could truly understand, and those are things I immediately see as far more pressing concerns than making the QueerOS.  That’s an issue for a different blog post. However, in the meantime, we’ll go back to reacting to the article.

The joke may be lost on me if it is one, but I find it unusual for a scholarly article to crack something like this:

“By offering its flesh to the OS, the user becomes one/multiple/nothing and binds itself in a contract with the OS.The user’s offer of flesh is irrevocable, nonexclusive, worldwide, perpetual, royalty-free, and sublicensable.”

For a group that advocates for consent and states that consent can be revoked, I find this flesh language to be borderline hypocritical. Perhaps this needs to be fleshed out.

The rest of it is pretty straightforward, mentioning more about trans inclusion and how important it is to include POC as well, which I’m 100% on board for. However, I still end the article thinking: Why? What issues do you take with the existing operating systems? I understand that it was likely designed by a cishet white male, but at this point I think there’s higher priorities that need to be discussed and fixed before you go digging more into radical operating systems that won’t necessarily fix anything and won’t necessarily get you taken seriously, especially if there’s no real benefit to be gained from it and he authors of the article know it:

“We acknowledge that some of these features do not exist as part of present-day operating systems or terms of service. Nonetheless these concepts are repurposed here with performative and disruptive intent.”

I’m always fond of a little chaos and disruption, but the message doesn’t get translated well when others are worried about the chaos. I get that “neoliberals are the devil” mindset is hard to shake, but chaos isn’t going to bring everyone over to your side, and instead will alienate the people you’re trying to translate the message to.

I’m fine with a QueerOS if someone wants to make it. I’m not uncomfortable, and I’ll embrace it if it’s understandable, usable, and not put up too high in the ivory tower for even me to approach. I’m glad that there’s more queer and POC representation in DH, but this didn’t help me understand DH better. It just confused me more, actually. If you want to be inclusive, don’t bury your inclusiveness under jargon and hypocrisy.

This rant turned out longer than 100 words. Oops.

-Britt

I’m not tired of traditionally masculine spaces at all

So I know as a Senior Fellow I don’t have to do a micropost but this needs to be said.

Let me tell you something about my project and what I do: IT’S HARD.

What I do is hard. I’m going into a field that is already greatly skeptical and highly critical of any new members. I make tons of jokes about it: like if I had a dollar for everytime someone says “that’s not lady-like” I could pay my college tuition.  Funny, right? You know what’s not funny? Literally being laughed out of a military history class in high school because you’re a woman. Dreading the response of someone when they ask, “what do you want to do?”. Being told what you’re doing is worthless and won’t get you into grad school. Maybe you should go into women’s history because you’re a woman and you obviously you can’t do any other history outside your gender.

Throughout being laughed at, ignored, interrupted, disregarded, and criticized I have tried to keep an upper hand and keep my chin up. My life has literally become my cadets because if I were any less passionate or driven I would’ve given up. I would’ve given up the first week of my military history class in high school and sometimes I wish I did, it would’ve been so much easier.

I devote so much time to records because if I say I don’t know something I am automatically brushed off as a silly girl who doesn’t know what she’s doing. Sometimes I talk over people because so many times so often if I don’t talk over people I don’t get heard at all. I take on an enormous workload in short time periods because if I don’t it will be perceived that I’m not dedicated or I don’t have what it takes. And I can’t let anything get to me or else I am perceived as weak and I don’t belong for a reason.

I know I don’t belong already. It’s abundantly clear as I can name less than ten influential women warriors in history and even fewer women military historians. It’s hard to know you’re not accepted in your field and even harder when people don’t realize how hard it will be for me to get into the field much less change it.  My mantra is “You have to work twice as hard to get even half as far as they are”. If you think that’s extreme, I’d love to see you go through half as many records as I have, contact half as many references and have them laugh in your face, or devote half as much time as I do to my site and my cadets. Don’t tell me what I can or can’t do unless you’ve been in my heels for a day.

It is hard. It is overwhelming. It is exhausting. It is what I do every day and I’m expected to suck it up and take it like a man, which is exactly what I’ll do after I vent a bit with this post.

-Julia

css.php