search

RJP43 / LiliElbe_EngagedLearners

Lili Elbe Digital Archive practicum - learning markup via an engaged markdown community. Visit our wiki!
http://bit.ly/ELEarners
27 stars 26 forks source link

Danish Letter 19310615 #21

Closed RJP43 closed 5 years ago

RJP43 commented 5 years ago

Source Materials:

19310615 Folder
MIWschema.rng

RJP43 commented 5 years ago

@elenipamboukis in response to your email and as the assignment states you will download the schema from the link above and the XML file from the above linked documents folder. You should be able to tell which file is the XML by the file extension. The images and word doc file are just there for your reference as you try to navigate the XML and determine how the project has specialized certain elements to represent specific aspects of the letter (those aspects perhaps more easily seen in the images and/or word document).

alicapati commented 5 years ago

@elenipamboukis @skarrow After associating the MIW schema with the Danish letter, I used the validation shortcut to quickly find where the issue in the text was. It highlighted the element <persName key="wegnerS">. I decided to use the search function to see where else Wegener was used in the key. I noticed that this element was different from the others because the person coding the text had misspelled "Wegener." The correct way to tag the text would have been <persName key="wegenerS">. I tested this by simply adding an extra E, which validated the entire document (I took it out before uploading the text to the repository though).

elenipamboukis commented 5 years ago

2 different elements used in the XML- 1.) Element: <title> is very important because it confirms what the rest of the letter is about. For example, the title of #21 is "Letter to Ernst Ludwig Harthern." This confirms who the letter is to, and the body of the letter can explain why. 2.) Element: <date when="2017-11-20">20 November 2017</date> Dates are extremely important when coding Man Into Women because they create a timeline. Timelines give us a clue to what happened and when.

It is important for the project to know these names and identify those people/ places across different texts like German, Danish, and English.

elenipamboukis commented 5 years ago

@skarrow @alicapati List of people/ tags in the XML:

Places:

I have seen these different element names within the .xml file and found that Mor is supposed to be Mo'r from the prosopography keys and that Sigurd Wegener Thomsen is fine capitalized because it is still just a name.

edit: Professor Parker- I added spaces in between the elements so you could see what I was getting at (in class: fixed. learned that putting ticks helps)

skarrow commented 5 years ago

Key People in the text according to the XML mark up are

I was unsure of how to run the short cut in order to find the error... so I do not have that part of the assignment done.

2 other elements I noticed in the XML were is the <sourceDecs> which is important for understanding where the document comes from. It's a note at the top of the page that illustrates where the document came from.

Another element I found important and noticed was the <p style=>. This is an important element because it lets the reader know where in the letter you are. For example, in our letter an example of a paragraph style is the salutation, which lets the reader know it's where the letter is starting and what kinds of words and phrases to expect.

alicapati commented 5 years ago

One element I noticed is is <note type="translator">. This element is essential, especially for this project, because it allows people to understand what the document is trying to say. For people who do not know how to read German, Danish, or English, they will be able to follow along with what the author of the document is saying. If these documents were published, people who were navigating the site would be able to quickly search this tag and find the English translation.

Another element I noticed was <p style="salutation">. This element is important is because it helps readers and other contributors on the project figure out where the letters begin. There are different letters in this one document, and it's important for people to be able to distinguish where one letter stops (<p style="valedictorian">)and another begins.

alicapati commented 5 years ago

People mentioned:

Places mentioned:

RJP43 commented 5 years ago

@alicapati, @skarrow, @elenipamboukis well done completing the TEI XML Exercise! :tada:

