The End of the Fellowship: Where am I now?

It has certainly been an interesting and rewarding year as a first year fellow at the Center.  The life of a PhD student–much less a first year PhD student–is filled with trial, error, struggle, and hopefully at times, victory.  I came to the Roy Rosenzweig Center for History and New Media with little to no knowledge of the digital world outside of checking my e-mail and Facebook.  I’d never had a Twitter account, I had no clue what Python was, and html looked like a foreign language.  I can happily say that nine months later, I have a Twitter account, I’ve created my first digital history project with a proficiency level in html and css–but I still just cannot wrap my mind around Python.

After working at the Center for a year and spending time in all three divisions I can say that I have a much better grasp of the digital world, digital history, and what it means to be a member of this growing field.  I am proud to say that over the last year I’ve worked on multiple projects that have made me feel like I belong in this community and can continue to grow in my personal goals.  This semester in  the Education division, I had the opportunity to work with one of my favorite organizations–National History Day.  I did a lot of background work for their 100 Leaders project–collecting data, organizing tallies, and adding and organizing that data onto the website.  However, one of the most gratifying projects over the semester was working on information that will be implemented into the online DH certificate that will be offered by the university and the Center in the Fall of 2015.

I would like to thank the Center for giving me this incredible opportunity.  While it has been a trying semester I have learned many things that I can now use to further my career in academic history. While I will not be returning to the Center in the fall and will be returning to my love of working with undergraduates I am excited to show everyone at CHNM how much I was able to learn when I present a digital portion of my dissertation in the coming years.  I believe what I learned in both my Clio courses–especially Clio II–gave me a strong foundation that will make for promising research.

Thank you RRCHNM.

 

Live Tweeting–Is this always a good idea?

One of the requirements as a RRCHNM fellow is to live tweet once a semester the interesting things that happen around the Center.  Last semester this requirement was simple.  I was fortunate enough to live tweet the first year fellow trip to the National Mall during our time in Public Projects.  We ran up and down DC testing Histories of the National Mall and completed a scavenger hunt that drew attention to many of the historic sites in the area.  It was an interesting time, full of goofiness, excitement, and entertainment.  My live tweets came with images of the scavenger hunt and different types of media that made my live tweeting more of a pleasure for my followers.  It was easy to create tweets at least once every twenty minutes and from the amount of likes and retweets I received, I assume that my day of live tweeting went over well.

Similarly, the fellows and I added an extra day of tweeting at the 20th anniversary conference for RRCHNM.  While this event was a lot more professional than our scavenger hunt on the Mall, I was still able to tweet out all day long–even gaining followers across Open Source advocates and national museums.

It was a great experience!  However, by the time second semester came around I had a much more difficult time finding an outlet to live tweet.  While interesting things happened around the center this semester, the first year fellows were certainly more about business than testing or conference going.  Every week I waited for an interesting opportunity to tweet for the Center and my followers.  However, nothing extraordinarily interesting that I could draw out for an entire day ever came my way.  The good news is that we were working!  We just didn’t do anything my followers were interested in hearing about all day long. Plus, the portions that would have made for incredible days of live tweeting during my time in education had to be kept under wraps until the projects we were working on went live.

The last week of our fellowship I decided that it would be a good idea to live tweet our fellow sponsored DH Help desk that we and the second year fellows host every week. This help desk allows students to come to the Center and ask for help in their Clio Wired classes.  Since it was the end of the semester, a large percentage of PhD students had some sort of Clio Project due and we knew that our desk would be flooded with last minute questions on html, css, and mapping, I thought this would be the best chance to live tweet.

Well.  My live day of tweeting did not go the way I would have liked.  Unlike running up and down the National Mall and listening to a handful of panels chaired by the biggest names in our field–it was me, the fellows, and a bunch of confused PhD students.  In essence, no one but us gave a dang about what we were doing.  I think I even lost a Twitter follower or two by grasping at straws throughout the entire day with lame tweets.

While I feel like my live tweeting day crashed and burned like no other, I think this assignment taught me and the other fellows a lot about using social media to promote organizations and/or academic interests.  If you don’t have anything thoughtful to tweet, you probably just shouldn’t tweet.  There is a level of professionalism that must be upheld and we all follow that one person on Facebook or Twitter who fill our feeds up with nonsense and we resent them.  In order to remain respected, it’s best to leave live tweeting to some of the more important and enlightening events.

