If Text Then Code

  • About the Course
    • Course Goals
    • Course Modules
  • Important Information
    • Contact Me
    • Policies
  • Schedule
  • Assignments
    • Reflection Posts
      • Prompt #1
      • Prompt #2
      • Prompt #3
    • “Found Text” Abstracts
    • Build Your Own Website
    • Write Your Own Text Adventure Game
    • Publish Your Own Digital Edition
    • Final Project
    • Rubrics
  • Resources
    • Readings
    • Tool Kit
    • Tutorials & Exercises
  • Reflections

Standardize, Organize, and Finalize: Neil and Ella Take on TEI

December 11, 2016 by Ella Ekstrom

Neil and I were apart of the Editorial Staff regarding TEI markup standards and revision. Our goal was to refine the markup in a way that focused on the clarity, consistency, and effectiveness of the tags themselves. For example, we found a limited use of the tag <roleName> surrounding terms like “Capt” or “Gen”. However, when it transferred to the extract file, it did not include the context of whom it was referring to, and it was not used consistently throughout the journal, therefore it proved to be neither clear nor consistent so we dropped its use. Instead, we kept the role titles within the <persName> tag. Yet, even so, we still found variation in spelling of certain names as well as a general ambiguity as to who each person referenced was. Therefore, we collected all the extract data under the tag persName, organized it, and researched civil war records to determine whom Linn was referring to. Then, we created TEI ID tags, such as #CGS for Captain George Shorkley, to include more information like birth, death, full name, and position on the names that were most referenced. This helped us find true spelling for names as well as provide a clearer and more in-depth understanding of the context Linn was writing about.

Going through the text further, we found insufficient use of tags like <name type=”event”>, used to describe weather or meals, and the <trait> tag, so we decided to remove them given their inconsistency and general inapplicability to the rest of our project. We also decided to add a tag that we saw wasn’t being used, <orgName>, to describe army groups or other organizations, which otherwise were mislabeled under <persName>.

We found the need to add specificity to certain tags as well, such as what we did with the TEI ID tags, but instead using “n” within the tag. For example, to specify certain places, like Roanoke, we used <placeName n=”Roanoke Island”> to clarify. Also, we decided to add use of n=”pers” and n=”weather” under the <state> tag, to clarify between the descriptions of emotional or descriptive state, and the state of the weather. Finally, for objects, we used <objectType n=“boat”> to indicate which were ships or boats.

Individually, after we made a decision of our overall goal and set the TEI standards, we split up the work accordingly. Neil would individually revise the TEI markup detail throughout the document, while I wrote the statement explaining our decisions and goal as the staff. Then I took the data from the persName extract to determine the identities and correct spelling of those mentioned using Civil War databases, and then I created and defined the TEI ID tags that Neil then applied to the document. Together we discussed whether certain terms should be included under certain tags and we each double checked spelling and formatting of the document when we finished.

screen-shot-2016-12-11-at-4-34-53-pm

This is a screenshot of the excel sheet that I used to organize all the data I collected of each identity from different Civil War databases.

screen-shot-2016-12-11-at-4-45-38-pm

After determining which of the names were used most frequently, I created and defined TEI IDs for each, including information like their title, full name, birth, and death.

I found this project to be a culminating experience, where the whole class worked together to finalize not only a topic that has been the focus of a large portion of this semester, but also by having each of us use skills learned throughout the semester. My favorite part, however, was knowing that all of our work will go toward something larger than the class itself, a unique history that hasn’t been touched by any other institution but ourselves. This unparalleled history is the key feature of this project and I am so grateful to be apart of the process.

Filed Under: Prompt, Reflections

Vibing while Transcribing

November 17, 2016 by Ella Ekstrom

When I first read one of James Merrill Linn’s letters, the script itself felt both foreign and strangely familiar. Ever since 6th grade, I have been encouraged to write in cursive with incentives such as extra credit or praise until it became a genuine habit continuing to this day. Although my handwriting can be quite artistic and neat when I want, if I am rushing to write an in-class essay or scribble down some notes, my handwriting becomes its own manuscript in need of deciphering. In this sense, I felt a bond with Linn’s script that I don’t usually encounter, given most all my other friends and professors simply use a print script in writing. However, there is more than a century of difference that would account for the difficulty in understanding certain words or phrases. Also, certain letters took time to recognize, but once I did the whole process became easier.

