Exit, Pursued by a Bear

There’s bound to be a ghost at the back of your closet no matter where you live.

Greetings from a place that isn’t Gettysburg again! The 2017 cohort has given the 2016 cohort a much deserved break from our nonsense and taken it to Ursinus College for the PCLA Digital Learning Conference! The college was kind enough to stash us in a couple of houses for the two nights we’re here, so it’s me, Emma, and Christina vs. the adults we brought along in the other house. Mind you this place might be a little old, and with all old houses they tend to make weird noises. Emma and Christina are a bit spooked, but frankly with what Ursinus hooked me up with, weird noises don’t freak me out and I’ve had WAY creepier stuff happen. If a ghost comes, let them come at me because you bet I’ll fight them and probably win. Ghosts aren’t high on my list of fears… otherwise that would make going to Gettysburg a little awkward.

Shoutout to snapchat for my ability to put geofilters on things and have any inkling of where we are besides outside of Philadelphia.

Besides, I’m sleeping in a former dining room with a pretty dope bay window, and the lighting makes me happy because I, the second most extra person in the overall cohort, can do my makeup and take cute selfies. Priorities, right?

You bet your ass I totally took a selfie just to prove it.

Obviously we’re not here to only appreciate the accommodations, but I’m excited to meet more DH scholars and learn more about DH overall. It’ll be fun to hear different perspectives on definitions of DH, and also hear more about other digital tools I might be able to use to put my project together. Maybe it’ll help me like Scalar more! We’ll find out!

-Britt

P.S. peep that shakespeare quote because… Ursinus. Bear? HA!

Digital Project Review- Maps as Art

What is the link to the project?
http://daniellasnyder.sites.gettysburg.edu/maps_as_art/

Who created the project? Why did they create the project?
Daniella Snyder. She was a Mellon Fellow and created it to showcase her research.

Who is the audience for the project?
-Art Historians
-Historians
-Map Historians
-Special Collections
-Future DSSF Fellows
-Future Kolbe Fellows
-Professors
-Graduate Students
-Map Collections
-The Gettysburg College Community

What research question does the project appear to be asking? Is there a central thesis?
Daniella was looking to understand and analyze Willem Blaeu’s “Noca Totius Terrarum Geogrpahica ac Hydrographica Tabula” map A 1643 print, after a 1606 original. Her main question was “how can maps be pieces of art work?”.

How easy is the project to navigate and use? Is there an inviting home or front page?
The project is very easy to navigate. There is a navigation bar, a home page, and all of her scans are hyperlinked. If someone did not have much technological knowledge they would be able to navigate through this website. She even explains how to explore the website. I think the home page is very inviting. I wish the navigation bar was centered differently, but other than that, it is great!

Is the writing clear, succinct, and precise, or does it read like a traditional scholarly paper?
The writing is extremely strong. As Daniella analyzes the different aspects of the map, it becomes more scholarly because it uses specific art terms, but I think for her audience it is okay. She is very detailed but does not write too much. Each page and section of the Storymap is manageable.

Is there an About page, or other information page? Is there any technical information about the creation of the project?
There is an about page on the website. It explains who Daniella is, what a Mellon Grant is, some of the research she did and the people that assisted her during her work. She does discuss the digital tools that she used.

What kinds of digital assets are used? Is metadata available?
Daniella used scans of her map on her website. I did not find any metadata about the map.

What kinds of digital tools are used for the project? Why were they chosen?
Daniella used WordPress and StoryMapsJS. She does not have a section on her website explaining why she used each tool. I believe she used StoryMapsJS because it is very easy to annotate images.

What can you learn from this that you couldn’t from a traditional research paper?
This project allows users to interact with, visualize and understand  the map and the parallel images that the border is based on. This would be very hard to do with a paper especially if there were no images in the paper. I think this project is best as a DH project.

I really love this project and really enjoyed watching her create it. It has helped to inspire my project for this year. I hope to see more projects like this one!

Thank You!

I have spent the past week reading through files upon files for research. This can be tiring, but it would be even harder if not for the cataloging efforts of those who work at archives. Anything I find has already been documented and categorized by an archivist, which makes my job of reading and interpreting the material much easier. Since the collections have already been catalogued, I can find material through finding aids and the like, searching for words and ideas that pertain to my research. Thanks to the people at Special Collections, the Musselman Library, and Adams County Historical Society, my work is made possible. The trove of information open to me because of the work of others is invaluable. So, I will take a quick break from researching to say thank you all. Then I will go back to the finding aids to dig up more information so graciously catalogued for all to use.