For the next assignment, your team will need to reference the latest file added to the Danish Letter 19310615 Archival Materials Folder 📂 -- a screenshot of the TEI header information provided by the project manager, Emily Datskou. As a team, you will work together to create a <teiHeader> element for Danish Letter 19310615 using the information provided by Emily, the existing XML encoding, photograph(s) of the letter (a.k.a the facsimile images), and the translation/transcription documents.
(⬆️ all available in your text's folder linked above ⬆️)

Be sure to reference the TEI Header Exercise in order to let each other, @ProfPLC, and I know what tasks you each are comfortable with completing by Tuesday (2/26) 📆. Please remember the main goals in all of our assignments are team communication 💬 and collaboration 👐.

_Note: the TEI header template is available in Thursday's lesson on Capturing Metadata and as a download-able XML file containing the template <teiHeader>._ Happy coding! 💻 😃

skarrow commented 5 years ago

Some TEI elements to start putting together Letter to <persName key="">Ernst Ludwig Harthern Jacobson</persName> `

Sigmund Wegener Thomsen 
        </author> `

`

Translation completed 20 November 2017 by 
          <persName>Kristin Jacobsen</persName> <persName>Maiken Boysen</persname>
        </respStmt>`
ProfPLC commented 5 years ago

It's "Jacobson" with an "o."

From: skarrow notifications@github.com Sent: Monday, February 25, 2019 6:58 PM To: RJP43/LiliElbe_EngagedLearners Cc: Caughie, Pamela; Mention Subject: Re: [RJP43/LiliElbe_EngagedLearners] Danish Letter 19310615 (#21)

Some TEI elements to start putting together Letter to Ernst Ludwig Harthern Jacobsen

Sigmund Wegener Thomsen

' Translation completed 20 November 2017 by Kristin Jacobsen Maiken Boysen '

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/RJP43/LiliElbe_EngagedLearners/issues/21#issuecomment-467248212, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AtJRgbojBfIO4bx9A7VL1pSYMPkNfi1Sks5vRIbGgaJpZM4a8wFv.

alicapati commented 5 years ago

hey friends! ☺️ @elenipamboukis @skarrow

`

XML transformed into HTML on by 
           <persName ref="rjp">Rebecca J. Parker</persName>
        </respStmt>
HTML proofing completed from to , by ` _- For this part of the header, I was unsure what to put for the "exact transformation date" and "HTML proofing completed from..." If either of you know where I can find this information, please let me know!_ _- If you could look at the images of the physical text in the folder and make note of anything you see, please let me know so I can add them to the header!_ ******************************************************** **Some TEI Elements to put together:** ```` Letter to <persName key="">Ernst Ludwig Harthern</persName> Sigurd Wegener Thomsen Photographed August 16-17, 2017 by Pamela L. Caughie Images prepared from November 2017 by Matthew Gallagher Transcription completed from 20 November 2017 by Kristin Jacobson Translation completed from 20 November 2017 by Kristin Jacobsen Translation reviewed in July to September, November, 2018 by Marianne Ølholm, Maiken Boysen Encoding completed from October to December, 2018 by Taylor Brown Encoding assistance and/or XML proofing completed by Rebecca J. Parker Nikolaus Wasmoen/persName> Assigned Spring 2019 Engaged Learner(s) Aliana Capati Sophie Karrow Eleni Pamboukis XML transformed into HTML on by Rebecca J. Parker HTML proofing completed from to , by Loyola University Chicago Loyola's Center for Textual Studies and Digital Humanities Danish Arts Foundation Lili Elbe Digital Archive Chicago, IL, USA July 6th, 2019

Reproduced by courtesy of the Ernst Harthern Archives, Arbetarrörelsens Arkiv och Bibliotek (Swedish Labour Movement's Archives and Library) in Huddinge, Sweden

Distributed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International licence.

AC: Page numbers are written in the center of the top of the page. Dates are written with the day as the first number and the month as the second.

Some text here.
alicapati commented 5 years ago

@skarrow @elenipamboukis I uploaded the TEI header into our folder, the only 2 things I didn't fill in were the two elements I mentioned above.

skarrow commented 5 years ago

One TEI header element that is missing from ours is <encodingDesc> This element describes the relationship between a document and its sources. It tell us whether or not a text was normalized in transcription, how ambiguities were labeled or resolved, etc. It provides extra information about the document itself and the process in which it was encoded.

This would add to our letter because there nothing sepecific mentioned about the source or sources of the electronic document, or about the levels or processes that were made in the encoding process.

skarrow commented 5 years ago

Today in class during team time... @alicapati made revisions to the document as @RJP43 went over our document in class @skarrow will go through and add to the keys of the persName elements in the TEI header

@alicapati @elenipamboukis @skarrow --> all three of us commented on a missing TEI element and responded to each others comments

elenipamboukis commented 5 years ago

https://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html I am choosing "fileDesc"- 1.) a file description, tagged fileDesc, containing a full bibliographical description of the computer file itself, from which a user of the text could derive a proper bibliographic citation, or which a librarian or archivist could use in creating a catalogue entry recording its presence within a library or archive. The term computer file here is to be understood as referring to the whole entity or document described by the header, even when this is stored in several distinct operating system files. The file description also includes information about the source or sources from which the electronic document was derived. The TEI elements used to encode the file description are described in section 2.2 The File Description below.

In our project here is where "fileDesc" is used: <fileDesc>

Letter to <persName key="harthernE">Ernst Ludwig Harthern Jacobsen</persName> Sigurd Wegener Thomsen Translation completed on 20 November 2017 Kristin Jacobsen Maiken Boysen Marianne Encoding updated on 18.11.26 Taylor Brown 
        <publicationStmt> <p style="letter header"><persName key="wegenerS">SIGURD WEGENER THOMSEN</persName>
            STUD. MED. GENTOFTEGADE 14. <placeName key="gentofter">GENTOFTE</placeName></p>            
            </publicationStmt>
        <sourceDesc><!-- This is a general note at the top of the page that describes where the source document is from. I added 
        the translator's note element though I'm not sure who actually wrote the note. -->
            <p><note type="translator">Letter is in the <persName key="harthernE">Harthern</persName> Archives. Note:
                All items in brackets were written by <persName key="wegenerS">Sigurd Wegener
                    Thomsen</persName> and are not translator insertions. <persName
                        key="wegenerS">Sigurd</persName> seems to have written in haste, leading to a number of mistakes, missing words, or incomplete sentences, which are noted when practical. The original letter includes notations and underlining in red and sometimes black, which most likely were added by <persName key="harthernE">Harthern</persName>.</note></p>
        </sourceDesc>
    `</fileDesc>`

File desc is incredibly important because it gives the document a proper citation, and describes who wrote the document, when it was written, and I think is incredibly essential. Without this part in the TEI header, the questions - "Where did this come from? Why is it important?" will arise. There is no question that it shouldn't be included within the TEI header.

skarrow commented 5 years ago

@RJP43 I couldn't find a key id for Harthern for our letter

alicapati commented 5 years ago

When reading the TEI Header article, one element that was mentioned was the <revisionDesc> which allows various editors to write an account of things that they may have changed, tweaked, etc. in the document since it was last opened. Although I know that comments may serve a similar effect, I think it would be nice to have a place in which various editors could write about the changes they have made. It could serve as a paper trail that future coders could refer back to when working on the document.

elenipamboukis commented 5 years ago

One TEI header element that is missing from ours is <encodingDesc> This element describes the relationship between a document and its sources. It tell us whether or not a text was normalized in transcription, how ambiguities were labeled or resolved, etc. It provides extra information about the document itself and the process in which it was encoded.

This would add to our letter because there nothing sepecific mentioned about the source or sources of the electronic document, or about the levels or processes that were made in the encoding process.

@skarrow I think that this is important to add within our TEI header because it can give us insight to the information within the TEI header that has been labelled or transcribed. It tells us why the decisions were things made- the motive behind them. Without it, I feel like the reader can just assume- but even that causes 'wrongs' and 'errors.'

skarrow commented 5 years ago

@elenipamboukis I agree that the <filedesc> is an important TEI element. Because even though we have all that information in our current TEI element, it is standing alone, and the <filedesc> element can be used to link all the elements together

skarrow commented 5 years ago

@RJP43 there is also no key ID for Sigurd Wegener Thomsen in the spreadsheet

elenipamboukis commented 5 years ago

When reading the TEI Header article, one element that was mentioned was the <revisionDesc> which allows various editors to write an account of things that they may have changed, tweaked, etc. in the document since it was last opened. Although I know that comments may serve a similar effect, I think it would be nice to have a place in which various editors could write about the changes they have made. It could serve as a paper trail that future coders could refer back to when working on the document.

@alicapati I agree with you that this is essential for the document because without a proper history of changes, there would be no responsibility for wrongs and there wouldn't be an account of who made what changes and why. There HAS to be notes of who made what changes and why so that the reader can understand the connections. If it weren't there I believe that the reader wouldn't know what was changed.

alicapati commented 5 years ago

https://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html I am choosing "fileDesc"- 1.) a file description, tagged fileDesc, containing a full bibliographical description of the computer file itself, from which a user of the text could derive a proper bibliographic citation, or which a librarian or archivist could use in creating a catalogue entry recording its presence within a library or archive. The term computer file here is to be understood as referring to the whole entity or document described by the header, even when this is stored in several distinct operating system files. The file description also includes information about the source or sources from which the electronic document was derived. The TEI elements used to encode the file description are described in section 2.2 The File Description below.

In our project here is where "fileDesc" is used: <fileDesc>

Letter to Ernst Ludwig Harthern Jacobsen

Sigurd Wegener Thomsen

Translation completed on 20 November 2017 Kristin Jacobsen Maiken Boysen Marianne

Encoding updated on 18.11.26 Taylor Brown

SIGURD WEGENER THOMSEN STUD. MED. GENTOFTEGADE 14. GENTOFTE

Letter is in the Harthern Archives. Note: All items in brackets were written by Sigurd Wegener Thomsen and are not translator insertions. Sigurd seems to have written in haste, leading to a number of mistakes, missing words, or incomplete sentences, which are noted when practical. The original letter includes notations and underlining in red and sometimes black, which most likely were added by Harthern.

</fileDesc> File desc is incredibly important because it gives the document a proper citation, and describes who wrote the document, when it was written, and I think is incredibly essential. Without this part in the TEI header, the questions - "Where did this come from? Why is it important?" will arise. There is no question that it shouldn't be included within the TEI header.

@elenipamboukis I like the fact that you addressed the importance of having <fileDesc> in the TEI header. Without having this, it would be difficult for those who are navigating the article to find where the author, date, publication, etc. of the text is located. Having this element keeps all the pertinent information of the origin of the text in one place instead of forcing individuals to scroll through a long form of text.

skarrow commented 5 years ago

@alicapati I agree that the <revisionDocs> element would be nice to add to our letter. It would explicitly tell us any additional revisions that have been made to the document. This would be better than having to hunt through the document for possible revisions, or not being aware of revisions in general.

elenipamboukis commented 5 years ago

Observation: In looking at images 1-10, I noticed that it is handwriting written in black cursive ink with some red crayon lines drawn on the sides of some of the writing.

alicapati commented 5 years ago

One TEI header element that is missing from ours is <encodingDesc> This element describes the relationship between a document and its sources. It tell us whether or not a text was normalized in transcription, how ambiguities were labeled or resolved, etc. It provides extra information about the document itself and the process in which it was encoded.

This would add to our letter because there nothing sepecific mentioned about the source or sources of the electronic document, or about the levels or processes that were made in the encoding process.

@skarrow I like the fact that you called attention to the importance of this element. I think this would be a good way for other encoders to know where their information is coming from. In this case, this letter was originally a written document, then was translated and transcribed, then coded. Having this element would allow coders to document any changes that were made between the original written document and the text. This could be a place in which the encoder could write about the letter and what its purpose was, and how it relates to the greater project.

alicapati commented 5 years ago

@elenipamboukis @skarrow and I completed our tasks during the 20 minutes of Team Time in class. 🎆 🎉 🎈

RJP43 commented 5 years ago

@elenipamboukis @skarrow @alicapati Fantastic conversation here regarding your statements and suggestions for possible elements to include in our TEI Header. For the revision description element since our project has utilized version control software (at the root of GitHub and Gitlab - the two online repository spaces our project uses) we might consider writing up a statement for each file looking at the exact changes made across each file as recorded by the Git software. In creating the TEI Header the project editors have gone for a more simplistic feel giving just the essentials, but as we continue to grow the template we might want to consider how summary statements in elements like <revisionDesc> could be valuable to include. Thank you all for your thoughtful considerations. 🎉