However, just in case you are interested in my by “Barney the Dinosaur-esque” tweets, here is the feed:

 

My First Year Fellow Experience in the Education Divison

My first semester in the Education Division of RRCHNM has been an interesting and educational experience. Since January, I’ve been lucky enough to work on the 100 Leaders project for National History Day and played a major role in adding up leader votes in different ways and then uploading them to the 100Leaders.org website.  What made the project so interesting was that (after 100 days of voting) the results were far from what anyone at NHD or RRCHNM expected.  Interestingly, once voting opened in November, social media voters from other countries started pouring in and these votes single handedly knocked down most of the famous western leaders that many people thought would steal the top ten.  Instead of Washington, Lincoln, and Jefferson as the most influential leaders, voting ended with Muhammad taking the number one spot, Mustafa Ataturk in second, followed by Jesus of Nazareth in third.  On the 100 Leaders website, National History Day published a fascinating background story on the findings and how so many votes were cast from outside of the United States.

After working for weeks on the 100 Leaders website, I was also given the opportunity to work on the new Digital Humanities online certificate that will be offered by George Mason University through RRCHNM in Fall 2015.  This exciting new project for the university and the center also comes with a lot of background work.  Everyone in the Education division has been very hands on—from recording interviews from creators of digital humanities projects to transcribing those projects, to outlining assignments.  I’ve had the opportunity to research a lot of the projects that new certificate students will be asked to complete.  As a content provider, I’ve been on the lookout for different types of digital archives, content data bases for mapping and text mining, and open source/copyright free sites so students have the best tools available when learning what exists in the digital world.

Outside of working in the Ed division, the first year fellows and I have had the interesting opportunity of holding Clio II tutoring sessions every Monday between noon and 5pm.  At our table in the center we offer help on the PhD required Clio II projects where all of us have been asked to create a digital history project and build our own websites from scratch.  While I was the first year digital history fellow who came in with the least amount of knowledge in DH, being able to tutor on coding has not only helped with learning HTML, CSS, Java Script, etc, it’s given me a confidence that was severely lacking last semester. I’ve learned through helping others build websites and have become a pro at looking up answers for website building questions and can now quickly solve issues.  Last semester I was nervous and lost.  The Clio II help desk  has helped me retain knowledge of coding and I’m excited that I no longer have to constantly lean of W3 schools for information.  I’m finally retaining how to move an object from point A to point B on my computer screen.

While there is only a month left in my fellowship at RRCHNM I am thankful for how much I’ve learned this semester and look forward to how much more I can cram in my brain in the following months.

 

Reflections on the End of the Semester

For the last part of our first semester at RRCHNM, we were asked to create Omeka exhibits for the 20th anniversary website.  Since I’m studying the Revolutionary Era and have been interested in the Papers of the War Department since I arrived at the center earlier this fall, it was an easy decision to take on PWD for an Omeka exhibit.  However, the farther along I got into the project, the more complicated I realized it was going to be.

In all honesty, it took me a lot longer than normal to figure out what the heck I was doing.  It’s not that I misunderstood the directions, it’s that I couldn’t wrap my head around telling the story of PWD with Omeka without  replicating the site that already existed.  How do you tell the history of a virtual archive and a plugin like Scripto without much visual data outside of grants?  I wasn’t alone either.  Jordan, Alyssa, and I all stared at each other for a few days over our projects, trying to figure out how we can get our stories across without being text heavy and with more visuals.

Fortunately, Sharon Leon—director of Public Projects—came to my rescue.  Sharon not only told me  the fascinating story behind the creation of PWD, but she graciously gave me sets of graphs, an article she had written about Scripto and PWD, and a few leads on what would make great visuals for an Omeka exhibit.  Since we only had to have four pages for our exhibit, I decided to dedicate one page to Sharon’s article and graphs, one page on reviews of PWD by outside sources, a narrative on the creation of Scripto for PWD, and a page on Scripto from the administrator’s point of view.  While my themes don’t exactly tell a fluid narrative, with only four pages and a topic with very few visuals, the project turned out fine.