Emma Lewis

Digital Project Review: What Jane Saw

In all digital work, user exerience must be kept in mind. If a DH project cannot be understood or navigated by a user, then the DH project has failed. A good way to understand this as a designer of a digital project is to look through other examples to see what others have done with their user experience. Through the DSSF17 website, other projects can be seen and analyzed to do exactly that. For this post, I examined  “What Jane Saw” from the University of Texas at Austin College of Liberal Arts.

Created through the Department of English, the main researcher was Professor Janine Barchas. She is the only person to have been linked, although credit is given to others for coding and research, and the project itself is supported by the Liberal Arts Instructional Technology Services.

The main page is relatively simple in design, and from the language it appears to be for a more general audience than a closed off academic one. The main page is not cluttered or overwhelming, it invites people to come and investigate the site. The purpose of the site is to compare two art exhibitions that took place in the same space over the span of 17 years. It is framed through Jane Austen, who went to both exhibitions. Users are, in essence, seeing what Jane saw when the exhibition space was still standing. Jane is not called upon often. The about page for each exhibition devotes one section to Austen’s experience of the space, and  in the digital exhibition pages she all but disappears. However, the aim of the site is to show two different points in history, and at that it succeeds.

The site appears to be a custom build at first glance, which is confirmed when users go to the “About WJS” page. ( 1796 and 1813 each get their own page) While it makes sense to give each exhibition its own page, the fact that the information about the site construction and content can only be accessed through other pages is disorienting. That is one aspect of user experience which could be improved. The build of the site is not disclosed on any page. A few coders are given credit, but not much else is given as far as site information. The page source can be viewed, but that is not accessible to all users.

That said, the project itself is very interesting. I chose to analyze this due in part to its home page. The page is simple, not overloading new visitors with information. This urges users to look further, to click over an exhibition and discover what was there in 1796 or 1813. Once a user clicks on an exhibition, they are taken to a digital exhibition space.  Paintings can be clicked on to produce a clearer image and metadata. Different walls and rooms can be looked at by clicking to the left or right. A scan of the original catalogue can also be accessed to navigate the space. This, unlike a traditional research paper, puts users inside of this lost space and allows them to experience the exhibition. It is not exactly as Jane Austen would have seen it, but it is as close as we can get.

The site does a wonderful job of transporting users to this space. In this space, however, some things can be confusing. The catalogue is my biggest issue. Unlike the paintings, which keep users in the same digital space, the catalogue and each page it contains is put on a separate page on the site. In order to get back to the rooms for exhibition, users must either click back through the pages they just read or choose a link to a painting to be taken to it in the digital room. If the painting is in another room, users can get disoriented. There is a map of the floor plan to help in this case, but it is still a shock and undercuts the ease of use the site had.

Overall, this site works well to engage users in its material, even if there is a learning curve to using it.

Emma Lewis

A Dead Poets Society Moment

One thing that struck me about this article was that it addressed my confusion about my frustration about the field that I’ve been feeling lately. After being immersed in DH and the DH community for about a year, I’ve noticed something: we never stop asking what DH is. We opened last summer with the question “what is DH?” and we opened the first conference of the summer, a year later, the PALA workshop opened with asking “what is DH?”. As DSSFs we fully expect to be immersed in the field so questions of asking what the field is, in the beginning, is expected. However, these articles and discussions are not easy to understand for beginners and use jargon like “pedagogy”, “Community of practice”, and even “Digital Humanities” itself.  If you’re being introduced to DH and have no idea what Digital Humanities is, these articles and discussions will confuse you. The only conclusion I can draw from this is that discussions about “what is DH?” is for audiences who are familiar with DH, not people just being introduced.

So why do we always ask what DH is? Haven’t we come to a pretty solid conclusion as a community right now? If DH prides itself on openness and accessibility, why are discussions and papers that discuss the concepts and definitions of the field littered with jargon and theory, assuming that their audience are never beginners in DH? I get it. Once you’ve been so immersed in a field you forget what it’s like to be a beginner, for everything to be new, strange, and confusing.

There is elitism in DH. We have built ourselves an ivory tower. Say what you want about History and History’s high ivory tower of academia but there is a low barrier of entry into the history community because anyone could pick up a book, go to a historic site, see a sign, hear from their family, etc. and be touched by history and pursue it. There are millions of non-academic historians and millions of academic historians as well. There is elitism in history but in a different way. History is like a backdoor speakeasy, where you can get into the main establishment easily, but to get into the academic area, you need to know a password or know someone to get in. Digital Humanities is more like the Ravenclaw common room, where you must answer a question to get in at all and much like in the Harry Potter books, there will be frustrated students who do not understand that will be left outside.

