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

German Letter 2 #9

Closed RJP43 closed 5 years ago

RJP43 commented 5 years ago

Source Materials:

German_letter2 Folder MIWschema.rng

RJP43 commented 5 years ago

Information provided before class by @ProfPLC and Emily :

Transcriber/Translator: Tatjana
Translator Consultant: Sabine (reviewed in August, 2018)
Where the physical letter exists: Ernst Harthern Archives, Arbetarrörelsens Arkiv och Bibliotek (Swedish Labour Movement’s Archives and Library), Huddinge, Sweden
Photographed by: Pamela Caughie, August 2017 (camera settings attached)
camera settings from when images were photographed

Images prepared by: Matt Gallagher, Fall 2018
Lead Encoder: Zanabe with consultation from Rebecca and Tatjana , September 2018

RJP43 commented 5 years ago

@katebarrettmurphy please be in contact with @ProfPLC and I so we can catch you up.

RJP43 commented 5 years ago

@ProfPLC @katebarrettmurphy After associating the schema there is one error. The error indicates a missing key attribute value for Herta Keller in the salutation Dear Friend. <persName key="?">Freundin</persName>. I have uploaded the schema associated XML.

RJP43 commented 5 years ago
ProfPLC commented 5 years ago

I found a placeName that isn't marked as such: <p>Dresden. I also found two persNames, only one with an ID: 'your dear husband, Lilimoe and his brother.'

RJP43 commented 5 years ago

Hi @ProfPLC and @katebarrettmurphy! 👋

For the next assignment, our team will need to reference the latest file added to the German Letter 2 Archival Materials Folder 📂 -- a screenshot of the TEI header information provided by the project manager, Emily Datskou. As a team, we will work together to create a <teiHeader> element for German Letter 2 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 our text's folder linked above ⬆️)

@katebarrettmurphy be sure to reference the TEI Header Exercise in order to let us know what tasks you 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! 💻 😃

RJP43 commented 5 years ago

@katebarrettmurphy I am in Damen near the cafeteria. Where are you?

katebarrettmurphy commented 5 years ago

on my way

Get Outlook for iOShttps://aka.ms/o0ukef

From: Rebecca Parker notifications@github.com Sent: Tuesday, February 26, 2019 9:14:15 AM To: RJP43/LiliElbe_EngagedLearners Cc: Barrett-Murphy, Kate; Mention Subject: Re: [RJP43/LiliElbe_EngagedLearners] German Letter 2 (#9)

@katebarretmurphy I am in Damen near the cafeteria. Where are you?

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

katebarrettmurphy commented 5 years ago

When you click on the error you notice a question mark as a key, which we can't have because it's not specifying the persons identity.

RJP43 commented 5 years ago

@ProfPLC just leaving notes to reflect on @katebarrettmurphy and my in-person meeting:

In our meeting, I was able to show Kate how to download a file from GitHub, associate a schema and report on validation errors, upload a file to GitHub, and edit the XML. For the TEI Header assignment, Kate downloaded the TEI header template from GitHub and started changing the commented out information to reflect the information presented in the header spreadsheet provided by Emily.

Next steps will be finishing those <respStmts> and adding descriptive text to the header's <sourceDesc> element detailing the physical state of the letter or at least what can be observed from the facsimile image and uploading the completed TEI Header XML to GitHub.

Finally to complete the final task of the assignment, Kate will need to comment on this issue one element from the TEI Header section of the TEI Guidelines that we are not using in the project's template. @katebarrettmurphy once you leave your comment I will respond. I will post my example below for you to respond to since that is the second part of the final task on the exercise.

See you both in class! 👍

RJP43 commented 5 years ago

TEI Header Exercise Task # 4 - TEI Header Element Discussion

One element I observed in the TEI header section of the TEI guidelines that I do not see being used in the project's template is the <calendarDesc> element. According to the guidelines, the <calendarDesc> element "contains a description of the calendar system used in any dating expression found in the text." While I do think this element could be useful to incorporate into the TEI header, the project seems to use the date element around wordy-descriptions of dates instead of numerical representations it doesn't seem to be a necessary clarification (for example: <date>August to December, 2018</date>). I guess one argument against this would be since the project incorporates many languages where the date is written numerically different than how a date is typically written in American-English it might actually be a clarification worth making. @katebarrettmurphy and @ProfPLC let me know your thoughts and I look forward to responding to Kate's observation of a tei header element not being used in the template.

ProfPLC commented 5 years ago

?Given the different ways of dating material in different languages, this might be a useful element. We've been writing out the dates because in English we would write 02-03-19 for February 3, 2019 whereas in German and Danish it would be written 03-02-19 (which we would read as March 2). If the calendar element would standardize dates, that could be useful; if, however, it allowed us to use both dating systems above, that might create more confusion. I'd like to look at it.

RJP43 commented 5 years ago

Thanks @ProfPLC. @katebarrettmurphy I hope my statement and Dr. Caughie's response help you understand our expectations for task # 4 of the assignment.

katebarrettmurphy commented 5 years ago

i can’t find the spreadsheet

RJP43 commented 5 years ago

@katebarrettmurphy if you mean the spreadsheet screenshot with the TEI header information it is available in our team's folder. Here is a quick link to the file.

katebarrettmurphy commented 5 years ago

Revision Description is non-existent in the German letter 2 file. Revision Description is a summary of the file's history. I think this might be beneficial for the document to have because it would have everything all together in one spot making it easier to find everything.

katebarrettmurphy commented 5 years ago

@RJP43 @ProfPLC I think writing the months in the form of words (January, February, March...) has less of a chance for misunderstanding than writing months in the form of numbers (01, 02, 03...). Numbers can be left for specific dates and the year.

RJP43 commented 5 years ago

@katebarrettmurphy Thank you for your consideration of the revision description element. I agree it might be a useful element to look into; however, our series of resp statements are giving the information that a revision history in the revision description would also give. Luckily when we transform the XML we can grab all the resp statements and form them into a single paragraph so that might be an important consideration especially if the preferred, general consensus is a single paragraph reading of the information versus a different format like a list.

Well done completing this assignment. 🎉