However, I will add that this exhibit was definitely not my best from the rush of the end of the semester and the amount of visuals I had to tell my story.  I am very excited that Dr. Robertson is letting us work on our exhibits into next semester and on our own time because I still believe that there is much to be done on the project and resources that I have yet to tap into.  I believe that adding a few oral histories on people who worked on both PWD and Scripto, as well as copies of grants would make this project much better.  The story of PWD is fascinating and deserves a clear and detailed exhibit, which is something that calls for much more time, research, and resources.  I have all the faith that this project will come together in the spring.

Reflections on #RRCHNM20

I always know I chose the right profession when conference season comes around.  I get excited for conferences like children get excited for Christmas and  every year I plan my schedule around them.  When I found out that the Roy Rosenzweig Center or History and New Media 20th anniversary conference landed on my birthday this year, it seemed appropriate.

However, the RRCHNM20 was unlike any history conference that I’d ever been to before.  At times I was mesmerized by the conference and other times I felt like a complete deer in the headlights.  I was expecting it to be like all of the other conferences that I attended and presented at in the past, where there was a fixed schedule of rooms full of people who stared at the speakers and nodded their heads constantly.  This definitely was not the environment of my first digital history conference and–in a way–  it was a lot more refreshing.  Having the ability to have a say in what panels would be presented that day by voting in between sessions and watching the audience live tweet intently made me fell like I was a part of something more important and like my opinion mattered along with everyone else’s.

The sessions I attended dealt with subjects that affect the world of digital history and the entire historical community.  How do we fight the cultural constructs of gender in our field and give women the same respect as men in centers?  How do we collaborate more with public historians and museums in order to reach larger audiences?  Perhaps one of the most important: how to we get the funds to accomplish all of these goals?  These sessions were encouraging and inspiring because at time it felt like a digital history summit to take over the world instead of listening to panels with three different interpretations of the exact same subject.  It was refreshing and terrifying.

The conference reminded me exactly how new I am to digital history and that while I’ve learned so much in one semester (thanks to RRCHNM) that I still have a long way to go in the field before I truly understand enough to feel comfortable making assertions in panels or offering my own opinions in front of the digital historians whose articles I’ve read in class.  I felt very much like a green horn, especially after Dr. Robertson turned on the large screen in the conference room with the live #RRCHNM20 tweets.  All of a sudden my 20 tweets a minute turned into 2 tweets an hour because I realized these digital history giants would be reading my Twitter banter.  I started questioning whether on not I had to right to comment on digital history when so many people in the room had built its foundations.

While my own fears got the best of me at times, I was constantly surprised and comforted by the amount of the support in the sessions and throughout the conference.  I was approached by many digital historians who knew that I had the words “graduate student” tattooed on my forehead.  Many people asked me questions about my research, the support I’d received from RRCHNM, and why I chose George Mason.  It was fun to explain that I’d chosen George Mason because of RRCHNM and how I wanted to become a part of something bigger in our field and I knew digital history was what would get me there.  The digital historians at the conference made me feel –even though I had my own concerns over how much I actually knew–that I belonged in this group of tech-savy historians.

The conference also reminded me how lucky I am to be at RRCHNM.  Listening to all of the stories about Roy, his legacy and what that means to digital history, left the biggest impression of what exactly I am a part of.  I go to work every day for a center that not only changes our conceptions of history, but reaches audiences at the academic, public, and international level with our projects and tools.  RRCHNM’s 20th anniversary conference has reminded me of why I got into history into the first place.  It’s all about changing the way we view our pasts and teaching to large audiences.

Tweeting on the National Mall

I am still getting the hang of Twitter and how to use it for academic purposes.  For years I refused to create an account because I wasn’t sure exactly what purpose it served and I didn’t want to be on another form of social media shared with distasteful celebrities.  However, now that I’ve been expected to keep up a Twitter account I’ve realized it’s much more than celebrities and tabloid news.  It has been a fun experience following other historians and getting to understand the tech humanities a little bit more.  However, while I’ve gotten used to reading other people’s tweets, I’m still getting the hang of tweeting my own thoughts out in the Twitterverse.

Live tweeting was a very interesting experience. I purposefully chose what would be an exciting day to do my live tweeting so I would have a  little bit better of a chance of not being a boring tweeter.  The day we tested the Histories of the National Mall in DC and I knew there would be lots of pictures and fun experiences that would make for a good day of reading for all of those who cared to follow me.