In my experience with teaching digital tools to students who weren’t necessarily in DH, I wouldn’t just hand them Lisa Spiro and say “Welcome to DH, now tell me: what is DH?”. That’s not what makes Digital Humanities. While readings do help further understand the field, I don’t feel they’re as constructive to beginners. I feel like I’ve learned the most about the field by doing my own projects, looking at and teaching tools, interacting with others projects and talking with other scholars.

While I agree with the author on many things, I disagree on one thing: I do believe that Digital Humanities can have a “Dead Poets Society moment”.

“In many ways, I think the way we often frame DH tries a bit too hard to achieve a Dead Poets Society moment: “your other teachers taught you literature with close reading and literary criticism, but in my class we’re going to disrupt that stale paradigm using computers. Now rip up your books and pull out your laptop!” But those attempts fall flat, for all the reasons I have tried to articulate thus far.”

-Ryan Cordell, “How Not to Teach Digital Humanities”

I don’t know if you’ve seen Dead Poets Society but ripping pages out of the book is not the purpose of that scene.

“We don’t read and write poetry because it’s cute. We read and write poetry because we are members of the human race. And the human race is filled with passion. Medicine, law, business, engineering, these are all noble pursuits, and necessary to sustain life. But poetry, beauty, romance, love, these are what we stay alive for. To quote from Whitman: “O me, o life of the questions of these recurring, of the endless trains of the faithless, of cities filled with the foolish. What good amid these, o me, o life? Answer: that you are here. That life exists, and identity. That the powerful play goes on, and you may contribute a verse. That the powerful play goes on and you may contribute a verse. . .What will your verse be?”

-Robin Williams, “Dead Poets Society”

The human race is still filled with passion. Even with all the assumptions that technology is making us lifeless and brain-dead, we are undeniably filled with passion. Just like the author in his own course makes a comparison between Digital Humanities and Traditional Humanities by recalling that the Gutenberg Press was once newfangled technology and its opposition by traditional fields at the time; humanity has always found a way to express themselves and has adapted to new technology. The reason why that scene is so powerful is because everyone can relate as members of the human race that feel and love and dream. Instead repeatedly asking “What is DH?” to beginners who don’t even know what the acronym ‘DH’ is, maybe we should finally give an answer and that answer could be as simple as “It exists. It is an expression of life and identity through a new medium.”. Instead of focusing the field on that one question, we should focus on engagement and contribution because that powerful play goes on, life goes on, and we may contribute a verse. Asking “What is DH?” for the 1000000000th time might sustain the life of the field, but digital projects and engagement are what makes the field worthwhile.

-Julia

 

StoryMapJS: Cool Beans

The Knightlab program is cranking out digital tools that I find to be pretty user friendly and easily adaptable to different site templates like WordPress and Scalar (I’m sure you can probably put it in Omeka, but why don’t we cross that bridge later?), and honestly I’m here for it. I love free tools that are designed to be easy to use. StoryMapJS is no different here, and I’m excited to potentially use it for my project.

StoryMapJS is good for mapping out points on a world map to tell a story and document the path, but what sets it up for my own use is its ability to import images so they can be notated as well. This is perfect for my own uses, honestly (given how I’m using art…).

When you go to open up StoryMapJS to make one, the tool immediately asks for your Google account. People do take issue with this for privacy reasons- however, I really don’t and will be proceeding under the impression you don’t either.

The tool opens up with a straightforward, black and white world map. On the map feature, you can zoom in pretty close to get as accurate of a location as possible. However, this is a standard Mercator map, which could affect some more Eastern versions of maps if that’s your issue (maps really are biased, mainly because spheres don’t flatten very well. Different post.).

You can toggle a setting on the map that lets you connect each point on the map and slide, making a path. Turning this off might be easier for other images, but if you’re following someone’s journey across the world, that is a useful tool to have.

However, I take issue with the points themselves, mainly the aesthetic. They’re big, chunky, and put logos on your map that don’t really work depending on what media you use for your notations. The colors can’t change, and neither will the size. They may or may not match the aesthetic a user might be trying to work with, and looks weird on a piece of art.

Uploading images to notate can be a bit tricky too, mainly because you want a giant image that can take up space on your computer, and then you have to use another tool to break it into smaller pieces so the map will load faster and not get distorted. It takes time to do that, and you definitely need a high resolution image to upload to make it work. But this can

