Discussion: Comparing Emily Dickinson XML Projects

[ebeshero]

The short poems of Emily Dickinson have generated lots of excitement and serious digital humanities projects in our time. Web technology lets more people than ever before view "photo facsimiles" of the tiny scraps of paper on which she wrote, and text encoding has transformed and remixed and circulated the poems to give them a digital rebirth. Let's review and discuss some of these projects to see what text encoding can do with the way we read a poet. This should also get you used to writing in markdown on GitHub Issues!

Browse the following projects and choose two to discuss together in your post. You'll need to be patient and "dig around" some of these sites to get to the poems. I'll provide a little guidance to get you in to each one:

1. Radical Scatters: Emily Dickinson's Late Fragments and Related Texts, 1870-1886

   • Skim around the introductions to get a sense of what this site is archiving.
   • Then wander about in the Browse documents: dig into a collection and select some poems: look at each reading view and look at the XML code.

2. Emily Dickinson Project (fascicles 16 and 6) (made/remade by my students from 2015/16!) :-)

   • Try interacting with some specific poems posted on this site, such as Poem 1605, and look at the Dash Reduction Analysis. What can you learn about how Dickinson a) wrote variations on her own wording, and b) how publications of her poems altered her work? How are you able to learn about this?

3. Emily Dickinson Archive: An open-access website for the manuscripts of Emily Dickinson

   • There are three ways to explore this site from the front page: either by Searching the text of the poems for a word or phrase, by browsing by library collection, or by Lexicon: looking up words and definitions pulled from Dickinson's poems. Try exploring some of each.
   • For the Search box, try plugging in some words that jump out at you from the Lexicon. Suggestion: try the word "bee" or the word "fly"
   • If you look up the word "funeral" you'll see how this site archives versions of Poem 1605 represented in the Emily Dickinson student project.

In your posts, comment on how any two of these sites compare with each other for a) how you interact with Dickinson's poems: how are they represented and what is the reading experience like? b) what you can see of the text encoding: How easily can you find the markup, and what kinds of things can you see in the markup? How does the markup compare between the two projects you're looking at?

This is a discussion! Since each of you is responding here, you can reply to each other, help each other out (it's tricky to to get a view of the code in the Emily Dickinson Archive but it is there!), and also feature examples. Please feature some markdown code blockss in your posts! (You may also include some screen captures to comment the website navigation, but please use code blocks if you're talking about code!)

<feature>
         <example type="codeBlock">XML code block</example>
</feature>

[HadleighJae]

Radical Scatters

The XML was easy to find as you can get the TEI in the Encoding tab.

This database focuses on the original written poems of Emily Dickinson. It separates them by how they are rendered. For example, in poem a94, the element looks as follows:

<div2 type="poem" xml:id="a94-1.txt.1" rend="fair-copy draft">

The xml:id distinguishes the different poems from each other while the rend attribute separates the different types of ways the text was written. In another poem, the element looks like this:

<div2 type="poem" xml:id="a516.txt.1" rend="intermediate-copy draft">

Below the <div2> element is a comment that describes the type of handwriting that was used and the ink:

<div2 type="poem" xml:id="a94-1.txt.1" rend="fair-copy draft">
    <!--   hand="fair" ink="ink"  -->

<div2 type="poem" xml:id="a516.txt.1" rend="intermediate-copy draft">
    <!--  hand="intermediate" ink="pencil"   -->

Emily Dickinson Project

The XML is very easy to find, as it is located right next to the various versions of the poem.

This database focuses less on the original poem, but more focuses on the different variants of the poem. The different values in the wit attribute show that there are multiple versions of the same Emily Dickinson source depending on the variants. The id's help distinguish which variant includes what. Anything outside of the <rdg> and <app> elements are the same throughout all variants. The value #df16 means that it is in the original version (or how it's written). The value #fh means that it's in Final Harvest. The value #ce means it's in The Poems of Emily Dickinson: Centenary Edition. The value #poems3 means it's in Poems, Third Series

<l n="1">
I felt a
<app>
<rdg wit="#df16 #fh">Funeral</rdg>
<rdg wit="#ce #poems3">funeral</rdg>
</app>
<app>
<rdg wit="#df16 #fh">,</rdg>
<rdg wit="#ce #poems3"/>
</app>
in my
<app>
<rdg wit="#df16 #fh">Brain</rdg>
<rdg wit="#ce #poems3">brain</rdg>
</app>
,
</l>

Emily Dickinson Archive

The Text Encoding was quite literally almost impossible to find. I had to inspect the website element and find the TEI link in there. Here's the link if anyone is struggling to find it: TEI XML for 1650

This one was interesting because I could look at the differences between the way this encoded Poem 1605 compared to the Emily Dickinson Project.

What I notice is that the Emily Dickinson Archive focuses on just having the transcription of the poem in its data rather than showing the different versions of the poem.

Archive:

<lg type="stanza">
    <l>And then a Plank in Reason, broke,</l>
    <l>And I dropped down, and down --</l>
    <l>And hit a World, at every 
        <app type="revision">
            <lem>Crash --</lem>
            <rdg>Crash --</rdg>
        </app>
    plunge,
    </l>
    <l>And 
        <app type="revision">
            <lem>Got through --</lem>
            <rdg>Got through --</rdg>
        </app>
    Finished knowing -- then -- 
    </l>
</lg>

Project:

<lg>
    <l n="17">
        <app>
            <rdg wit="#df16 #fh">And then a Plank in Reason, broke,</rdg>
            <rdg wit="#ce #poems3"/>
        </app>
    </l>
    <l n="18">
        <app>
            <rdg wit="#df16 #fh">And I dropped down, and down—</rdg>
            <rdg wit="#ce #poems3"/>
        </app>
    </l>
    <l n="19">
        <app>
            <rdg wit="#df16 #fh" type="var0">And hit a World, at every plunge,</rdg>
            <rdg wit="#df16" type="var1">And hit a World, at every Crash—</rdg>
            <rdg wit="#ce #poems3"/>
        </app>
    </l>
    <l n="20">
        <app>
            <rdg wit="#df16 #fh" type="var0">And Finished knowing—then—</rdg>
            <rdg wit="#df16" type="var1">And Got through—knowing—then—</rdg>
            <rdg wit="#ce #poems3"/>
        </app>
    </l>
</lg>

Both show the revision, but the Project focuses on the various versions of the text rather than just the written original.

[rcc5418]

Radical Scatters

The different files were super easy to find and sort through here, since they're organized in a ton of different ways. I chose to look at one that was labeled as having a tear that obfuscated the writing's content. Here's how the tear in the page was shown:

<gap reason="damage, document torn" extent="extent of loss unknown"/>

What the encoding (a361 by the way) didn't seem to document was the newspaper fragment caught on the second page. Some of it was illegible, and upside down/difficult to read, but for it to be lacking entirely seems strange, especially when notes like this are included:

<milestone rend="this line is only partly visible" unit="absent" type="horizontal_line"/>

Looking at another example (a760), I could tell that even when the lines are pretty legible, they're not encoded in the same way I would've:

<ab type="passage">
I hope it may
<lb/>
sometime be that
<lb/>
you will chance
<anchor xml:id="delend07"/>
<lb/>
<gap reason="damage, document torn" extent="one or more lines lost"/>
</ab>

the lb element stands for a line break, but I would've just encoded each line individually instead of putting a bunch of self-closing elements. Anyone else have a particular take on this?

In all, I think the poems encoded on Radical Scatters could stand to be more legible in their encoded forms. To completely deconstruct a poem's readability kind of feels insulting in a way.

Emily Dickinson Archive

I found the Archive a lot less satisfying to navigate. It just came across as a little harder to find something interesting right away as compared to Radical Scatters. I did like how the poem was written in XML, it was a lot more readable than the Radical Scatter example I used:

         <lg type="stanza">
                    <l>Bees are Black,<app type="division"><lem><lb/></lem></app> with Gilt Surcingles - </l>
                    <l><app type="emendation"><lem>Bucaneers</lem><rdg>Buccaneers</rdg></app> of Buzz - </l>
                    <l>Ride abroad in<app type="division"><lem><lb/></lem></app> ostentation </l>
                    <l>And subsist on<app type="division"><lem><lb/></lem></app> Fuzz - </l>
         </lg>

I suppose the lines could be numbered, but I don't think it matters that much. I couldn't find the same writing from Radical Scatter in the Archive, despite its 'search by opening line' function (I got a lot of results that didn't really match what I searched). Perhaps that collection is just a bit incomplete. I wish it was as browsable as Raidical Scatters is.

[rcc5418]

Response to @HadleighJae 's post Nice job deciphering the meaning of the attributes in the Emily Dickinson Project. Regarding the Emily Dickinson Archive, there's no need to inspect the website element. You can download the work's XML file by clicking the 'About Work' dropdown in the Text window at the right of the screen. Scroll down, and you should see a button labeled 'Download as TEI', which will let you download an XML file you can open in Oxygen.

[Remdog712]

Radical Scatters (R.S.) VS Emily Dickinson(Fascicles 16 and 6) (E.D.)

Both seem to be very strange from a website perspective. Radical Scatters feels like a mess of links until you reach a normal looking homepage, but E.D. Project has a clean home page and standard layout but then the poems are hidden under each fascicle which turns into a new dropdown menu.

Radical Scatters has a really nice layout for each paper. Different ways to view each which I know must've been some killer leg work.

Looking into Radical Scatter's XML is incredibly clean. I can really appreciate their comments adding about the physical description to keep track of and reference the real piece of paper.

<!--  hand="rough" ink="pencil"  -->

Most of the XML makes sense though I can't figure out what something like this would mean:

<rdg corresp="a156.4" xml:id="a156.3">
remember
<lb/>
</rdg>

It's very well crafted and provides a lot of context when looking between pages about how each are crafted physically let alone in the words on the page.

For E.D. once you reach the poems, the website layout is really nice. Simple buttons to go between variations and overlap them. Really nice stuff and even an immediate XML showing rather than a new window like Radical Scatters.

Some of the XML that worries me are links to off sites and images that I feel may have a tendency to break.

<ref target="http://catalog.hathitrust.org/Record/100654113">Hathi Trust Digital Library</ref>

I won't claim to know much about XML and correct me if I'm wrong but per word there's a lot of repeating tags that I'm not sure what they have to do with per line.

<app>
<rdg wit="#df16 #fh">And then a Plank in Reason, broke,</rdg>
<rdg wit="#ce #poems3"/>
</app>
</l>
<l n="18">
<app>
<rdg wit="#df16 #fh">And I dropped down, and down—</rdg>
<rdg wit="#ce #poems3"/>
</app>

It's also not major but there's no mention on some of the Fascicle poems XML about the paper itself. They capture the meaning but miss on possible details if they were to become important later.

[Remdog712]

@rcc5418 I'd agree with you on Emily Dickinson Archive. I avoided it as I could barely get my bearings in looking for the actual XML. I think a good site on top of good XML really matters when trying to preserve history. How much information is necessary on a site when looks are not the goal.

[TylerDollard]

Radical Scatters When looking at these websites, Radical Scatters might seem a bit messy with lots of links before you find a regular homepage. On the other hand, the E.D. Project has a neat homepage but hides the poems under separate sections, which can be a bit confusing.

Radical Scatters has a well-organized layout for each paper, with different ways to view them that probably took a lot of work to set up.

If you check out Radical Scatters' XML, you'll see it's very well-structured. They also include comments about the physical details of the original paper, which is helpful for tracking and understanding the real paper. It describes how you are holding your pencil and what type it is below. <!-- hand="intermediate" ink="pencil" --> Here are more of them<div2 type="poem" rend="fair-copy draft">all describe the type of draft and how it was written <!-- hand="fair" ink="ink" -->

Emily Dickinson Project

This database primarily focuses on the diverse iterations of the poem rather than its initial form. The variations noted in the wit attribute denote multiple versions of Emily Dickinson's source, depending on the different interpretations. The IDs are used to differentiate which version contains specific elements. Anything beyond the and elements remains uniform across all versions. The value #df16 signifies the original rendition or its initial wording. #fh corresponds to Final Harvest, #ce stands for The Poems of Emily Dickinson: Centenary Edition, and #poem3 indicates Poems, Third Series.

<app>
<rdg wit="#df16 #fh">And then a Plank in Reason, broke,</rdg>
<rdg wit="#ce #poems3"/>
</app>
</l>
<l n="18">
<app>
<rdg wit="#df16 #fh">And I dropped down, and down—</rdg>
<rdg wit="#ce #poems3"/>
</app>

[lgmccurdy]

Radical Scatters The interaction with Dickinson's poems on this site was pleasurable, as they are organized into various different categories and has a nice interface when viewing each poem. The XML is easy to access through an "Encoding" tab in which you will be taken to a new window that displays the code. The XML is nicely formatted and understandable. They use many different elements and attributes to describe features throughout the text.

<del rend="strike-out" status="unremarkable">best </del>

In this example, you can see how they used the rend attribute inside the del element to describe the strike made through the word in the original drafted poem.

You can see also how depending on the element, the same attribute used might have different meanings

<div2 type="poem" xml:id="a444.txt.1" rend="fair-copy draft, incomplete">

In this case, rend is being used to describe the status of the of the poem.

Emily Dickinson Project The Dash Reduction graph was very informative in how much the published versions of Emily Dickinson's reduced her dash usage. Through the graph, you are able to see exactly which published versions had greater amounts of reduction. While viewing Poem 1605, I liked the color coding aspect and how you could view each variation either individually or all stacked on top of each other. This allows for a good understanding of the differences between each variation. The XML is also easy to access as the "View Original XML" button takes you right to the code. I do wish there was an option to view it in a separate window however. Like "Radical Scatters", this code is also well organized and neat.

<app>
<rdg wit="#df16 #fh">Brain</rdg>
<rdg wit="#ce #poems3">brain</rdg>
</app>

In this example, you can see how the ID's are used to specify which versions have which elements. the "wit" ID is used to show which versions have certain differences in capitalization or punctuation for example. You can see in this example that version "ce" and "poems3" have brain lowercased while versions "df16" and "fh" have brain capitalized.

[ceq5032]

Radical Scatters

Upon opening up the website you are greeted with an array of links that send you to different fragments of text. The introductory text was exciting to read and I could tell whoever worked on this project was very passionate about it. Finding the XML coding was super easy. The web page itself is very easy to navigate.

Manuscript A523 <gap: Stating that there is a missing part to the document. reason="damage, document torn": The reason for the gap is because the document is torn. <gap reason="damage, document torn"/>

Manuscript A508 type="poem": indicates that the information is a poem. xml:id="a508.txt.1: Can be seen as a reference. rend="intermediate-copy draft?": Maybe a draft version of the text? <div2 type="poem" xml:id="a508.txt.1" rend="intermediate-copy draft?">

Emily Dickinson Archive

The website is easy to navigate and the reading views are super creative and unique. Finding the XML code was very easy. I feel like the XML code compared to Radical Scatters was written more in depth and had better structure.

Fascicle 6: Poem 1

The XML code represents four lines of poetry. The code uses <app> and <rdg> elements, along with line numbers (n attributes) to identify each line. ( I used ChatGPT to help explain this code to me. I am newer to XML and it was an excellent resource for me.)

<l n="1">Who never lost, are unprepared</l>
                <l n="2">A <app>
                    <rdg wit="#df6 #CP">Coronet</rdg>
                    <rdg wit="#ce">coronet</rdg>
                </app> to find<app>
                    <rdg wit="#df6 #CP">!</rdg>
                    <rdg wit="#ce">;</rdg>
                </app></l>
                <l n="3">Who never thirsted<app>
                    <rdg wit="#df6 #CP"></rdg>
                    <rdg wit="#ce">, flagons</rdg>
                </app></l>
                <l n="4"><app>
                    <rdg wit="#df6 #CP">Flagons, and Cooling Tamarind!</rdg>
                    <rdg wit="#ce">And cooling tamarind.</rdg>
                </app></l>

I really enjoyed navigating both websites. In my opinion I felt that each website offered the necessary information needed to research the archives of Emily Dickinson.

[ceq5032]

@HadleighJae When looking at Emily Dickinson Archive I could not find the XML coding. Thank you for providing the link to the code. I think it was very clever to inspect the website element.

[VocaloidOtaku39]

Emily Dickinson Project (Project 2)

When I looked into Poem 1605, between the XML archive and the project version, I saw that some of the lines were written differently. In the original archive, the first stanza of the poem is coded like this:

<lg type="stanza">
                    <l>I felt a Funeral, in my Brain,</l>
                    <l>And Mourners to and fro</l>
                    <l>Kept treading -- treading -- till it seemed</l>
                    <l>That Sense was breaking through --</l>
                </lg>

And when I viewed the page source to the Emily Dickinson project website (Ctrl+U), it was coded like this:

<lg>
<l n="1">
I felt a
<app>
<rdg wit="#df16 #fh">Funeral</rdg>
<rdg wit="#ce #poems3">funeral</rdg>
</app>
<app>
<rdg wit="#df16 #fh">,</rdg>
<rdg wit="#ce #poems3"/>
</app>
in my
<app>
<rdg wit="#df16 #fh">Brain</rdg>
<rdg wit="#ce #poems3">brain</rdg>
</app>
,
</l>
<l n="2">
And
<app>
<rdg wit="#df16 #fh">Mourners</rdg>
<rdg wit="#ce #poems3">mourners</rdg>
</app>
<app>
<rdg wit="#df16 #fh"/>
<rdg wit="#ce #poems3">,</rdg>
</app>
to and fro
<app>
<rdg wit="#df16 #fh"/>
<rdg wit="#ce">.</rdg>
<rdg wit="#poems3">,</rdg>
</app>
</l>
<l n="3">
Kept treading
<app>
<rdg wit="#df16 #fh">—</rdg>
<rdg wit="#ce #poems3">, </rdg>
</app>
treading
<app>
<rdg wit="#df16 #fh">—</rdg>
<rdg wit="#ce #poems3">, </rdg>
</app>
till it seemed
</l>
<l n="4">
That
<app>
<rdg wit="#df16 #fh">Sense</rdg>
<rdg wit="#ce #poems3">sense</rdg>
</app>
was breaking through
<app>
<rdg wit="#df16 #fh">—</rdg>
<rdg wit="#ce #poems3">.</rdg>
</app>
</l>
</lg>

Looking back to the Emily Dickinson Project, more punctuation was added between the dashes to make the story appear to be more grammatically correct. Also, specific words were repeated to give off the effect that it was highlighted in red. For every few words, some extra lines of code were added into the Emily Dickinson Project to add punctuation, like this:

<rdg wit="#df16 #fh">—</rdg>
<rdg wit="#ce #poems3">.</rdg>

Emily Dickinson Archive (Project 3)

When I looked up the term "funeral", I found that part of the code takes me to the original document that I found in the Emily Dickinson Project:

2</td><td><a href="[/editions/2/image_sets/12169674](https://www.edickinson.org/editions/2/image_sets/12169674)">I felt a Funeral, in my Brain,</a></td><td>1861</td><td></td><td>Johnson Poems 1955</td><td>J280</td><td><a class="m" href="[#](https://www.edickinson.org/search#)" data-i="2740">+</a></td></tr>

When I clicked on the link that was provided in the code, I even found that part of the code was rewritten from the poem. However, the text on that website was slightly modified from the original:

<li><a href="[/editions/1/image_sets/12174464](https://www.edickinson.org/editions/1/image_sets/12174464)"><span class='work-number'>F340 A</span><span class='work-title'>I felt a funeral in my brain </span></a></li>

Also, the poem was also coded differently if we were to compare Sites 2 and 3. On the Emily Dickinson Archive, the first stanza of Poem 1605 was coded like this:

<body>
<!--StartFragment-->

<p class="stanza linebreak-emily" data-number="0">
--
  | <span class="line" data-line="1">
  | I felt a Funeral, in my Brain,
  | <br class="emily author"/>
  | </span>
  | <span class="line" data-line="2">
  | And Mourners to and fro
  | <br class="emily author"/>
  | </span>
  | <span class="line" data-line="3">
  | Kept treading - treading - till<br class="emily"> it seemed
  | <br class="emily author"/>
  | </span>
  | <span class="line" data-line="4">
  | That Sense was breaking through -
  | <br class="emily author"/>
  | </span>
  | </p>

<!--EndFragment-->
</body>
</html>

In both poems, both forms of code represent different elements of the text, especially modifications of punctuation, such as reducing dashes and grouping lines together. These archives made the reading experience of the poem easier to navigate which lines contain certain words. The markup varies on each page source on whether the text is grouped together, intricately coded to add emphasis on certain words or lines, and the identification of how Emily Dickinson wrote her poem, making the markup on these sites easy to locate.

[VocaloidOtaku39]

@HadleighJae thank you so much for helping me find the link to the XML archive of Poem 1605!

[GKon26]

The first site, Radical Scatters: Emily Dickinson's Late Fragments and Related Texts, 1870-1886, does a good job explaining what each link is about and gives you an intro on how to navigate the archive. Very well formatted, the code was simple to find and it was successful in what it did. I like the way this XML was formatted, as it is line by line, very easy to understand.

<div2 type="fragment_extrageneric" xml:id="a809.txt.1">
<!--  hand="rough" ink="pencil"  -->
<ab type="lines">
<seg type="trace" corresp="a802.trace.1 oresman.trace.1 bplhigg116.trace.1" xml:id="a809.trace.1">
What a
<lb/>
Hazard
<lb/>
a Letter
<lb/>
is -
</seg>
<seg type="trace" corresp="a802.trace.2 oresman.trace.2 bplhigg116.trace.2" xml:id="a809.trace.2">
When
<lb/>
I think of
<lb/>
the Hearts
<lb/>
it has
<seg type="var" corresp="a809.2" xml:id="a809.1">
Cleft
<lb/>
or healed
</seg>
I
<lb/>
almost
<lb/>
wince to
<lb/>
lift my Hand
<lb/>
to so much
<lb/>
as as a
<lb/>
superscription
<lb/>
but then we
<lb/>
always Ex
<lb/>
cept
<lb/>
ourselves -
<lb/>
<pb rend="reverse (A 809a); paper flipped over right and rotated one-quarter turn left"/>
<seg corresp="a809.1" xml:id="a809.2">
<hi rend="indented">or</hi>
<lb/>
Scuttled and
<lb/>
Sunk
<lb/>
</seg>
</seg>
</ab>
</div2>
</div1>

On the second site, Emily Dickinson Project (fascicles 16 and 6), it was interesting to learn how the versions she made were different than the ones published. Some are subtle while others are significantly different. I believe she changed how she wrote to go along with the changes made in the publishing area. The XML for this site was also easy to obtain.

<teiHeader>
<fileDesc>
<titleStmt>
<title>Fascicle 6: Poem 1. 601/73/variant</title>
<author>Emily Dickinson</author>
</titleStmt>
<publicationStmt>
<p>Fascicle 6: Dickinson's variants and published versions</p>
</publicationStmt>
<sourceDesc>
<msDesc>
<msIdentifier>
<repository/>
<idno>601</idno>
</msIdentifier>
</msDesc>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<front>
<div type="references">
<listRef>
<ptr target="xml/fs601.xml"/>
<ptr target="img/601/fs601.jpg"/>
<ptr target="img/601/fs601-Map.jpg"/>
<ptr target="img/601/601CP.jpg"/>
<ptr target="img/601/601CP-Map.jpg"/>
<ptr target="img/601/601ce.jpg"/>
<ptr target="img/601/601ce-Map.jpg"/>
</listRef>
</div>
<div type="witness">
<listWit>
<witness xml:id="df6">
<bibl>
<title>ORIGINAL POEMS: Fascicle 6</title>
<author>Emily Dickinson</author>
</bibl>
</witness>
<witness xml:id="CP">
<bibl>
<title>The Complete Poems of Emily Dickinson</title>
<author>Dickinson</author>
<editor>Thomas H. Johnson</editor>
<pubPlace>Boston</pubPlace>
<publisher>Little, Brown and Company</publisher>
<date>1960</date>
</bibl>
</witness>
<witness xml:id="ce">
<bibl>
<title>The Poems of Emily Dickinson, Centenary Edition</title>
<author>Emily Dickinson</author>
<editor>Martha Dickinson Bianchi and Alfred Leete Hampson</editor>
<pubPlace>Boston</pubPlace>
<publisher>Little, Brown, and Company</publisher>
<date>1930</date>
</bibl>
</witness>
</listWit>
</div>
</front>
<!-- 2016-03-27: nll: We'll need to make sure we use CSS to create the underlining, italicizing, and quoting! -->
<body>
<head>
<title>Poem 1 (J 73: 1830-1886)</title>
</head>
<lg>
<l n="1">Who never lost, are unprepared</l>
<l n="2">
A
<app>
<rdg wit="#df6 #CP">Coronet</rdg>
<rdg wit="#ce">coronet</rdg>
</app>
to find
<app>
<rdg wit="#df6 #CP">!</rdg>
<rdg wit="#ce">;</rdg>
</app>
</l>
<l n="3">
Who never thirsted
<app>
<rdg wit="#df6 #CP"/>
<rdg wit="#ce">, flagons</rdg>
</app>
</l>
<l n="4">
<app>
<rdg wit="#df6 #CP">Flagons, and Cooling Tamarind!</rdg>
<rdg wit="#ce">And cooling tamarind.</rdg>
</app>
</l>
</lg>
<lg>
<l n="5">
Who never
<app>
<rdg wit="#df6">Climbed</rdg>
<rdg wit="#CP #ce">climbed</rdg>
</app>
the weary league—
</l>
<l n="6">
Can such a foot
<app>
<rdg wit="#df6">Explore</rdg>
<rdg wit="#CP #ce">explore</rdg>
</app>
</l>
<l n="7">
The
<app>
<rdg wit="#df6">Purple</rdg>
<rdg wit="#CP #ce">purple</rdg>
</app>
territories
</l>
<l n="8">
On
<persName>Pizarro</persName>
's shore?
<!-- 2016-03-27: nll: Should we tag Pizarro as a persName? -->
</l>
</lg>
<lg>
<l n="9">
How many
<app>
<rdg wit="#df6 #CP">Legions</rdg>
<rdg wit="#ce">legions</rdg>
</app>
overcome
<app>
<rdg wit="#df6 #CP">—</rdg>
<rdg wit="#ce">?</rdg>
</app>
</l>
<l n="10">
The
<app>
<rdg wit="#df6 #CP">Emperor</rdg>
<rdg wit="#ce">emperor</rdg>
</app>
will say
<app>
<rdg wit="#df6 #CP">?</rdg>
<rdg wit="#ce">.</rdg>
</app>
</l>
<l n="11">
How many
<app>
<rdg wit="#df6">
<emph rend="underline">Colors</emph>
</rdg>
<rdg wit="#CP">
<emph rend="italic">Colors</emph>
</rdg>
<rdg wit="#ce">colors</rdg>
</app>
taken
</l>
<l n="12">On Revolution Day?</l>
</lg>
<lg>
<l n="13">
How many
<app>
<rdg wit="#df6">
<emph rend="underline">Bullets</emph>
</rdg>
<rdg wit="#CP">
<emph rend="italic">Bullets</emph>
</rdg>
<rdg wit="#ce">bullets</rdg>
</app>
bearest?
</l>
<l n="14">
<app>
<rdg wit="#df6 #CP">Hast Thou the Royal scar?</rdg>
<rdg wit="#ce">The royal scar hast thou?</rdg>
</app>
</l>
<l n="15">
Angels
<app>
<rdg wit="#df6 #CP">!</rdg>
<rdg wit="#ce">,</rdg>
</app>
<app>
<rdg wit="#df6 #CP">Write</rdg>
<rdg wit="#ce">write</rdg>
</app>
<q rend="double" type="emph">Promoted</q>
</l>
<l n="16">
On this
<app>
<rdg wit="#df6 #CP">Soldier's</rdg>
<rdg wit="#ce">soldier's</rdg>
</app>
brow!
</l>
</lg>
</body>
</text>
</TEI>

[JordanJ7]

The interaction with Dickinson's poems on this site was very interesting. They are organized into different categories and has a nice interface when viewing each poem.

<del rend="strike-out" status="unremarkable">best </del>

In this example, they used the rend attribute inside the del element to describe the strike made through the word in the original drafted poem.

<div2 type="poem" xml:id="a516.txt.1" rend="intermediate-copy draft">

above the <div2> element describes the type of handwriting that was used and the ink.

This database focused less on the original poem, but more focuses on the different variants of the poem. The different values in the wit attribute show there are multiple versions of the same Emily Dickinson source depending on the variants.

[LPHerschell]

Radical Scatters

On the first site, Radical Scatters: Emily Dickinson's Late Fragments and Related Texts, 1870-1886, Dickinson often uses ambiguity and symbolism within her writings to her advantage. In the example below, she says "A Half a Dozen kissed/ the Eaves -/ And made the Gables/ laugh," describing raindrops that have "kissed" various locations. The XML for this cite was relatively easy to understand and acquire.

<ab type="stanza">
A Drop fell on the
<lb/>
Apple Tree -
<lb/>
Another - on the Roof -
<lb/>
A Half a Dozen kissed
<lb/>
the Eaves -
<lb/>
And made the Gables
<lb/>
laugh -
<lb/>
</ab>

Emily Dickinson Project

On the second site, Emily Dickinson Project (fascicles 16 and 6), Dickinson continues to utilize ambiguity in her writing. Although the writing style feels similar, the format of the poem does feel structured differently overall. She writes, "I felt a Funeral, in my Brain," which is a fascinating way to describe ones state of mind. The xml structure is different, but I slightly prefer its more blocked off categorization compared to the previous website.

<td class="df16text">I felt a</td>
<td class="df16">Funeral</td>
<td class="df16">,</td>
<td class="df16text"> in my </td>
<td class="df16">Brain</td>
<td class="df16text">,</td>

[LPHerschell]

@TylerDollard I definitely agree that the websites have messiness here and there. While I was able to traverse both websites, it did pose some confusion and challenge sometimes.

[gylertaydos]

I chose Radical Scatters and the Emily Dickinson Project. I will say, from my navigation, the sites allow you to interact with the texts in very different ways. Radical Scatters is more analytical, featuring essays breaking down and analyzing what her poems mean; the Emily Dickinson Project actually gives you the raw poem (and its altered version) for you to look at yourself.

I thought the reading experience was much better on the Emily Dickinson Project, as the poems are clearly featured and broken down- I found the essays on Radical Scatters quite hard to read.

The XML is very easy to find on the Emily Dickinson Project, as there is a tab on the left side of the screen which lets you bring it up. I know we are just getting started, but I was shocked at how long the page of XML for just one short poem was!

For example, this is a block of code for a single line of poem 1601:

` Before I got my

Eye eye

put out

— ,

`

Usually in class we just mark line breaks and call it a day, but in this line, the word "Eye" is highlighted in red. I'm sure it's not that hard to code when you know what you're doing, but man, this looks intimidating.

[gylertaydos]

Radical Scatters When looking at these websites, Radical Scatters might seem a bit messy with lots of links before you find a regular homepage. On the other hand, the E.D. Project has a neat homepage but hides the poems under separate sections, which can be a bit confusing.

I thought the E.D. Project was much easier to navigate, but I found it really puzzling why they have a tab for the fascicles which then leads to another page with a tab for the poems. I would've figured the fascicles tab would lead to a list of poems to choose from.

[creaturepsu]

When visiting the Radical scatters site, I couldn't find the poems easily without looking back on GitHub for instructions. the browse section has only one link under it so just making the search a part of everything else doesn't seem to make sense, I think a search bar would be more natural. The reading of poems seems fine but requires some scrolling, which itself is just an issue of how the poems were originally formatted I think. When finding the markup of the poems, it was very easy but kind of annoying having to open up a new window to see each markup.

<ab type="passage">
<hi rend="indented">Had</hi>
<lb/>
I known I asked
<lb/>
the impossible -
<lb/>
should I perhaps
<lb/>
have asked it,
<lb/>
but Abyss is it's
<lb/>
own apology -
<lb/>
</ab>
<ab type="passage">
I once asked
<lb/>
him what I should
<lb/>
do for him when
<lb/>
he was not here,
<lb/>
referring half
<lb/>
unconsciously to
<lb/>
the great Expanse -
<lb/>
In a tone italic
<lb/>
of both Worlds
<lb/>
<pb rend="second leaf (NYPL)"/>
"Remember Me," he
<lb/>
said - I have kept
<lb/>
his Commandment -
<lb/>
But you are a
<lb/>
Psychologist, I, only
<lb/>
a Scholar who
<lb/>
has lost her
<lb/>
Preceptor -
<lb/>
</ab>
<ab type="passage">
For the great
<lb/>
kindness of your
<lb/>
opinion - I am
<lb/>
far indebted -
<lb/>
</ab>
<ab type="passage">
Perhaps to solidify
<lb/>
his faith was
<lb/>
for him impossible,
<lb/>
and if for him,
<lb/>
how more, for us!
<lb/>
Your noble and

this section of code was from one of the the radical scatters poem markup. most of the meta data is available on the website to view in the form of tags, commentary, and context. this in turn gave it a cleaner look than the other poem I saw.

the Emily Dickinson project looked much more modern and finding the poems seemed very straightforward. the poems include the digitalized versions as well as a photo of the original on paper. something I found really interesting about this site was how certain words were marked red in the poems. I don't know the reason for this from just looking around the site, but I assume the words marked are ambiguous and it is still not clear what was actually written. the markup was right there alongside the poem and didn't open a new window, which made things more difficult for me since there was so much to see in the markup, and so little of the poem in it. I think I preferred the markup being in a separate window instead

<?xml-model href="Schematron2Dickinson.sch" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>Fascicle 6: Poem 13. 613/78/variant</title>
<author>Emily Dickinson</author>
</titleStmt>
<publicationStmt>
<p>Fascicle 6: Dickinson's variants and published versions</p>
</publicationStmt>
<sourceDesc>
<msDesc>
<msIdentifier>
<repository/>
<idno>613</idno>
</msIdentifier>
</msDesc>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<front>
<div type="references">
<listRef>
<ptr target="xml/fs613.xml"/>
<ptr target="img/613/fs613.jpg"/>
<ptr target="img/613/fs613-Map.jpg"/>
<ptr target="img/613/613cea.jpg"/>
<ptr target="img/613/613ceb.jpg"/>
<ptr target="img/613/613ce-Map.jpg"/>
<ptr target="img/613/613CP.jpg"/>
<ptr target="img/613/613CP-Map.jpg"/>
<ptr target="img/613/613lSD.jpg"/>
<ptr target="img/613/613lSD-Map.jpg"/>
<ptr target="img/613/613poems2.jpg"/>
<ptr target="img/613/613poems2-Map.jpg"/>
</listRef>
</div>
<div type="witness">
<listWit>
<witness xml:id="df6">
<bibl>
<title>ORIGINAL POEMS: Fascicle 6</title>
<author>Emily Dickinson</author>
</bibl>
</witness>
<witness xml:id="CP">
<bibl>
<title>The Complete Poems of Emily Dickinson</title>
<author>Dickinson</author>
<editor>Thomas H. Johnson</editor>
<pubPlace>Boston</pubPlace>
<publisher>Little, Brown and Company</publisher>
<date>1960</date>
</bibl>
</witness>
<witness xml:id="ce">
<bibl>
<title>The Poems of Emily Dickinson, Centenary Edition</title>
<author>Emily Dickinson</author>
<editor>Martha Dickinson Bianchi and Alfred Leete Hampson</editor>
<pubPlace>Boston</pubPlace>
<publisher>Little, Brown, and Company</publisher>
<date>1930</date>
</bibl>
</witness>
<witness xml:id="lSD">
<bibl>
<title>LETTER TO SISTER-IN-LAW (Susan Dickinson)</title>
<author>Emily Dickinson</author>
</bibl>
</witness>
<witness xml:id="poems2">
<bibl>
<title>Poems, Second Series</title>
<author>Emily Dickinson</author>
<editor>Thomas Wentworth Higginson and Mabel Loomis Todd</editor>
<pubPlace>Boston</pubPlace>
<publisher>Roberts Brothers</publisher>
<date>1891</date>
<ref target="http://www.ibiblio.org/ebooks/Dickinson/Dickinson_Poems2.htm#copy">Poems by Emily Dickinson, Second Series (html version)</ref>
</bibl>
</witness>
</listWit>
</div>
</front>
<body>
<!-- 2016-04-08: nll: The poem to Susan Dickinson has a picture sewed to the top of it, so we'll have to describe this.  -->
<head>
<title>Poem 13 (J 78: 1830-1886)</title>

the markup shown above was everything before the first line of the actual poem which is shorter than the one from the radical scatters site. it seems to me that all the metadata of the poem, and the formatting of it was just included in the markup instead of the website. the bibliography is also weirdly cut apart instead of being one whole which I think would've been better just for organizational sake.

[nhammer514]

Radical Scatters

The Radical Scatters: Emily Dickinson's Late Fragments and Related Texts website has a very good interface, making it an easy process to access the XML transcripts of Emily Dickinson's poems. For this assignment, I chose to look at two documents; A711 and H159.

A711 Sample

<div1 type="electronictranscription">
    <div2 type="poem" xml:id="a711.txt.1" rend="fair-copy, enclosed with letter (mailed)">
        <!--   hand="fair" ink="pencil"  -->
        <ab type="line_s_verse">
            <seg type="trace" corresp="a255.trace.1" xml:id="a711.trace.1">
                Last to
                <lb/>
                adhere
                <lb/>
                When Summers
                <lb/>
                swerve away -
                <lb/>
            </seg>
            Elegy of
            <lb/>
            Integrity -
            <lb/>
        </ab>
    </div2>
</div1>

I think it is interesting how, instead of putting each line of the poem into their own independent element tags; they encompass the entire poem in an <ab> element, and separate the lines using self-closing <lb/> elements. Going down the XML document, we find that the metadata is hidden inside the <div2> element. And below that is the <div1> element, which acts as the root for the entire document. Most of the XML documents from the Radical Scatter website is laid out like the sample above.

Emily Dickinson Project

The Emily Dickinson Project website has a very good interface as well, with it being easy to navigate and pleasant to look at. This website has an Analysis page that features graphs, statistics, and paragraphs that analyze the variations of Emily Dickinson's poems. It is very interesting how much the poems can be interpreted with the context of the original texts. For this website, I chose to look at Poem 1605 and Poem 1608.

Poem 1608 Sample

    <teiHeader>
        <fileDesc>
            <titleStmt>
                <title>Poem 8 (J 242: 1861/1945)</title>
                <author>Emily Dickinson</author>
            </titleStmt>
            <publicationStmt>
                <p>Fascicle 16: Dickinson's variants and published versions</p>
            </publicationStmt>
            <sourceDesc>
                <msDesc>
                    <msIdentifier>
                        <repository/>
                        <idno>1608</idno>
                    </msIdentifier>
                </msDesc>
                <bibl>
                    <ref target="http://www.cs.virginia.edu/~ajf2j/emily/"/>
                </bibl>
            </sourceDesc>
        </fileDesc>
    </teiHeader>

If there is one element that stands out the most in the Emily Dickinson Project XML documents, it is that they use TEI infrastructure and namespaces.

        <body>
            <head>
                <title>Poem 8 (J 242: 1861/1945)</title>
            </head>
            <lg>
                <l n="1">
                    When we stand on tops of
                    <app>
                        <rdg wit="#df16">Things</rdg>
                        <rdg wit="#bm">things</rdg>
                    </app>
                    <app>
                        <rdg wit="#df16">—</rdg>
                        <rdg wit="#bm"/>
                    </app>
                </l>
            </lg>
        </body>

Compared to how Radical Scatters organize Emily Dickinson's poems, this website holds each line of a poem in their own <rdg> elements Though, this is likely organized as such to compare the variations between versions of poems, as each <rdg> has an attribute the signifies the version of the poem. This reminds me of another project that also uses TEI namespaces to compare versions of writings.

Summary

Comparing the two websites and the techniques they used to transcribe Emily Dickinson's poems in XML -- the layout of the document changes depending on the archiver's intentions.

[nhammer514]

@gylertaydos

I thought the reading experience was much better on the Emily Dickinson Project, as the poems are clearly featured and broken down- I found the essays on Radical Scatters quite hard to read.

I agree. The scattered nature of the line break elements makes looking at the XML a little confusing. As well, the use of vague <div1> and <div2> elements make the documents feel like rough prototypes rather than carefully laid out transcripts.

[lindseyxwood]

Emily Dickinson Project

When interacting with the poems on this site, you can see the comparison of the actual manuscripts and the variations that were published. Comparing the different versions is helpful when deciphering the specific meanings of words and elements throughout Emily Dickinson's poems.

It was easy to find the markup on this site as it is one of the tabs underneath the different versions. The metadata is easily accessible and the words depicting the markup make sense to the actual information about the poem.

<bibl>
<title>The Poems of Emily Dickinson: Centenary Edition</title>
<author>Emily Dickinson</author>
<editor>Martha Dickinson Bianchi and Alfred Leete Hampson</editor>
<pubPlace>Boston</pubPlace>
<publisher>Little, Brown and Company</publisher>
<date>1930</date>
</bibl>

The markup includes the different versions of the poem, so when selecting the version you want to see, it will depict it for you.

<app>
<rdg wit="#df16 #fh">Bell</rdg>
<rdg wit="#ce #poems3">bell</rdg>
</app>

Emily Dickinson Archive

When navigating through this site, it was a little bit more difficult to browse different poems. You may have to have a previous word or collection to locate a specific poem. The Lexicon option is helpful when finding words in one of Dickinson's poems. If you search for a word, it will give you the different versions of one poem as well. The Emily Dickinson Project seems a bit easier when locating the different versions of the poem as it is a simple click to compare. The poems are also a bit harder to read/find since you have to click on the right-hand side "Text" block and read the small font.

It was a bit tricky to find the markup. It was hidden within a few clicks inside the "Text" box. The metadata does not have a lot of information about the poem within it compared to the one on the Emily Dickinson Project site.

<fileDesc>
            <titleStmt>
                <title>I felt a Funeral, in my Brain, 
</title>
            </titleStmt>
            <publicationStmt>
                <p>The Poems of Emily Dickinson, Johnson, 1955</p>
            </publicationStmt>
            <sourceDesc>
                <p>Emily Dickinson Archive</p>
            </sourceDesc>
        </fileDesc>

The markup does not have any specific information on the different versions of the poem embedded in it. The markup seems to focus on the basic features of one of Emily Dickinson's poems.

<lg type="stanza">
                    <l>And then I heard them lift a Box</l>
                    <l>And creak across my Soul</l>
                    <l>With those same Boots of Lead, again,</l>
                    <l>Then Space -- began to toll,</l>
                </lg>

[lindseyxwood]

@nhammer514

Comparing the two websites and the techniques they used to transcribe Emily Dickinson's poems in XML -- the layout of the document changes depending on the archiver's intentions.

You had an interesting take on the differentiation in the XML markup between the two sites. I never thought of the fact that the different kinds of markup might indicate the intentions of the archiver.

[SonicSpaceFan025]

For this assignment, I looked at "Radical Scatters" and the "Emily Dickinson Archive." When I first accessed "Radical Scatters," I thought the website was hard to navigate because of how many links there are. I read the introductions and learned that the website describes and analyzes multiple fragments of Emily Dickinson's poems, along with XML translations of these poems. The indices section contains images of fragments from Emily Dickinson's poems, which also contain Reading Views and XML encodings of them. In Reading View, the text is easier to read when it was written into a text box. I also like how in the XML translation, the code describes the quality of the poem. In one poem I read, "A 850," I found a line of code in the XML version that read, <add place="composed sideways along the left edge of the manuscript" type="variant"> amazing</add>, which means that the file is an electronic transcription of the poem and that the word "amazing" is written on the left side of the original fragment.

In the "Emily Dickinson Archive," I like how I can filter out different poems by just searching a single word, such as "heart." I am even able to find the metadata of poems at the beginning of their text encoding by using the technique Alyssa showed me (Ctrl+U), and it is easy to understand what it is describing, such as

<html>
<body>
<!--StartFragment-->

<meta name="csrf-param" content="authenticity_token" />
--
  | <meta name="csrf-token" content="fERlvxr9hZ/2Fz6mykU2lEsNqTiHeRo/6VFImLIHQJhe7QkWAOGWGFAARFc+0GGisPyem12wFBarBNOeJpAxtQ==" />

<!--EndFragment-->
</body>
</html>

This means with this method, the encoding there signifies information about not only the poem's contents within the text, but also the poem's primary information such as the metadata, whereas the encoding in part 1 emphasizes information about not only the text's markup, but also the conditions of the paper.

[SonicSpaceFan025]

@VocaloidOtaku39 Hi, Alyssa! Thank you for the Ctrl-U technique! It helped me find the encoding for the poems in the "Emily Dickinson Archive!"

[SonicSpaceFan025]

@LPHerschell Hi, Lyndon! I agree your comments about organization of the encoding you found. With the encoding in the "Emily Dickinson Project," I also find the compact appearance easy to understand, as it is more organized so I can easily read the code.

[TommyMC2]

Radical Scatters is my favorite of the websites. I like how you navigate the browse documents tab. Not only does it let you scroll through the different sections, even if it can be overwhelming to a certain degree. The multitude of drop-down menus may be repetitive, but again, it works well for the abundance of information.

Text encoding is straightforward to access and read since the blocks of text are usually so small. Descriptions of what type of utensil and how the writing looks on the paper are added at the top, while problems or changes in where the text is on the paper are also marked.

The Emily Dickinson Archive was the one I expected to be the least interesting with its display, but the organization and little details on this site could be better. The ability to choose from 3 different site search methods is excellent. The page-turning animations are a nice touch that makes reading more streamlined and universal, even if the pages are generally hard to read. I found this xml harder to find on the site, but it's also there and marks similar to Radical Scatters. I like both of these websites. They do an excellent job at organizing and encoding these works. Still, the one I would recommend is Radical Scatters. Every part of the site works for me, the simple design with things laid out for you at once, while the Emily Dickson Archive had much more effort put into how everything would look.

[SonicSpaceFan025]

@TommyMC2 Hi, Tommy! I agree with your views about Radical Scatters. I also found it difficult to navigate through the Emily Dickinson articles on that website, but I also like the multiple methods of viewing fragments of Dickinson's poems, and that the Emily Dickinson Archive is easier to navigate.

[GarrettStroupe]

Radical Scatters While navigating in this project, it became evident that it prioritized archival and historical accuracy. The browsing feature though pretty dense, allows readers to explore and stumble upon new poems. Each poem has multiple reading views, offering a multifaceted look at the text, which i really liked. The experience is like wondering through a digital archive room and being presented with your choice of content type.

Text Encoding

Upon exploring the documents the XML code can be viewed in the Encoding portion. I chose to examine the poem titled Private Hands (Oresman).

`<?xml version="1.0" encoding="ISO-8859-1"?>

What a hazard an Accent is! When I think of the Hearts it has scuttled or sunk, I hardly dare to raise my voice to so much as a Salutation - E. Dickinson -

        </div1>`

I especially like the way they include subdivisions within the primary division.

<div2 type="letter" xml:id="oresman.txt.1" rend="fair-copy, signed (mailed)">

Emily Dickenson Archive

This site does make it more challenging to view the encoding, I though, but once located, the markup is comprehensive. I like the search capability to get a feel for her pattern of writing and the things she liked to write about.

Text Encoding

For this site, I chose to look at the poem F1660A - But that defeated accent

`<?xml version="1.0" encoding="UTF-8"?> <?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" ?>

The Poems of Emily Dickinson, Variorum Edition, Franklin, 1998

Emily Dickinson Archive

But that defeated accent is louder now than him Eternity may imitate The Affluence of time

` I like **Radical Scatters** site better, I like the way **Emily Dickenson Archive** encodes their XML. Perhaps its similar to what we have been learning. For example the primary content is wrapped in a `` element that contains a `` and `` for stanzas. Wow. As if it wan't clear by my comment, I appear to be having trouble adding code. I pressed command+e and pasted the code within the two "`". Am I not copying the code correctly? I'd love any help or suggestions! Thanks.

[MystKitteh]

Radical Scatters: Emily Dickinson's Late Fragments and Related Texts, 1870-1886

The Radical Scatters: Emily Dickinson's Late Fragments and Related Texts poems are easy to find since they organized the files on the website in a neat order. I chose to look at the following two poems, Drowning is not so pitiful and We | talked with | each other.

The markup in the two following codes will show similarities in how they are labeled and written.

Drowning is not so pitiful | A 1896PC, 12

   <div2 type="poem" xml:id="a1896ps.txt.1" rend="transcript">
      <!--  ink="ink" -->

This is how they sorted the file and showed what the poem was written with.

      <ab type="line_s_verse">Drowning is not so pitiful<lb/>As the attempt to rise.<lb/>Three
         times, 'tis said, a sinking man<lb/>Comes up to face the skies,<lb/>And then declines
         forever<lb/>To that abhorred abode,<lb/>Where hope and he part company -<lb/>For he is <seg
            type="trace" corresp="a169.trace.1" xml:id="a1896PC.trace.1">grasped of God.<lb/>
         </seg>The Maker's cordial visage,<lb/>However good to see,<lb/>Is shunned, we must admit
         it,<lb/>Like an adversity.</ab>

They used self-closing elements to show where each line would end. However, this way does not play nice with pretty print making it hard to see where each line starts. You can also find that they marked up the little imperfections and edits in the code above

We | talked with | each other | A 514

<div2 type="poem" xml:id="a514.txt.1" rend="rough-copy draft, with alternatives">
      <!--  hand="rough" ink="pencil" -->

This is how they sorted the file and showed what the poem was written with.

<seg type="var" corresp="a514.1" xml:id="a514.2">
            <milestone rend="vertical line" unit="absent"/>
<add place="composed_in_the_right_hand_sector_of_the_envelope_separated_from_the_body_of_the_text_by_a_vertical_line"
               type="variant">+ were <lb/>listening <lb/>to the<lb/>
               <milestone unit="absent" type="horizontal_line"/>
            </add>
         </seg>

The code above shows a part that was composed on the right-hand side of the envelope. This is an example of how to store data digitally

Emily Dickinson Project

I found the Emily Dickinson Project code to be much more complicated than Emily Dickinson's Late Fragments. However, this code is a lot more interesting as you can view the different versions the poem went through over time.

                <listRef>
                    <ptr target="xml/1605variant.xml"/>
                    <ptr target="img/1605/fs1605a.jpg"/>
                    <ptr target="img/1605/fs1605b.jpg"/>
                    <ptr target="img/1605/1605cea.jpg"/>
                    <ptr target="img/1605/1605ceb.jpg"/>
                    <ptr target="img/1605/1605fh.jpg"/>
                    <ptr target="img/1605/1605poems3.jpg"/>
                    <ptr target="img/1605/1605ceMap.jpg"/>
                    <ptr target="img/1605/1605fhMap.jpg"/>
                    <ptr target="img/1605/1605poems3Map.jpg"/>
                    <ptr target="img/1605/fs1605Map.jpg"/>
                </listRef>

I noticed that this section has an error in it, but I can't seem to figure out what's causing it. If you know how to fix this please leave a comment!

`

The poems from Emily Dickinson's Late Fragments were much easier to read and to understand what was happening in the XML code. However, once implemented the code from the Emily Dickinson Project for poem 1605 is quite interesting to see and compare the changes through the different versions.

[MystKitteh]

@TylerDollard I one hundred percent agree that the sites can be confusing to navigate at the start. Though it was nice to see the code being consistent between each XML file!

[GarrettStroupe]

@rcc5418

"I couldn't find the same writing from Radical Scatter in the Archive, despite its 'search by opening line' function (I got a lot of results that didn't really match what I searched)"

I had a similar issue! I would have liked to compare the same poem and see their respective XML.

[MadisonSciarrillo]

Radical Scatters, once I clicked on the website, I thought it was very interesting to see many ways to be able to read and view the poems. Also the XML was very easy to find when just pressing the Encoding tab. For the Emily Dickinson archives it was challenging to find the XML for it. Luckily while looking through the discussion post many people tagged links to it. The code includes a rich set of metadata within the<teiHeader>section. This metadata includes the title of the poem, publication information, and source description. This metadata is crucial for cataloging and contextualizing the text. The XML document effectively captures the hierarchical structure of the text. It uses elements such as <div>, <lg>, and<l> to represent the logical organization of the poem, including stanzas and lines. This structural clarity is essential for analyzing and presenting the text.

<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" ?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
    <teiHeader>
        <fileDesc>
            <titleStmt>
                <title>I felt a Funeral, in my Brain, 
</title>
            </titleStmt>
            <publicationStmt>
                <p>The Poems of Emily Dickinson, Johnson, 1955</p>
            </publicationStmt>
            <sourceDesc>
                <p>Emily Dickinson Archive</p>
            </sourceDesc>
        </fileDesc>
    </teiHeader>
    <text>
        <body>
            <div type="transcript" xml:id="J280">
                <lg type="stanza">
                    <l>I felt a Funeral, in my Brain,</l>
                    <l>And Mourners to and fro</l>
                    <l>Kept treading -- treading -- till it seemed</l>
                    <l>That Sense was breaking through --</l>
                </lg>
                <lg type="stanza">
                    <l>And when they all were seated,</l>
                    <l>A Service, like a Drum --</l>
                    <l>Kept beating -- beating --</l>
                    <l>till I thought My Mind was going numb</l>
                </lg>
                <lg type="stanza">
                    <l>And then I heard them lift a Box</l>
                    <l>And creak across my Soul</l>
                    <l>With those same Boots of Lead, again,</l>
                    <l>Then Space -- began to toll,</l>
                </lg>
                <lg type="stanza">
                    <l>As all the Heavens were a Bell,</l>
                    <l>And Being, but an Ear,</l>
                    <l>And I, and Silence, some strange Race</l>
                    <l>Wrecked, solitary, here --</l>
                </lg>
                <lg type="stanza">
                    <l>And then a Plank in Reason, broke,</l>
                    <l>And I dropped down, and down --</l>
                    <l>And hit a World, at every <app type="revision"><lem>Crash --</lem><rdg>Crash --</rdg></app>plunge,</l>
                    <l>And <app type="revision"><lem>Got through --</lem><rdg>Got through --</rdg></app>Finished knowing -- then --</l>
                </lg>
                <lg type="stanza">
                </lg>

            </div>     
        </body>
    </text>
</TEI>

[sammoniot]

Poem 1605 seemed to have more metadata. However, it is important to remember that the poems are of different lengths. The text from 1605 has more highlights/annotations than the radical scatters. The Fascicle 1605 code is:

Immured in Heaven! What a Cell! Let every Bondage be, Thou sweetest of the Universe - Like that which ravished thee! Emily -

The Radical Scatters poem reads:

Immured in Heaven! What a Cell! Let every Bondage be, Thou sweetest of the Universe - Like that which ravished thee! Emily -

[creaturepsu]

@MadisonSciarrillo I agree. its a very clean setup and feels like it was designed to be used for the future. the markup uses simple lanuage to not waste time when writing but is still readable