Past courses of mine have already created digital editions of Duffy’s poetry<\/a>. But if we are going to have confidence in our research, it’s critical that we make sure we have accurate versions of her poems. This assignment will give us the opportunity to spot-check this work since mark-up requires significantly more care than transcription.\u00a0<\/p>\n In addition to providing a better environment for careful attention, a marked-up edition provides us the chance to enrich the text. These enrichments can take the form of adding themes to the metadata, tagging place or person names, or identifying rhyme schemes in the different poems, as infrequent though they may be. If we work\u00a0consistently across all five volumes of the poetry in this process, we will be able to query our markup to highlight similarities and differences between\u00a0The World’s Wife<\/em> and the books that precede it.<\/p>\n Each of us will markup 15 poems, three from each of her five volumes. More specifically, you will each markup the two poems that you select for your daily poetry discussion<\/a>\u00a0plus one that I randomly select. I suppose that this could encourage you to pick shorter poems for your daily discussion, but I also trust you to not game the system too much.\u00a0<\/p>\n Random poem assignments:<\/p>\n Your marked-up poems will be due no later than\u00a0Monday, 18 March<\/strong> by the beginning of class.\u00a0Your reflection papers are due on Wednesday, 20 March<\/strong> by the beginning of class.<\/p>\n Download Oxygen XML Editor<\/a>\u00a0and sign up for a free, 30-day trial. You will receive a license key via email and you will need to use it with your individual copy.<\/p>\n The text of each of Duffy’s volumes is available either on this shared Google Doc<\/a>\u00a0or in our Duffy repository on GitHub<\/a>. The poems are identical in either location, so choose the one that seems easiest for you to work with.<\/p>\n In Oxygen, open the poem template<\/a> from the repo and copy all of its text (Ctrl\/Cmd-A, then Ctrl\/Cmd-C). Then open a new document in Oxygen and paste the template (Ctrl\/Cmd-V) into it.\u00a0Do\u00a0NOT<\/em> start editing the template itself.<\/strong><\/p>\n Name the file as follows: [two-digit number of poem]-[title of poem, underscored if multiple words]-[abbreviation of book].xml, using all lowercase. For example, “Girl Talking” and “Comprehensive” which are the first and second poems in\u00a0Standing Female Nude<\/em> would have the following filenames: Save the file in the appropriate folder in your local copy of the GitHub repo.<\/p>\n Before marking up the poem, check carefully to see whether the poem has been transcribed faithfully from the text. Please pay special attention to the following:<\/p>\n Markup the poem as follows. Be sure to refer to our “Duffy Encoding Editorial Decisions<\/a>” document.<\/p>\n After you’ve finished your work on the poem, make sure you After you have completed your edition, you will write a two- to three-page, double-spaced reflection on the assignment in 12-point Times New Roman. Some questions to consider in your reflection are:<\/p>\nNitty Gritty<\/h2>\n
\n
Get Oxygen<\/h3>\n
Get the poems<\/h3>\n
Create the poem file<\/h3>\n
01-girl_talking-sfn.xml<\/code> and 02-comprehensive-sfn.xml<\/code>, respectively.<\/p>\nCheck the poem<\/h3>\n
\n
<hi rend=\"italics\"><\/code><\/li>\n<\/ul>\nMarkup the poem<\/h3>\n
teiHeader<\/h4>\n
\n
<filedesc><\/code>\n\n
<titleStmt><\/code>\n\n
<title><\/code>: the poem’s title<\/li>\n<respStmt><\/code>\n\n
<persName><\/code>: your name<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<publicationStmt><\/code>\n\n
<date><\/code>: the date you are encoding the poem<\/li>\n<\/ul>\n<\/li>\n<sourceDesc><\/code>\n\n
<bibl><\/code>: the original information about the poem you’re encoding<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\nprofileDesc<\/code>\n\n
textClass<\/code> –> keywords<\/code> –> term<\/code>.<\/li>\nterm<\/code>, you will include a type:\n\n
term<\/code> tag. Be open to themes that are not yet on the list and bring them to the class.<\/li>\nterm<\/code><\/em> tag.\u00a0If there are no characters with identifiable genders, simply write “unknown.”<\/li>\nterm<\/code> tag.<\/li>\nterm<\/code> to indicate whether or not there is a “you” addressed in the poem. Simply write “you” or “no you.”<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<revisionDesc><\/code>\n\n
<change><\/code>: record the date as the value for “when” using YYYY-MM-DD format and add your name\/initials as the value for “who.” Then replace the “?” with a description of what you did. Most of the time, “initial markup” is a good description.\u00a0<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nBody<\/h4>\n
\n
\n
<lg type=\"poem\" n=\"X\"><\/code>. Change the X to the number of the poem\u00a0in the volume that you’re working on. Yes, this will mean counting in the table of contents.\n\n
\n
\n
<lg><\/code>, e.g., <lg type=\"poem\" rhyme=\"ababcdcdefefgg\"><\/code>.<\/li>\n<\/ul>\n<\/li>\n<head><\/code>: the poem’s title<\/li>\n<lg type=\"stanza\" n=\"X\"><\/code> tag. Change the X to the number of the stanza.<\/li>\n<l><\/code> tag and number the lines, e.g., <l n=\"1\"><\/code><\/li>\n\n
<persName><\/code>. If the person is a real person, put in a VIAF<\/a> reference using ref=\"\"<\/code>, e.g., <persName ref=\"http:\/\/viaf.org\/viaf\/76321889\">Ronald Reagan<\/persName><\/code><\/li>\n<placeName><\/code>. If the place corresponds to somewhere\u00a0in the real world, put in a GeoNames<\/a> reference using ref=\"\"<\/code>, e.g., <placeName ref=\"http:\/\/www.geonames.org\/maps\/google_40.714_-74.006.html\"><\/code><\/li>\n<seg type=\"bodyPart\"><\/code><\/li>\n<rhyme><\/code>\u00a0and use the label attribute to indicate the rhyme scheme, e.g.\u00a0<rhyme label=\"a\"><\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\nPush the poem<\/h3>\n
push<\/code> the changes you have made to the repo using the GitHub Desktop client. You might want to create a different commit for each poem as you work.<\/p>\nReflect on the poems<\/h3>\n
\n
Grading<\/h2>\n