My procedure for transcribing consisted of splitting my computer screen between the image of Linn’s letter and a Word document, allowing me to simultaneously read and transcribe. Nevertheless, for certain
documents, I ended up printing them out so I could highlight and markup words I
couldn’t understand to get a fresh perspective when figuring them out. However, nothing compared to actually being able to read the document in persoscreen-shot-2016-11-17-at-9-23-23-pmn. I really enjoyed having the trip to the Archives as our culminating experience for transcribing because it was as if all my struggles with certain phrases or words were resolved as soon as I held the document itself. This is especially true in relation to my first document, which was a letter from John Merrill Linn to his brother John Blair screen-shot-2016-11-17-at-8-16-35-pmLinn, where in the middle of the first page JML drew a diagram (of what I would assume to be the arrangement of their housing situation) over the text, making it nearly impossible to read unless in person. Seeing the actual document, you can see the pen marks and indentation, making it easier to figure out if something is a conscious marking or merely a smudge. Also, in comparison to simply looking at the image on the computer, being able to hold the document, you don’t need to scroll from word to word, or line to line, but instead you have everything before you in one place—screen-shot-2016-11-17-at-9-26-51-pm fullsizerender-8providing context that allows you to easily connect sentences to the letter’s subject on a whole. Yet, even if no original copy were available (though having one is extremely convenient) having a scan or picture still allows you to transcribe most all of the document—given that the original document itself is legible.

When I encoded the semantics, I went through the document methodically and marked names and places. Then I decided to define terms such as “North Carolinians” or “Virginians” as organizations, given that Linn was referring to their military establishments, as well as the Greek Organizations he mentioned. Then, the objects I found most relevant were those such as the ones he personally acquired or wished to, like the “big knife,” as well as the biscuits and butter he beautifully described at the end. For the most part, JML talked about larger military plans versus detailing objects or things so there weren’t as many objects to be marked—nor traits or states for that matter.

Now since my letter was dated February 11th, it is before the journal entries begin, so I can only look at the entries afterward. However, the entries seem much more cheerful than what was expressed in the letter. My assumption is that the dreadful rain he referred to in his letter cleared up by the time he wrote those entries. Also in the second entry he talked of finally having clean clothes, which would definitely boost one’s mood. The other possibility is that he might just sound more pessimistic or somber when talking to his brother versus being quite upbeat in his own personal journal. However, there is no way to know for sure.

Filed Under: Reflection #3, Reflections

FYI via TEI

October 30, 2016 by Ella Ekstrom

In regard to the relationship built while encoding text, I do believe that TEI helps you better understand the subject matter and writing itself, and even though the same understanding could be accomplished by hand and paper, it could not be analyzed to the same extent, nor shared with the same ease.

In my experience marking up the semantics within Edgar Allen Poe’s The Murders in the Rue Morgue the first observation I noted was that there were multiple titles and names used to describe the main characters—which I found could pose difficulty if not identified specifically. I also found that it would be most effective to limit the items that I identify to those of most relevance to the story—the evidence from the crime scene. Lastly, I believed that Poe’s use of French and Latin proved to be a significant part of the story as well. So, with this all considered, I framed my markup accordingly. To identify the main characters, I used keys to indicate whom Poe was referring to. For example, “Frenchman” was a term used to reference Dupin, so I encoded it as such: <rs key=”Dupin” type=”person”>Frenchman,</rs>. Next, to identify which items I believed to be evidence, I marked them as such: <rs type=”evidence”>grey human hair</rs>. Finally, when foreign terms were used, I identified them as such: <foreign xml:lang=”latin”>_quondam_</foreign>. Overall, TEI provided precise identification tools that weren’t available in the previous programs we used in class, allowing me to not only categorize key themes or ideas within the story, but also to organize each accordingly by type and their underlying intention. Thus, TEI pushed me to dig into the text deeper, which I might not have done if I were simply formatting the text.

In our most recent project involving the Declaration of Independence, we explored more of the origin behind the documents creation—the analysis of the signers themselves. When filling out the person ID, you are allowed to go into as much or as little detail as required. For Samuel Adams, I was given many choices as to how I could interpret the tags and thereby fill them out. For example, in the affiliation tag, I was given the choice between stating the religious or political affiliation; instead, however, I decided to incorporate both. Thus, I used “n=” to distinguish one from the other: <affiliation n=”Political”>Democratic-Republican</affiliation>. Next, considering Adams did not simply have one occupation, I chronologically listed his professional progression using “n=” as well: <occupation n=”5″>President of the Massachusetts Senate</occupation>. Finally, to indicate those in relationship to Adams, I was not able to use the typical “active” tag, since we solely identified signers of the document with xml:id’s required. So, given the slightly confining nature of the “relation” tag, I expressed the spouses of Adams using “n=”: <relation name=”spouse” active=”#SAMA1″ n=”Elizabeth Checkley”></relation>. Overall, TEI allowed the reader of our document to go beyond simply reading the signatures within the Declaration of Independence to being able to grasp a quick summary of each signer, to see both how they all connect to the document and how the document ties them all together.