You can embed pretty much anything into the map point description, which is pretty nice. That description also probably has a pretty high word count tolerance, or that is also unlimited. I have also been told that there’s either a really high cap on the number of points you can put in, or that number is unlimited. Julia’s project, for example, is pretty wordy and has many points on a battle map (which is super impressive).

Overall, it’s a pretty good tool for beginners and people who are getting into DH with uses that need to be simple, pleasing, and accessible with more limited budgets. Nothing wrong with that, and honestly it’s my favorite tool we’ve used. I didn’t run into any technical problems while playing with it, and I call that a good sign.

There’s the Community of Practice / DHSI Day 5

It’s always weird getting used to a new place, especially when you’re anxious and don’t know a lot of people, and the people you do know, know a lot of other people so you feel weird hanging out with them too much, because you know they want to be with people they know.

You know?

Thankfully, the crews from Hamilton and Washington & Lee’s DH programs have been hospitable enough to let me socialize with them, and I’ve been able to connect to some folks from #ILiADS15 as well. This is one of the reasons why I really appreciate the DH community of practice, in a larger sense, because we have a lot of common goals and struggles and successes, and being able to share them with each other has been helpful in figuring out why I’m really here this week. Our Models for DH course has started connecting as well, and the large number of librarians running around has been good for talking shop and thinking about how to approach DH from a library perspective. And outside the scheduled working hours for the day, we can relax together and encourage each other for the next day’s events. I’ve always heard that the DHSI community is one of the best reasons to be here, and I’m really starting to feel that.

Today we spent a lot of time in class going over project management and thinking about best practices for getting a team working together on a project. Nothing was particularly new, but it helps to have it reaffirmed. And while there’s overlap from knowledge I already have, the in-between moments that punctuate a new approach or get me thinking in a new direction are particularly valuable. Effective project management is an important next step for Gettysburg, I think, and will be necessary if we try to develop an institutional model to support DH on campus. It helps break down silos by improving communication and giving clear goals, and making sure work is properly distributed. Janet said something that stuck with me:

Silos develop because we justify our existence by being unique. We have to collectively find a way to be unique together.

This resonates with me, especially as we try to figure out how to be more intentional with supporting DH work on campus; this isn’t something we can do in our own offices or buildings, we need to come together to make things happen on a larger scale. This is why we need to focus on things like process when we talk about DH, as well as collaborative research that reaches across boundaries. The research no longer belongs to one person, but a team.

We also talked about elevator pitches today, with the idea that a pitch for a DH center/project/assignment has to last for one floor of an elevator ride, with time for questions on the rest of the floors. We should be able to articulate what we want to accomplish from this week-long class in that time, with the idea that there’s some sort of hook to get people to ask questions. This is probably the most challenging part of this class so far, because by creating this pitch, the next logical step is to find people to pitch it to. That means going outside my comfort level and trying to sell an idea, and with that all the accompanying anxieties and fears of rejection. I’m not a sales person, so it’s a new world for me to try to get others to buy into my ideas.

What has struck me this week has been that many of the pieces we have talked about when trying to develop a model for DH (user experience, project management, talking about what you are doing, community, defining DH) are core components of the DSSF program as well. That really gives me some confidence that we are teaching the right things. I think the next step for that is to go back and apply them in a new way to the model for DH itself.

At any rate, lots of conceptualization and thinking and writing today. Tomorrow is the last day, which is really weird, because it just seems like I got here.

 

Finally Reaching an Understanding, Which Leads to Gratitude

Accompanying Song

One more for the road

I’m sure the followers of this project noticed my absence from the #dssf17 tag this week, and that is because I wasn’t there to make the jokes and comments that I usually make to spice up the hashtag while Christina tries to make us look good.

The quick explanation? I went home because I needed some time to collect myself. A sudden blow hit my mental and emotional health that took it down to a solid 1% emotional battery remaining. Honestly, I’ve been riding at a solid 55% emotional battery the past few weeks, but I’ve been afraid to acknowledge it and talk about it under the fear that people wouldn’t want to talk to me, Debbie Downer. It’s easier to hide behind funny jokes and smart comments to try and fake it til you make it, or at least help others not feel the same way. I knew I wouldn’t be able to focus on the work properly, not without breaking down into tears at the slightest mention of anything I associated with the person involved in this event.

