Closed RJP43 closed 5 years ago
I'd be okay with doing the second task, with the encoding and transcribing!
I find interesting both tasks, but I would rather join @kklimek1 in transcribing and encoding--it would be a great way to refresh my French. Whenever you will see this, let me know, @kklimek1 , @schola0208 and @elenipamboukis, if is OK with you.
:eyes: @bcristiana be careful not to close your team's issue when commenting. Please click the green comment button to post your responses. Thanks :+1:
❗️ ❣️ hey team @schola0208, @bcristiana, @kklimek1, @elenipamboukis
Just popping in to let you know @ProfPLC had me add Anne's translation to your project team's folder. Here is the quick link to the PDF - H l ne Allatini Il et Elle He and She from Mosa ques 1939.pdf
@bcristiana that is okay with me! Hey team, I would prefer to work on the first task!
@bcristiana @elenipamboukis @kklimek1 I'm happy either way. I would do whatever task is left on the list
Dear Allatini team, The translation by Dr. Anne Callahan that Rebecca sent you in a previous comment is a revision of the translation that was encoded last semester. So those on task 1 will need to revise the translation, re-encoding where necessary before associating the schema. This is work you must do first. Rebecca and I can meet with you to go over this task.
Class March 19- @schola0208 and I are doing assignment 1, we will meet together and separate our work @bcristiana and @kklimek1 are doing assignment 2, Christiana is doing first half of pictures and Kat is doing that second half
@RJP43 Schola and I found that this error: key="madrid">Madrid</placeName>
is not valid. We looked Madrid up in the prosopography and the key does not exist as a location name.
@elenipamboukis I will add it to the prosopography. Thanks! 👍 Please leave the encoding in the XML file and when the next schema release goes out in a few days the error will disappear.
Today March 21 from 11:00-1:00, Eleni & Schola: Meet together updating translation by reading aloud together and comparing it, From line 1-500 in the XML and page 124-142 in the updated translation.
@RJP43 Hi Rebecca! I'm attempting to encode my half of the pictures, but I've hit a snag. The pages all have "Mosaiques" at the top of the page, and I'm not sure how to incorportate that into the XML file. Would I be encoding that as <pb style="heading" rend="___"/>
? Thanks!
:eyes: @kklimek1 Huzzah, you are correct. 🎉 Well done finding the correct encoding in the guidelines. Now for the rend
attribute value paste the exact transcription/translation of that heading text. So your encoding for those should look like this:
<pb style="heading" rend="Mosaïques"/>
👍
@RJP43 , good evening! I tried to send you my two Mozaiques
, 10 and 11, and wonder if you've been able to open them. I don't know how otherwise to show you my work without uploading it. Do you have any time tomorrow, after 12.30? You could see what I've done and tell me if I am on the correct path.
:eyes: @bcristiana You will need to upload your materials to GitHub not only so I can see your progress but so your teammates can too. We can schedule a meeting for Monday or Tuesday to go over how to upload and to check your progress if you like. Unfortunately, I do not have any availability today to meet. 📆 For Monday, I am open Monday before 11 AM or between noon and 2 PM. For Tuesday, I can meet anytime before the Engaged Learning class at 2:30 PM. Please let me know when works best for you. 💟
@RJP43 Would you mind meeting with me around 1:00 on Tuesday? Similarly to @bcristiana I want to make sure that I'm doing everything correctly!
:eyes: Sure thing @kklimek1! I have you on my schedule for 1 PM on Tuesday (3/26) in IC Study Room 217.
@RJP43 , could you meet me Monday? My class starts at 11 am.
:eyes: @bcristiana Monday is fine. Do you want to meet before your 11 AM class or after? If after, what time in my noon to two slot works best for you?
@RJP43 , thank you. The class ends at 12.40, so I could come see you whenever it is more convenient for you: either before 11 am or after 12.40 pm.
@RJP43 , if Monday is still fine, where do I meet you and when?
:eyes: @bcristiana let's meet at 12:45ish in IC Study Room 214. 📆 I have added you to my office hours schedule. I have reserved 214 for the majority of the afternoon if others also need to meet.
@RJP43 , thank you. I will be seeing you Monday.
@RJP43 Schola and I just finished comparing the two translations and fixing what was missing/ incorrect in the XML. We found some things that didn't necessarily make sense when we were correcting the XML. For example, the XML on line 833 said, "like all or almost all operations," which made sense to us rather than the corrected text which says on page 137, "like almost all or almost all operations." We are just a bit confused, because that wasn't the first example of something that didn't make a lot of sense. I have a list of notes on my phone of other examples.
Also- are we still waiting on the new schema to move onto the next task? The next task for us would be to correct the XML errors.
:eyes: @elenipamboukis please update your file by uploading your latest XML to your team's folder over top of the old XML so I can better understand where you are in the process of completing your team's tasks. I have recently updated the prosop. and schema to include the missing Madrid key and the most recent file in your folder suggests you have already associated the new schema to the XML prior to making the corrections.
@RJP43 and team, I gladly let you know that I uploaded my contribution to the task. There are still two pages--the title page and the cover of the memoir--that I didn't upload: the first, because it has to precede one of @kklimek1 's pages, and the latter, because I need suggestions about how to encode it.
@RJP43 , thank you for your help! I was so relieved to finish this part of the project, that I forgot to state the obvious: your help. So thank you again!
@RJP43 Thank you for meeting with me! As I was encoding, I stumbled upon "Marcus Hierschfeld" in the text, but in the prosopography there was only <persName>Magnus Hirschfeld</persName>
.
:eyes: @kklimek1 This is one where I wonder if this is a spelling error on Allatini's part. Is there any information in the surrounding text indicating Marcus is of relation to Magnus or does it seem Allatini is actually talking about Magnus? Might be worthwhile to pose the question to @ProfPLC before/after class: Does Magnus have a brother Marcus? Is Marcus an alternate name for Magnus?
Please report back. If it is a spelling error on Allatini's part I can give you the encoding to indicate this, but if it turns out this is a separate person all together I will add him to the prosopography. 👍 Thanks!
:eyes: @kklimek1 @ProfPLC Also we will want to take note of the different spellings of the last name. Is this just how the French would write Hirschfeld or is this an even bigger indicator that Allatini botched Magnus Hirschfeld's name?
Marcus is a mistake, this is Magnus Hirschfeld and should be encoded as such. Do you know if Marcus is in the original? I believe it's Allatini's mistake but we want to make sure it's not the translator's.
@RJP43 Schola and I have updated our XML document with your new schema, and have corrected all errors in the document besides the Frauenkilink place key because we do not know which of they four keys in the pros. to use for it.
Today in class @bcristiana and I realized that there was a little bit of a miscommunication. We ended up having some overlap in the facsimile images that we transcribed and encoded. So while I finish up the images 28 through 41, Cristiana will finish images 5 through 9. Once we both finish up, I'll be taking both of our XML documents and turning them into one file.
@RJP43 Schola and I have updated our XML document with your new schema, and have corrected all errors in the document besides the Frauenkilink place key because we do not know which of they four keys in the pros. to use for it.
@RJP43 , we figured out the Frauenkilink key, with the help of @ProfPLC , and we figured out the translation issues with her as well. @elenipamboukis is uploading the new corrected xml file. I'm adding the transformation ready tag
@RJP43 I'm still a little confused on how I do the persName element around certain people in the document. For example Professor W., in the prosopography, this is what I'm looking at: <person xml:id="warnekros" source="historical" synch="#kreutz">
<persName>Kurt Warnekros</persName>
<persName>Warnekros</persName>
<persName>Professor Warnekros</persName>
<persName>Professor W</persName>
<persName source="#frenchSupp">Professeur W</persName>
<note/>
</person>
Do I use this whole fragement? Or do I just put a <persName>
element without any key=
? Thank you!
@RJP43 I'm still a little confused on how I do the persName element around certain people in the document. For example Professor W., in the prosopography, this is what I'm looking at:
<person xml:id="warnekros" source="historical" synch="#kreutz">
<persName>Kurt Warnekros</persName>
<persName>Warnekros</persName>
<persName>Professor Warnekros</persName>
<persName>Professor W</persName>
<persName source="#frenchSupp">Professeur W</persName>
<note/>
</person>
Do I use this whole fragement? Or do I just put a<persName>
element without anykey=
? Thank you!
Actually I think I figured it out, would it look like this: <persName key="warnekros">professeur W.<persName/>
?
:eyes: @kklimek1 you got it!
Hi, @kklimek1, team and @RJP43 , I finished encoding the facsimiles 5-9 and added them to the final Mozaiques_bc.xml, as well as the comments about facsimiles 1 and 2. Now I need to remember how to upload the final version of the Mozaiques_bc.xml.
@RJP43 , I tried to remind you about Lili's French IDs and I am certain that I have attached the help wanted
label to the wrong thing, so that there is a new issue
assigned to you and, somehow, to myself (had I known how to attach emojis, I would have put something here).
@bcristiana 👀 🎉 thank you so much for creating a new issue for the couple of specialized items you need help with I will go ahead and answer you on that issue - #37. Seriously, well done with the label and everything - that is a perfect example of what to do! 💟
As for getting your file into your team folder (so @kklimek1 can reference it and the two of you can move forward with combining your two encoding styles) I have just tagged the class in a comment about proper GitHub workflow (including upload/download habits) on issue #35. I hope that walk-through helps. Please let us know if you succeed in uploading so we can celebrate :tada: OR let us know if you still need help sharing your file so we can 📆 schedule a meeting during my office hours or have you meet with your partner(s) that are confident in their upload abilities before/after/in class. 🤝
Though by the looks of your commit history - https://github.com/RJP43/LiliElbe_EngagedLearners/commits?author=bcristiana - it seems you were able to upload - 🎉 ❓
@kklimek1 , hi! Just wanted to let you know that I uploaded the revised version of Mozaiques_bc.xml, this time with new info added to the TEI header, as provided by the TEI header spreadsheet. Please let me know if you find it, because I cannot see it, though the uploading seems to have been successful. It is the file that contains the title page and pages 201-223, as well as the comments about the physical condition of each facsimile. @RJP43 , thank you for the explanations, I tried to follow them as best as I could. We will see if Katy can retrieve it. Honestly, I can't wait to share into whatever the celebratory emoji is about.
Sorry for the late comment, but the combined document has been uploaded (and then reuploaded because I missed a little part of the text) !
Hey there @schola0208, @bcristiana, @kklimek1, and @elenipamboukis 👋 I have reserved IC Study Room 217 for our 10 AM meeting on Friday. See you all there!
After meeting with Rebecca at 10:00 in a study room, @kklimek1 will be uploading the new combination file onto the Allatini Chapter file, and @bcristiana will update the new TEI header.
@kklimek1 will be doing place name attributes and I will be doing person name attributes both of us making sure the French matches the English attributes. @bcristiana and @schola0208 will be doing the segments in the paragraphs.
@RJP43 Should we be putting persName elements around pronouns and nouns that indirectly refer to the person? So if Einar is referred to as "my fiance"?
:eyes: @kklimek1 and @elenipamboukis -- Pronouns do not get persName elements. If you can identify the reference, such as "my fiance," from context, then put the persName element in with the appropriate key ID. But if you're not sure of the reference, run these by me via email (pcaughi@luc.edu). For example, a reference to my fiance by Gerda could be Einar but also Fernando Porta. I could help identify which one.
@RJP43 , hi, this is a message from both me and @schola0208 . This is the problem we ran into: the french text has paragraph 4 and 5 separate, while the translation has them combined into one. We thought to use different segment numbers to mark the differences btw paragraphs, but that would mean we have two segments in one paragraph in the english transaltion. @schola0208 is pasting what it looks like in the next comment. So is it ok to have two segments in one paragraph, or is there another way to segment it when paragraph divisions don't match?
`
`
Rome.
`Upon my return, five months later, we took up again our friendly relations that became more and more cordial and affectionate. I had just lost my mother and was expectingmy first child . My Scandinavian friends embraced me and I found great comfort in their affection on days when, without news of myhusband , they increased their attention and tried to distract me as best as they could, to turn my thoughts away from my anxiety.
:eyes: @schola0208 @bcristiana I think this is an instance where you need to instead divided the translation and original paragraphing so they match the original print rendition. If there are two paragraphs in the facsimile images then both the translation and the original French need to be divided according to the print. I believe that will also solve the <seg>
issue but please comment back and let me know if not. Thanks 👍
hey there @schola0208, @bcristiana, @kklimek1, and @elenipamboukis 👋
Your team has been assigned the French-language Allatini chapter. As a team, you will create one file containing both the already-encoded translation and the to-be-encoded original transcription of this text. This text is rather unique so be sure to reach out via this issue if you hit any snags. Simply tag me - @RJP43 - and add the "help wanted" label to this issue.
If I do not respond within 48 hours with my 👀 reaction then please shoot me an email at
rparker3 (at) luc (dot) edu
and I will be in contact ASAP.Two of you should begin by associating the new project schema to the encoded-translation XML file: AllatiniChapter.xml. Then you will need to correct the XML errors (in the entire file - including errors found in the
<tei:header>
elements). After you have uploaded the valid and well-formed XML file, tag me - @RJP43 - and add the "transformation ready" label to this issue. I will then use our project's XSLT (eXtensible Stylesheet Language Transformation) and will respond to your team here in this issue with an HTML proofing link. From there your team will work to HTML proof the HTML rendition of this text's translation -- reporting errors and design concerns regarding the HTML styling to me via this issue (tagging me and using the "help wanted" label) and, otherwise, revising the XML where improper encoding has resulted in faulty HTML rendering. As a reminder, you will use all of the materials in the Allatini Chapter folder (i.e. original transcriptions, facsimile images, etc.) to proof the HTML.The other two of you will work on transcribing and encoding (directly in oXygen) the original French of this text using the facsimile images. Once encoding is complete on the original French your team will consult our project's encoding guidelines and combine the two files into a single file named
HAllatiniChapter_combo.xml
. Then @ProfPLC and I will inform your project team of next tasks or that your project contribution (well... at least this more "technical" aspect of it) is complete. Please note the project and the training materials available on this repository are still in flux. This means that there might be moments where I need to inform your team of new updates that will require XML corrections or re-reading of lesson materials; therefore, please check this issue and the general issues board regularly for alerts from me.Recent Update: We have moved away from using the MIWSchema.rng, and are now using our new schema - LEDA_ODD.rng. Please be sure you download this new schema and delete the old one from your computers. We also now have a much more robust prosopography file listing all of the identified people and places in our project files. Please reference our LEDA_Prosopography.xml when trying to identify proper key attribute values. Every xml:id attribute value in the file is a possible key attribute value that can be used in your XML files. We will be outputting an HTML transformation of this prosopography file soon and when we do I will be sure to inform your team via this issue.