While I managed to get out quite a few tweets, testing a mobile website and switching back and forth between Twitter was a little bit more difficult than I had initially planned—which should have probably been the first issue that popped into my mind when I chose that day. However, Alyssa, Jordan, and I managed even though I was usually a few feet behind them playing on my phone so I could tweet more of our day out.

The only other issue we had was the length of the day.  We ended up being able to test the mobile website a little bit faster than anticipated, which meant that my day of live tweeting was cut just a little shorter than I would have liked.   I did manage to get out plenty of tweets full of interesting information about mobile testing on the Mall and it appeared the people following us from the center enjoyed watching us run around the National Mall attempting to find new clues on our scavenger hunt.  Those invigorating tweets can be found here:

 

Reflections on Public Projects

Last week Alyssa, Jordan, and I completed our final rotation in Public Projects.  When I first arrived at RRCHNM, Public Projects was one of the divisions that I was most eager to experience due to my background in public history.  I am in the process of finishing up my public history certificate at Southern Miss and I have always wanted work with or pursue an entire career in public history projects.  This love for public history is what made me excited to learn and understand the digital work that goes into some of the RRCHNM projects that used since I was an undergraduate.

Our first week in Public Projects was one of the most difficult, but definitely one of the most educational.  As my blogs have shown from our rotations in Research and in Education, my coding skills definitely need some work.  However, our mentor that week—Megan Brett—was exactly what I needed to understand code life a little better.  She helped us understand SSH and was able to help me and my PC keep up with everyone else and their Macs.  For once I was never left behind with Alyssa and Jordan two or three steps ahead of me because tutorials weren’t adequate enough for PCs.  Megan was able to help me understand my windows PowerShell and never became frustrated when I forget one of the dozens of commands when trying to manipulate Omeka.  Whether it was Megan’s patience or the fact that I’ve been here for an entire semester and things are finally starting to stick, my first week in Public Projects made me feel like I was finally getting the hang of things around the center and that I could actually “talk tech.”

In week two with Public Projects, the first year fellows were sent on a mission to conduct mobile testing on Histories of the National Mall. The experience was exciting not only because we got to spend an entire work day on the National Mall, but because we were able to find some of the issues with the site on our phones.  Since I’m the one of the three of us with the least flashy technology (PC and Android kid), it was fun to see Histories of the National Mall working well and at a good download speed, whereas Jordan’s was a little slow and poor Alyssa could never find a wifi network for her ipad.  It was my own personal win for the week!  However, we were able to find a few content problems, specifically with Ghost Sites, that we were able to bring back to Public Projects.

In the last two weeks of Public Projects, we were tasked with adding newly submitted documents to the 9/ll Digital Archive.  The center recently received donated materials from Brian Sullivan who worked for the FAA around 9/11 and we were asked to submit them to the Omeka site.  We reviewed the 17 documents that were submitted and then created descriptions and other portions of Dublin Core that were needed before the documents can go live on the site.  On one of our days going through the documents we were even able to watch a documentary (Please Remove Your Shoes) that was also submitted by Sullivan so we could add it to the collection.  Aside from absolutely never wanting to fly again after going through the FAA documents and watching the documentary, I really enjoyed going back to one of the reasons I wanted to become a historian—going through primary sources.

My four weeks in Public Projects was a great experience, not only because I’m finally starting to find my way around the center, but because I was genuinely interest and excited about the content we were able to learn and create.  Sharon and Shelia made all three of us feel like we’d been in Public Projects the entire semester and it was such a smooth transition to begin working with everyone in the division because of how welcomed we felt.  The things I learned in Public Projects, especially working with Omeka, are something that I will be using throughout the rest of my time at Mason and hopefully for a dissertation project.  I’m excited about the possibility of working more with Public Projects in the future and cannot wait to learn more.

Reflections on the Education Division

Over the last four weeks the first year fellows had the opportunity to work in the Education division of the RRCHNM.  Since the start of our first year fellowship, working in the Education division was something that I was really looking forward to—especially since a lot of the projects they were completing were with National History Day.  As an undergraduate and MA student at Southern Miss, National History Day in Mississippi was always one of my favorite times of the year.  Having the opportunity to work with middle school and high school students on History Day projects and offering an outlet for students who were more gifted in the liberal arts has given me something to be proud of over the years and I was excited to do some work with the Education division on the national side of History Day.