When I interviewed for this fellowship, I asked what the best part of the fellowship was. Keira was the only fellow at my interview, and she told me cohort. Lauren mentioned at one point that it surprised people when at a panel about their research, someone asked a similar question and all three fellows answered “Cohort.” R.C. came and checked on me at one point and said we all have to rely on each other because campus really, really is dead right now. I hadn’t understood it, honestly. I’m introverted and anxious, if you met me- and if you found me right now it would be honestly worse. Several years of people I care about hurting me has led to me isolating myself more out of fear of bothering people or looking too needy or inconveniencing them. That wasn’t helping me bond with the other people in the cohort as much as it looked with Keira, Julia, and Lauren.

This weekend changed those feelings. If it weren’t for the cohort, there would probably be some crazier stuff that would keep me from posting, and it wouldn’t be good. My cohort helped get me home and hugged me and told me it was going to be okay. My cohort sent me positive messages and checked on me to make sure I made it safely, and that I was feeling better. Christina’s hashtag documentation was helpful in keeping in the loop, and now I’m back in the house with everyone else after several days at home recharing.

Admittedly, it’s going to take a while to get back to where I was once before shit hit the fan. I can’t describe my feelings about what happened with proper words beyond “aaaaaaaaaaaaaaaaaaaaaaaaaa,” but I guess I’m just going to say the jokes on the hashtag probably aren’t going to be back for a bit. Also, this might be a pretty personal post to put here, but digital humanities are about preserving and appreciating the human experience. All of us are human, and humans aren’t immune to emotions and pain. I wish I was, but I figured this was good to document. For this paragraph and the entire post’s verbosity (this pattern seems to come up often), I apologize.

For everything else, I just want to say thank you. It means a lot to me, more than you think it does.

-Britt

It’s Better to Burn Out than to 404 / DHSI Day 4

Three hours of social time tonight, and a lunch spent lamenting the current state of politics in the United States. Things are certainly picking up.

We spent the first part of the day talking about why we’re here for DHSI, thinking about what projects we want to start, what courses we want to design, and what sorts of big picture infrastructure we want to create. This was very helpful to get a high-level overview of where everyone is, and look for places of overlap and how we can provide support for each other. In many ways, this class can function as a support group (and probably a bit of therapy) for all of us, as we are all in different places, yet we have a lot of common themes running through our roles and institutions. In the end, we are all going to have to do what works for us, but it’s good to reaffirm that none of us are where we want to be, and there are things we are all running up against. There’s a conversation about burnout in here as well, and the pressure that people doing DH work feel to constantly ramp up their work and produce results. That’s probably another post. But it’s a real thing, and something we share on varying levels.

For Gettysburg specifically, there are several projects I’d like to see moved to the next phase (or really just get started), but for the most part we are where we need to be for these projects (at the moment, anyway). We’re moving along with assignment redesign with two courses that are changing assignments in a digital direction with support of the Provost, and our involvement in a PCLA grant to support digital liberal arts fellows will give us some structure and accountability for how we are deploying the students that come out of the DSSF program. However, we still struggle with getting faculty interesting in doing DH work in the first place, but that’s not an uncommon problem. In fact, it’s better at this point to have a smaller cohort of faculty who we know and work well with in order to help build up what we are doing.

A theme that continues so far is that Gettysburg really doesn’t need a DH/DS center right now, but we do need some sort of formal structure in place to communicate and coordinate our activities. While good working relationships exist among those of us doing DH work right now, we need to be more intentional in how we plan, design, support, and maintain digital projects, developing a framework for project lifecycles and creating funnels that push projects to particular individuals and teams for consultations. This will help with assessment, evaluation, and preservation as we try to weave DH work into the curriculum and campus culture. Pulling the people together could be done with a working group or similar cohort on campus; while we have an educational technology committee that is faculty-led and campus-wide, it is far more focused on broader concerns about academic technology and not focused on DH work. There would be some overlap on this group, but it could have a different charge and mission. Much of our informal conversations could easily be transferred to a more structured and intentional setting, bringing in the appropriate people to help support it.

Process continues to be an important topic, and DH as process is something I appreciate and want to find ways to continue to develop. Process is harder to evaluate, assess. Its outcomes aren’t nearly as apparent, except for how it affects other outcomes. “Students will create a digital project in order to show mastery of digital humanities skills” is an outcome that still needs a product. While an effective process should result in this outcome, what if the process is more important? Can we assess the process based on the outcome? Angel spoke about finding ways to talk about DH process in a way similar to how scientists publish short papers, and I think this is very exciting for the larger DH community, especially for those of us who really need to understand how others do the work.