For these documents and others we have interacted with during class, they possess the potential to be shaped and formatted in ways that expand beyond merely displaying text. As indicated by Krista Stinne Greve Rasmussen, there is a “distinction between stationary and sequential works: stationary works (such as paintings and sculptures) are conceived in space, while sequential works (such as literature and music) are conceived in time.” These “sequential works” allow us more liberties in regard to their presentation, allowing for original and innovative means in both their formatting and analysis. Now in connection to the use of TEI, these coding liberties extend all the way from being able to identify the author’s syntactical choices to expanding upon the context within the text—providing links to historically relevant information, background information, or even linguistic origins of certain words or phrases. As stated by Elena Pierazzo, “for digital editions based on text encoding the editorial interventions are all present at once in the source, they are just not displayed at once.” I believe this accurately articulates how informative TEI can be. TEI can be as dense or as empty as the encoder wants; yet, the depth by which this work goes into is solely revealed by the extent at which the reader interacts with the document. The work done with TEI is not one that is blatantly obvious. Instead, it is embedded within the text, and its recognition is at the mercy of the reader. Thus, both the encoder and decoder play a large role in how the work is perceived and thereby understood.

Filed Under: Reflection #2, Reflections

Partners In Crime

September 26, 2016 by Ella Ekstrom

Ambiguity. Mystery. History. Those three words define the foundation on which our project will be constructed. However, in contrast to the typical crime-solving structure, it will be a crime-creating game. As the player, you have graduated from Bucknell University and are desperate for work. You have two best friends, Neo, the com-sci engineer, and Christopher, the history major. After following a suspicious series of events, you three are prompted to “follow the whale” and, in doinbean-1997-rowan-atkinson-9g so, ultimately end up in a gang located in Hong Kong, with a mission to steal a major artifact from the museum. Throughout the game, as you are evading the law and completing dangerous missions, your deeper motivation will be to uncover the true motive behind the orders given to you and the root cause behind it all.

The focus of our game is mainly placed on the series of interactions between members of the gang and authority figures, with the missions being merely background tasks that just help to tie the story together. This relates to the idea in Literary Gaming that “in computer games and gaming as literary art, narrative, dramatic, and/or poetic techniques are employed in order to explore the affordances and limitations of rules and other ludic structures and processes,” (“Introduction,” Literary Gaming). We plan on creating a game that is driven by context and conversation—with suspicion laced onto each action described and an ambiguous motive behind every statement—with stimulating puzzles and secretive missions mixed in. Using terms from Literary Gaming, the core gaming strategy we therefore will use would be that of “cognitive ludicity,” (i.e. cognitive reading strategy), with “ergodic ludicity” (i.e. physical interaction with the software) and “ludic mechanics” (i.e. videogame-inspired technology such as winning and losing mechanics) as secondary forces. Essentially, we wish to involve the player’s mind more so than their keyboard when striving to win.

The greatest benefit of working in collaboration is that of the added creativity and collective skill that comes along with it. From our first brainstorming session, I witnessed the creative spark that spread like wildfire, lighting a myriad of inspired ideas almost effortlessly. Everyone focuses on and notices different things, so by adding other perspectives, you are able to illuminate aspects of the project that you might have otherwise overlooked if solo. However, with new perspectives also comes the possibility of contradicting perspectives, which could end up being counterproductive. Yet, disagreement can allow for further growth by which the best sides of each idea might be molded into a newer and better idea. In our group, each person has his or her own personal flair. My own niche tends to be one concerning the design and aesthetic of something, whereas Neil’s would be in the creativity and smoothness of the story, and given Dale’s experience with Python, his focus would be within the coding.

unnamed-1For me, I was greatly inspired by the “Open Sorcery” game I played during class. Despite its seemingly simple structure of providing textual context and then asking for the player choice of response, the compelling storyline added a vivacity that glowed through the unassuming text. It also incorporated riddles as a means of succeeding at a task, which I loved. These qualities are what I wish to construct our game with. Other inspirations for our game include The Matrix, such as “follow the whale” in comparison to “follow the rabbit,” and one of the main character’s names being Neo (which also sounds suspiciously similar to the name Neil).

Filed Under: Reflection #1, Reflections Tagged With: ambiguity, history, Mystery

HUMN 271

Bertrand 012
TR 9:30-11:20am
Dr. Diane Jakacki

Authors

  • Dale Hartman RSS feed
  • Diane Jakacki RSS feed
  • ejp013 RSS feed
  • Ella Ekstrom RSS feed
  • jaa023 RSS feed
  • Jingya Wu RSS feed
  • Julia Wigginton RSS feed
  • Matthew Fay RSS feed
  • Matthew Lucas RSS feed
  • Neil Lin RSS feed
  • Peter Onusconich RSS feed
  • Sarah Rosecky RSS feed
  • Tong Tong RSS feed
  • Xing Fu RSS feed
  • Yash Mittal RSS feed

Creative Commons License

Creative Commons License Bucknell University Humanities 271 Course by Diane Jakacki is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Copyright © 2023 · eleven40 Pro Theme on Genesis Framework · WordPress · Log in