Working in the Education division was more than just learning new aspects of something that I was already interested in, it was like coming back to my nice “cuddly blanket” of history that I was a little bit more familiar with.  While I enjoyed working with Research immensely, after having my ups and downs with Python coding and reaching the mid-point of my first semester as a PhD student, the Education division made me feel like I was “coming home” and it reminded me that I was still useful and could learn new things at a faster pace.

The first assignment we were given was to locate photographs of the 100 leaders for the 100leaders.org website.  While I initially thought this task would be simple, I quickly learned a lot about the overly complicated world of copyright laws.  I had always assumed that famous paintings and photographs became famous because they were open access and freely used enough by the public to become recognizable and iconic—e.g. Washington Crossing the Delaware.  Oh, how wrong I was.  While I had a feeling it would be difficult to find open access photos of Walt Disney (because Disney is notoriously good at copyrighting everything), I was more than shocked to discover just how difficult it was to find an image of Thomas Jefferson, George Washington, Benjamin Franklin, etc.  These are some of the most famous and recognizable figures in American history and it is almost impossible to find a copyright free image of them for public use.  Even other—not as well-known—leaders such as Ray Kroc, and Rachel Carson would exceedingly difficult to find images of due to copyright laws.

In order to show how important these leaders were without using their own images, Jordan, Alyssa, and I had to get a little creative with our searches.  For instance, since Susan B. Anthony only has one or two open access pictures, I found free images of women protesting for their right to vote.  For Ray Kroc, I found an image of a retro McDonald’s and so on.  While it was frustrating at times trying to find new ways to represent the 100leaders, it was also an exciting challenge that reminded me of why I love history so much and chose it as a career.  The hunt can be frustrating, but when you find that one image that brings everything together it makes you feel like Indiana Jones.  There were definitely many “booyahs!” yelled out from my side of the fellow’s table.

Finding these images made up the majority of our work in Education and I learned so much from it.  I’ve had the opportunity to teach History 101 (pre-history to 1500CE) twice at the university level and after working on the 100 leaders project I’m aiming to teach a world history course again this summer.  Going through bios, finding pictures, and learning about figures that I’d never heard of before has made me want to revamp my lectures and inspired me to look at different ways of teaching. While I’m sure this wasn’t necessarily an intended lesson from Education, I’m so grateful it reminded me of how much I love history, research, and teaching.

In our time in the Education division we were also asked to do some testing on the 100leaders website before it goes lives in November.  Sitting down at the Education table and giving Thomas Edison a constant rating of “1s” is what I call a pretty fantastic day.  However, outside of my historical hate of Edison, I discovered that I’m interested in how these websites are created.  Getting to give feedback on whether the “slider” was working properly or how many times the system would lock up depending on voting made me want to explore more of the technical side of Education.  Even though we didn’t get to work with the design and construction of the website, I was constantly shocked by how many different components went into creating a simple slider and how many options there were for creating the pages for voting.  I had the same curiosity when we were asked to create a manual for the 100leaders website once Education hands the website off to National History Day.  I was in charge of creating a step-by-step guide for editing resources on the website.  Writing this portion of the guide helped me to better understand the inner workings of a wordpress website and also let me see all the ways these sites can be manipulated.  While we weren’t able to help create portions of the website, it definitely made me want to explore more with coding for future use.

I will definitely miss working in the Education division.  I looked forward to going to work every day and working on topics and projects that I love.  I’m excited by the possibility of working in the Education division again and will actively keep up with their projects throughout the rest of the semester.

 

Research Division Reflections

My first few weeks as a Digital History Fellow at RRCHNM have been both an amazing experience and a complete challenge.  Before I began my PhD program, I didn’t really understand digital history and I wasn’t quite sure what I would be doing during the first year of my fellowship.  I had a hunch that I would learn some computer programing, do some blogging, and for some crazy reason thought that I would be digitizing historical documents.  However, my first few weeks in Research taught me that my ideas about digital history and the RRCHNM were a little off.