Picking a good name for your DH center is important.
Picking a good name for your DH center is important.

On another note, it was great to hear Greg Lord speak about narratives and video games today; despite it being a talk I have heard before, I get something new from it, and new ideas continue to emerge. Unfortunately, the narrative arc of being a bad enough dude to save the president has lost much of its luster since last November, but interrogating classic games to tease out the underlying narratives is a fun exercise in seeing how process and technology can drive story. I’m still interested in getting the DH+VG project off the ground to build a community that can think more critically and practically how games can be worked into DH, as well as trying to figure out how small liberal arts colleges can be more involved in game preservation. Playing DHQuest V3 was fun, and an example of how we can use game engines to drive interactivity.

On to Thursday!

 

Critical Engagement / DHSI Day 3

Second day of Models for DH is done. Thankfully no music bingo was involved.

Today we spent time looking at materials from Hybrid Pedagogy and the MLA Commons’s Digital Pedagogy in the Humanities. I was drawn to the Indie, Open, Free article and, somewhat naturally, the Gaming keyword.  I’ve been continuing to stress to the DSSFs that no tools are neutral and nothing is free; you need to continually critically engage tools to discover their perspective, to see what data they collect, to not accept what they are at face value. Even something awesome, like Reclaim Hosting‘s Domain of One’s Own service, has its challenges when it comes to trying to see how it fits into your larger DH program/initiative/confederation/etc. Even though I love Reclaim, it’s still something we don’t have complete control over. It’s a hosting service, so there’s limits to what can go in the stack, no root access, and we don’t own the servers. So I struggle with the idea of Reclaim being an infrastructure solution as I think more and more about it. Again, don’t get me wrong, it does some things beautifully, and I love one-click installs of Omeka and WordPress. But how do we make the entirety of our corner of Reclaim searchable and something we can archive? I can embrace the concept of ephemerality in DH, but that’s not a typical response.  At any rate, to show process and develop longer-term projects, it may not be the best option. So I understand the logic behind the DHi’s need to develop a self-hosted, cohesive platform for their projects. What that looks like at Gettysburg, I don’t know, because we simply don’t have the capacity to do that right now. Maybe it doesn’t happen.

We also talked about failure and experimentation, and the idea of reframing failure as experimentation in order to take some of the negative stigma out of the reality that things don’t always work, and that’s ok. But it’s important to model that as well. Workshops shouldn’t go as planned. While we often script out demos and get everything working perfectly the first time, maybe it’s important to stumble along and reassure us all that we don’t always know what we are doing, and things sometimes just don’t cooperate with us. The idea of building failure into an assignment is interesting, so that students have to struggle with something and then realize they simply can’t complete the assignment as “expected.” I wonder about this, and go back and forth between thinking this is a cheat, or a way of manipulating students, or a positive learning experience. It all depends on how it is presented and reflected upon, I suppose.

Strategies for integrating digital pedagogy into the curriculum was also brought up; at Gettysburg, we have a pretty in with this, as our Special Collections staff have a great track record of connecting collections with classes, and much of what we have is digitized, so it’s not too big of a leap to consider how to integrate more digital materials into classes and take the next step and find ways to apply DH methods to the materials. Special Collections is also on the lookout for new materials that strengthen the curriculum, which can be digitized and shown to classes, so there’s certainly a mechanism to exploit there. As we try to be very curricular-focused in what we acquire and digitize, and try to work closely with students to support their original research, there’s a path to greater integration of DH into the broader curriculum. Our DH efforts have very much revolved around our Special Collections and telling stories with them, and we have become a very narrative-based shop in a lot of ways, as opposed to DH that is more data-driven. I think that’s good, since there’s a lot of interest in our collections and how they are used for classes, so playing to our strengths and existing relationships is a good strategy to continue moving forward with.

One thing that really stuck out to me was the idea that your DH program, at some point, has to define what DH is. And it should be a somewhat concrete definition, not nebulous. DHi uses the Digital Humanities Quarterly’s definition as a basis for theirs, with some modifications. Our digital scholarship definition as it relates to the DSSF program certainly could use some strengthening, and after this summer, I hope we are in the position to revisit it. Right now, we spend part of the first day trying to define what is DH, and thefirst and last student blog posts of the summer deal with the act of defining DH, especially as a shifting concept that may not have a set definition. Perhaps in the future, we need to have our definition ready and have them critically engage with that definition instead, and force us to revisit it on a regular basis to see if we need to change it.  That seems to be a more sustainable idea, and one that may help give us focus.

css.php