First, I’ve never had much experience with websites, blogs, etc.  For the 2012 Society for Military History conference, I managed a wordpress website for the program committee to rate and select papers and panels.  However, all I was asked to do was upload posts, pages, and rating systems.  Most of what I was doing was simple copy and paste.  When I heard we would be working with PressForward and Digital Humanities now, I was excited because I would have a leg up on understanding basic components of a wordpress site—not so much.  For the first few days my colleagues Jordan, Alyssa, and I kept looking at each other with complete confusion.  There were so many acronyms and lingo that we’d never heard and jumping into the digital world made me worried that I wouldn’t be able to figure everything out.

However, the Research Division never let us slip and I am so grateful everyone on the team knew that I walked into the fellowship with very little experience.  We were so lucky to have Mandy, Amanda, and Stephanie sit down with us to explain the components of PressForward  (and for me what an RSS Feed even meant) and Digital Humanities Now.  Without a doubt, working on Digital Humanities Now was my favorite part of the last four weeks.  Having the opportunity to be an editor at large and select dozens of articles collected by PressForward made me feel like I was living in a digital world, but kept me in my comfort zone—i.e.  intense sessions of reading.   We got about two or three days to look through PressForward, mining for different articles that would be worthy of a front page spot on Digital Humanities Now, and then had the opportunity pick which articles were chosen for that week.  Mandy showed us how to use wordpress and publish the top stories, as well as setting up Twitter to tweet out our selections at different times throughout the day.

Learning PressForward and what goes into updating Digital Humanities Now was challenging, but fun because after a couple of mistakes playing in sandbox, the material started to click and I could then recognize and regurgitate steps.  However, the bottom kind of dropped out when we were told our next assignment was to work with the Programing Historian website and learn the ins and outs of Python and Zotero.  I started having problems almost immediately because of my “awesome” PC.  All of the digital history fellows, young and old, have Macs—I do not.  I had to download different programs than Jordan and Alyssa, such as Text Wrangler, and any time I a problem would occur not many people in the room could figure out what was going on to help me.  After about a day we had things up and going and I starting the Programing Historian tutorials.  Like I said before, I’ve never worked with programing and I was excited to start these tutorials because “Programing Historian” sounds like a step-by-step guide for those in the humanities who have never used a computer for more than research, Facebook, and e-mail.  This was not necessarily the case.  While the first four lessons were simple enough, I felt like I started fighting the tutorials and the tutorials started fighting me.  After eight years of higher education in the liberal arts, I’ve been trained to question everything.  Why does a “/” go in front of this phrase?  Why do I have to have a variable?  Why do I have to set up a string?  I wasn’t questioning programing to be a big liberal arts jerk, I honestly just wanted to know why.  I’ve been trained for almost a decade to understand how and why patterns work and then after that it sticks in my head and it becomes a natural reflex.  The problem I faced was not with the programing, but with letting go of having only one very specific way of learning a new tool.  Jordan told me quite a few times that there doesn’t have to be a reason for the amount of spaces and slashes in programing—you just do it.  Once I stopped fighting with myself, I finally started learning how to write code.

Once I was past my natural reflex of being stubborn, I started having a few more problems.  Programing Historian for Microsoft really has a tendency to just “run away with itself.”  I kept getting multiple errors and could never get further than the sixth tutorial because no one really around me understood why my computer was being crazy and Programming Historian doesn’t show what to do if you have common errors.  I knew there were free coding tutorials online, but very few offered lessons in Python.  Jordan suggested that I use Code Academy and within minutes I was on a tutorial page and learning code at double the speed of Programing Historian.  I was doing well with Code Academy and even got to yell out to the fellow table every time I collected a new badge.  However, within about two days, Jordan and Alyssa were on entirely different places in their Programing Historian tutorials than I was in Code Academy and I could no longer ask them questions about how to do “this” and “that” and they couldn’t really ask me anything either.

I appreciate Programing Historian because it taught two out of three people how to code in Python.  It’s not that we didn’t like each other; it’s just that our relationship really wasn’t working out and Programing Historian and I decided to see other people.

Challenges are a huge part of a PhD program and I knew I would have them starting out in a field of history in which I had very little experience. I’m sad that my time in Research is over because I was just getting the hang of Python and I really want to explore more options and how to manipulate Zotero for my personal research needs.  Everyone in Research was constantly at my side, making sure that I had all of the tools I needed to learn PressForward, Digital Humanities Now, Programing Historian, and Zotero.  I can honestly say that I am glad the first part of my fellowship was spent in the Research division and I’m excited at the possibility of working with them once again.