Sanheden article ready for transformation

The Sanheden article is ready. I missed the class where you talked about proofing HTML. I signed up for a Hypothes.is account, but I'm not sure what I need to do next. From reading the lesson for Feb. 28, it looks like I need an HTML Proofing URL. Do I get that from you or Dr. Caughie? Thanks for your help!

Technical Issues - How to post an issue!

As explained in class on Thursday (2/28), please bring any technical questions/concerns to the issues board. We ask you to tag the entire class just in case someone in the class is able to respond quicker than Rebecca. To create a new issue navigate to the Issues Board and click on the green "New issue" button in the top-right corner.

From there, give your issue a short but descriptive title (e.g. Need Help Finding Prosopography Link) and in the box where it says "Leave a comment" provide a detailed explanation of the technical problem(s) you are having as well as any actions you have already taken in attempts to resolve the problem. Then copy from our tips for writing on the issues board the class handles and paste them into your comment. Like this:
@RJP43 @ProfPLC @zothman @Tatjanawj @JackieAlfarah @Dadelinee @katebarrettmurphy @bcristiana @ElleBromer @alicapati @joaquindavalosponce @Katiegriggs24 @schola0208 @skarrow @kklimek1 @ekupchella @amandallopez @amccann2 @BMiller10 @elenipamboukis @dpedz @wravindran @Samantha9899 @nroyce @kschoen3 @jsteele1 @tinatiehen @anais-turiello @bossa12 @kejcat
Finally, on the right side of your text under "Labels" select the "help wanted" label.

Then click the "Submit new issue" button.

Problem 4

Key: garlandM - Name: Maria Garland - No ID - Appears: 3 times
Key: Lili - Name: Lili Ilse Elvenes - ID lili - Appears: 3 times
Key: (ref) kj - Name: Kristin Jacobsen NO ID - Appears: 1 time
Key: (ref) mb - Name: Maiken Boysen NO ID - Appears: 1 time
Key: (ref) tnm - Name: Tyler Monaghan NO ID - Appears: 1 time
Key: NO KEY (?) - Name: Hr. Oberartz - NO ID - Appears: 1 time
Key: NO KEY (?) - Name: The chief physician - NO ID - Appears: 1 time

Sanheden article

Becca,
Do you have any time to meet tomorrow (Wed.)? I’m almost done with my coding, and I have a fair number of questions best handled in person.
Thank you!
Kristin

Lili Elbe to Maria Garland : Jackie, Katie, Wagme

hey there @JackieAlfarah @Katiegriggs24 @wravindran 👋

Your team has been assigned the Danish-language letters from Lili Elbe to Marie Garland. As a team you will need to associate the new project schema to each of these four letters:

Then you will need to correct the XML errors (in the entire file of each file - including errors found in the <tei:header> elements). 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.

After you have uploaded the valid and well-formed XML files in each of the letters' respective folders, 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 each of the four letters -- reporting errors and design concerns regarding the HTML styling to me via this issue (tagging me and again 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 each of the four letters' folders (i.e. original transcriptions, facsimile images, etc.) to proof the HTML.

Once each of the four letters has been proofed @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.

Danish Letter 19310616

Source Materials:

19310616 Folder
MIWschema.rng

Lili's IDs in Allatini

@RJP43 , hi! This is to remind you that, in Allatini chapter, Lili is consistently referred to as "Lily" and, at least once, as "Lily Wegener". Also, I need instructions about how to encode to manuscript's cover page. Hopefully, this is the right way to do it.

German Letter 1

Source Materials:

German_letter1 Folder
MIWschema.rng

Let's Discuss "Storm Clouds on the Horizon"

Each student should write in the discussion thread below 2 discussion questions after reading:

Pamela L. Caughie, Emily Datskou & Rebecca Parker (2018) “Storm clouds on the horizon: feminist ontologies and the problem of gender,” Feminist Modernist Studies, 1:3, 230-242, DOI: 10.1080/24692921.2018.1505819

In place of writing a second discussion question, students are permitted to respond in 3-4 sentences to another student's question. If you opt out of writing a second discussion question, you must mention the person whose question you are responding to (using the @ symbol followed by their GitHub handle - e.g. @RJP43) and reiterate their question in your response. We ask you to respect each others' pronouns when responding to one another (see our list of Engaged Learner handles and pronouns).

Because we are hosting this discussion on GitHub you should take note that your responses can be "marked up" using GitHub's markdown syntax. In addition to text styling (like bold, italics, and offsetting quoted text) made available via markdown, you are also able to attach files (images are particularly welcome) and insert emojis in your responses. Please use the GitHub Help Tutorial on basic writing and formatting syntax along with the emoji cheat sheet to assist in writing an engaged response.

Danish Letter 19241200

Source Materials:

19241200 Folder
MIWschema.rng

Danish Letter 19310131

Source Materials:

19310131 Folder
MIWschema.rng

Danish Letter 19310807

Source Materials:

19310807 Folder
MIWschema.rng

Danish Letter 19310818

Source Materials:

19310818 Folder
MIWschema.rng

Allatini chapter : Schola, Cristiana, Kat, Eleni

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.

Error message concerning phrase "en bog"

When I coded the title of the Sanheden article, I got an error message that said, "Attribute name "bog" associated with an element type "En" must be followed by the '=' character." CODING: <item rend="primary"><b><En bog om, hvordan <persName key="wegenerE">Hr. Wegener</persName> blev til <persName key="lili">Frøken Wegener.</persName></b></item>. How can I fix this? @kejcat

Lili Elbe to Poul Knudsen and T. C. Thomsen to Hoyer : Adeline

hey there @Dadelinee and @nroyce 👋

Your team has been assigned the Danish-language letters from Lili Elbe to Poul Knudsen and T. C. Thomsen to Hoyer. As a team you will need to associate the new project schema to each of these four letters:

Then you will need to correct the XML errors (in the entire file for each file - including errors found in the <tei:header> elements). 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.

After you have uploaded the valid and well-formed XML files in each of the letters' respective folders, 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 each of the four letters -- reporting errors and design concerns regarding the HTML styling to me via this issue (tagging me and again 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 each of the four letters' folders (i.e. original transcriptions, facsimile images, etc.) to proof the HTML.

Once each of the four letters has been proofed @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.

TEI Header, Prosopography, Schema, and Encoding Guidelines - UPDATES!

👀 @zothman @Tatjanawj @JackieAlfarah @Dadelinee @katebarrettmurphy @bcristiana @ElleBromer @alicapati @joaquindavalosponce @Katiegriggs24 @schola0208 @skarrow @kklimek1 @ekupchella @amandallopez @amccann2 @BMiller10 @elenipamboukis @dpedz @wravindran @Samantha9899 @nroyce @kschoen3 @jsteele1 @tinatiehen @anais-turiello @bossa12 @kejcat 👀

Hello Everyone! 👋 This issue has all of the quick links to the files necessary for encoding and proofing!

`<teiHeader>` Template Update

I wanted to remind all of you that one part of the task "proofing XML" will be making sure the <teiHeader> elements in your XML files match our <teiHeader> template. **Please note I have recently updated the <teiHeader> template (and the teiHeader Lesson); therefore, all of the headers in all of the XML files will need to be adjusted. In particular, the wording for every <respStmt> has changed and these changes need to be reflected in all LEDA XML files.

There are two ways to go about doing this. Either copy the new template <teiHeader> and fill in the information fresh from the teiHeader information spreadsheet (linked below) or adjust the existing <teiHeader> element in your XML file(s) according to the changes made to the template. The <teiHeader> information must be corrected and matching the template before HTML transformation.

Danish Letter 19310122

Source Materials:

19310122 Folder
MIWschema.rng

Proofing HTML - UPDATES!

Hello HTML Proofers 👋 @JackieAlfarah @Dadelinee @bcristiana @alicapati @Katiegriggs24 @schola0208 @skarrow @kklimek1 @elenipamboukis @dpedz @wravindran @Samantha9899

For those that have marked and confirmed their documents are "transformation ready" I have now transformed your XML into HTML. You can locate all of the HTML versions of transformation ready XML in each of the different language archives.
Danish HTML Proofing Views = Main Repo > ProjectDocs >archivalMaterials > Danish_archive > HTML_ProofingViews
German HTML Proofing Views = Main Repo > ProjectDocs >archivalMaterials > German_archive > HTML_ProofingViews
French HTML Proofing Views = Main Repo > ProjectDocs >archivalMaterials > French_archive > HTML_ProofingViews

I have decided to group all of the HTML proofing views together because I do think it is important for anyone in the class to look over any of the HTML. Sometimes when working on a single document it is a bit more difficult to see mistakes that others first coming to a text will see right off the bat.

How to Proof HTML

Here is the step-by-step process of proofing HTML:

Preparing to Proof

Download HTML file to be proofed.
Have the XML of the transformed HTML open in oXygen.
Have the facsimile images of the original document ready to view.
Download proofView.css in the same folder/space you downloaded the HTML. The CSS must be in the same folder as the HTML in order for you to see the proofing styles.
Open the HTML file in oXygen and change the CSS link line to reflect the CSS is in the same folder as your HTML. Like this:

In the <head> element you will see this line: <link rel="stylesheet" href="../../proofView.css" />
Change the above line to <link rel="stylesheet" href="proofView.css" />

I have left this step in the process so I can know which files when reuploaded to GitHub have had some proofing even if not extensive, complete proofing.

Proofing HTML and Editing XML

I have decided to ditch the Hypothes.is method of proofing, for our class anyway, due to the difficulties of getting the HTML live online and this is why were are doing local proofing instead. Here are the steps to proofing locally:

The only file you need open in oXygen, at this point, is the XML. You will open the HTML in a browser. To open HTML in a browser you open the browser (Chrome, Firefox, etc.), hit CTRL (or Command on Mac) and the letter O. From there your file explorer (or Finder on Mac) will open and you can navigate to where you saved the HTML. Double click on the file to open.
In each HTML proofing view I have listed what the various color coding and text styles indicate. You should first look over the file to be sure all parts of the document are rendering in the HTML. For example: if your file has a postscript does it appear in the HTML.
The file used to transform the XML to HTML relies on the XML meeting the structural hierarchy indicated in the encoding guidelines and teiHeader template. Therefore if something is missing in the HTML it is likely miscoded in the XML. As you proof, you should correct the XML and re-upload the XML to GitHub as you make changes.
If there is something off in the HTML where you cannot find what needs changing in the XML come back to this issue and report what you see in the HTML so we have a list of problems spots as the archive moves closer to launch.

Please note besides changing the CSS link you will not make changes to the HTML. Once you have changed that CSS line I suggest you re-upload the HTML to GitHub and closeout of the HTML in oXygen.

PLEASE BE SURE TO UPLOAD THE XML, WITH YOUR PROOFING CHANGES, TO GITHUB. I will be taking the XML with your corrections and re-transforming it several more times during the final proofing stages of the archive.

If you are working on a team proofing HTML then you will need to determine with your group who will edit the XML when so as to avoid uploading your changes to the XML over your team-mates' changes. Anyone is able to proof any of the HTML. If you wish to proof HTML please let us know below which HTML file you are proofing so we do no get overlapping GitHub uploads.

Thank you all for your continued hard work on this project and it has been a pleasure working with you all! 💟

"Vice Versa" from Voilà : Jade, Ran, Danica, Elle

hey there @jsteele1, @bossa12, @dpedz, and @ElleBromer 👋

This issue was re-worked on April 6th to invite Elle on to this project team and to correct the transcription process. Please only continue working on transcriptions after re-reading this issue!

Your team has been assigned the French-language "Vice Versa" issues from Voilà. As a team, you will transcribe the original text from the facsimile images for the five issues. Each issue's images are available in their respective folders of the larger ViceVersa folder. Please note only the text of the Vice Versa story should be transcribed - ignoring any of the surrounding Voilà text (i.e. advertisements, other articles). We ask the text be transcribed (character by character; paying close attention to accents and original font styles found in the print rendition!)

Transcriptions can be done in Microsoft Word and then uploaded to the correct folder in your team's ViceVersa folder. You will notice in each issues' folder I have created a starter .docx file with the correct filename. If you choose to transcribe in Microsoft Word please begin by downloading the base file and upload your file overtop of that file as you progress.

Transcriptions can also be done in the following Google Docs for each issue:
ViceVersa_Issue1
ViceVersa_Issue2
ViceVersa_Issue3
ViceVersa_Issue4
ViceVersa_Issue5

Transcribing in either Microsoft Word or Google Docs is fine as long as your partner (if you have one on your specific issue) is aware of where you both are working -- so as to not upload over eachother's files. Also you must include accents -- if you are more comfortable adding special characters in Word then use Word. To insert special characters in Google:

At the top, click Insert and then Special characters.
Find the character you want to insert: search for base character (i.e. e for é), pick from categories, enter the character's Unicode value, or in the box on the right draw the character.
To add a character to your file, click it.

When transcribing please keep the following in mind:

You must transcribe titles and section titles with proper formatting (e.g., bold, italics, or caps)
Make sure you capture all accents and special characters (e.g., é, ä, ê)
Indicate paragraphs with indentations as in the article (not spaces or numbers)
Transcribe the article's page numbers at the end of each page's transcribed text, following the last line of the page
Transcribe all captions for images at the end of the transcription for each page following this format:
Indicate any comments/questions that arise while transcribing in square brackets, highlighted in yellow, and with your initials (as seen in the above example).

I have gone through and edited ViceVersa_Issue1 so it can be used as an example of our expectations.

Here are the new assignments:
Issue 1: images 10,11 -- Transcribed by @bossa12 and @dpedz, Revised by @RJP43, Needs to be proofed by @jsteele1 for accents, em dashes, and hyphenation removal.

Issue 2: images 12,13 -- Transcription started by @dpedz, Needs to be revised by @dpedz according to Issue 1 Example

Issue 3: images 14, 15 -- Transcription started by @jsteele1, Needs to be revised by @jsteele1 according to Issue 1 Example

Issue 4: images 14 (1934), 15 (1934) -- Transcription to be led by @ElleBromer

Issue 5: images 1934 PDF -- Transcription to be led by @bossa12

Collation : Tatjana, Anais, Tina, Elizabeth

hey there @Tatjanawj, @anais-turiello, @tinatiehen, @ekupchella 👋

Your teams have been assigned to collation work. Materials you will need are on Sakai/Resources/Project Assignments/Collation Work.

@tinatiehen, @ekupchella: You will fill out and proof the spreadsheets on your assigned chapters according to the samples and Thursday’s class lesson (3/14). You will need the collated versions of A1 and D1/TR (both available in the same Sakai folder).

@Tatjanawj and @anais-turiello: You will begin filling in the G1 column on the spreadsheet for Chapters 00-05 on Sakai (Sakai/Resources/Project Assignments/Collation Work/Sample Collation).

Danish Letter 19310724

Source Materials:

19310724 Folder
MIWschema.rng

Lili's Foreword

Source Materials:

LiliForeword.xml
Foreword Transcription
Foreword Images
MIWschema.rng

Let's Discuss Project Assignments

The final projects for this class will incorporate a variety of tasks. All of the tasks utilize skills we built together during the month of February. While certain groups will have slightly more technical aspects of their final project than other groups, ALL GROUPS will be responsible for communicating via our class Issues Board - following out best practices - as well as uploading to & downloading from this GitHub repository. Below I have defined the other types of tasks different groups will be completing.

Task Types

Document Transcription: As a minimal-tech task, those involved in document transcription will reference facsimile images of certain texts in order to transcribe the text seen in the image into a plain text (.txt) file or Google Doc with detailed comments describing document idiosyncrasies.
Transcription Encoding: If assigned this task, teammates will work with the project's encoding guidelines and the TEI Header template to construct an XML surrogate of the available transcription/translation of a given text. Encoders will be associating the project's new schema at the start of encoding; therefore, the final XML (.xml) file will need to be well-formed and valid.
XML Corrections: This task involves associating the new project schema to existing XML files and making corrections to the XML in order to make the XML valid and well-formed. Those working on this task will also be responsible for combining TEI Headers with the TEI Text from the existing XML. Some XML correctors will be working closely with @ProfPLC to make content corrections to mis-transcribed/mistranslated text.
HTML proofing: Proofers will be using Hypothes.is to indicate content and processing mistakes seen once the various XML texts are transformed into HTML. Proofers will report errors using the Hypothes.is annotation tool and the class Issues Board, but will need to review input XML to determine if errors in HTML presentation are results of encoding mistakes or missing style transformations.
Collation: This task involves going through the narrative carefully, marking in A1 (the American first edition) where changes exist in the other editions and the typescript. This task entails working closely with @ProfPLC in order to make decisions on what to mark as a variant and why.
Collation group 1 - (1 people) - paragraph by paragraph collation with @ProfPLC and @Tatjanawj
Collation group 2 - (2 people) - scene/motif collation

Available Texts

Danish materials:

Danish Materials GitHub Project Board
Danish Archive Folder

Lili Elbe to Maria Garland
four letters, 6 pages total
XML corrections and HTML proofing (2 people)

Lili Elbe to Poul Knudsen and T. C. Thomsen to Hoyer
four letters, 6 pages total
XML corrections and HTML proofing (2 people)

S. Thomsen to Harthern
approx. 20 pages total
XML corrections and HTML proofing (4 people)

Politiken articles
3 articles, 11 pages total
XML corrections and HTML proofing (2 people)

German materials:

German Materials GitHub Project Board
German Archive Folder

German letters 1 and 2, and the foreword
3 texts, 6 pages total
XML corrections and HTML proofing (3 people, including @Tatjanawj)

French materials:

French Materials GitHub Project Board
French Archive Folder

Allatini chapter
1 chapter, 14 pages total
XML corrections and HTML proofing of the translation (2 people, readers of French)
transcription of the original French version and encoding of transcription (2 people, readers of French)

Hirschfeld chapter
1 chapter, 6 pages total
XML corrections, HTML proofing (2 people, readers of French)

"Vice Versa" from Voilà
4 issues, 8 pages total
Transcription (2-3 people)

S. Thomsen to Harthern : Sophie, Aliana

hey there @skarrow and @alicapati 👋

Your team has been assigned the Danish-language letters and diary entries from S. Thomsen to Harthern. As a team you will work to combine the following XML files into a single XML file titled 19310615ThomasSHarthern_combo.xml:

In addition to combining those files and uploading the new file to the 19310615 folder, your team will need to associate the new project schema to your new XML file as well as this 19311221ThomsenSHarthern.xml file.

Then you will need to correct the XML errors (in the entire file for each file - including errors found in the <tei:header> elements). 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.

After you have uploaded the valid and well-formed XML files in each of the letters' respective folders, 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 each of the two letters -- reporting errors and design concerns regarding the HTML styling to me via this issue (tagging me and again 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 each of the two letters' folders (i.e. original transcriptions, facsimile images, etc.) to proof the HTML.

Once each of the two letters has been proofed @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.

Danish Letter 19211922

Source Materials:

19211922 Folder
MIWschema.rng

German Letters and Foreword : Samantha

hey there @Samantha9899 👋

Your team has been assigned the German-language letters 1 and 2 as well as Lili's Forword. As a team you will need to associate the new project schema to each of these XML files:

In addition to associating the schema, we are asking that you help us clean up our filenames for both of the German letters. Please change German_letter1.xml to 19320309KellerHLE.xml and German_letter2.xml to 19310627LEKellerH.xml. The foreword filename should remain the same.

Then you will need to correct the XML errors (in the entire file for each file - including errors found in the <tei:header> elements). 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.

After you have uploaded the valid and well-formed XML files in each of the letters' and foreword's respective folders, 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 each of the two letters and the foreword -- reporting errors and design concerns regarding the HTML styling to me via this issue (tagging me and again 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 each of the two letters' and the foreword's folders (i.e. original transcriptions, facsimile images, etc.) to proof the HTML.

Once each of the two letters and the foreword have been proofed @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.

Using persName with translations

I am about to code the English translation of the Danish letters. Do I encode persName and placeName in translations, too? Thank you! Kristin

German Letter 3

Source Materials:

German_letter3 Folder
MIWschema.rng

Hirschfeld chapter : Amanda

hey there @joaquindavalosponce, @amandallopez, and @ElleBromer 👋

Your team has been assigned the French-language Hirschfeld chapter. As a team you will need to associate the new project schema to HirschfeldChapter.xml.

Then you will need to correct the XML errors (in the entire file - including errors found in the <tei:header> elements). 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.

After you have uploaded the valid and well-formed XML file in the Hirschfeld Chapter folder, 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 chapter -- reporting errors and design concerns regarding the HTML styling to me via this issue (tagging me and again 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 each of the Hirschfeld Chapter folder (i.e. original transcriptions, facsimile images, etc.) to proof the HTML.

Once the chapter has been proofed @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.

~ Declaration of Commitment ~

Dr. Caughie and the Lili Elbe Digital Archive project-team wish to express our deepest gratitude for the undergraduate engaged learners participating in the ENGL 283.06E, Transgender in Literature, class. Their contributions to the archive are truly invaluable. In signing this “Declaration of Commitment,” the undersigned engaged learners commit to the following:

not sharing archival materials outside of the designated GitHub repository
upholding to the behavioral standards laid out in Dr. Caughie’s course guidelines, with regard to teamwork as well as responsible conduct and research
maintaining a professional digital persona and mutual consideration for fellow learners and project collaborators as laid out in Rebecca Parker’s digital etiquette expectations

This declaration was signed by the following Engaged Learners during the first week of our 2019 February class meetings - Feb. 5th & 7th, 2019.

Engaged Learners, please commit to this declaration by commenting the following below:

I, ____insert name here____, commit to the above declaration.

2019 Summertime Volunteer Tasks

Hello volunteers 👋

Thank you for continuing work on the Lili Elbe Digital Archive! 🎉 This issue is where we will organize and assign your technical tasks from May 2019 until August 2019.

As you complete a task please feel free to check-off the associated box.

Please note there will be more tasks added to this list as the months ensue and our website launch nears. Tasks might also change or become more developed so please check in here regularly.

@Dadelinee Tasklist

Finish encoding Spring2019_SecondBatchGermanLetters. You might find it useful to look over the issue where I first assigned these documents to your EL classmates here - #42

Let's Discuss "Glands, Eugenics, and Rejuvenation in Man into Woman"

Each student should respond in this discussion thread after reading:

Kadji Amin’s "Glands, Eugenics, and Rejuvenation in Man into Woman," TSQ: Transgender Studies Quarterly, vol. 5, no. 4 (November 2018)

The reading can be found on Sakai under Resources in the Required Essays folder.

Please respond to either option # 1 or option # 2 by Monday, March 11, 5 PM. Be prepared to discuss your responses and the essay in class on Tuesday, March 12th.

In your response please indicate the option you are responding to, and as always because we are hosting this discussion on GitHub we encourage you to use GitHub's markdown syntax. In addition to text styling (like bold, italics, and offsetting quoted text) made available via markdown, you are also able to attach files (images are particularly welcome) and insert emojis in your responses. Please use the GitHub Help Tutorial on basic writing and formatting syntax along with the emoji cheat sheet to assist in writing an engaged response.

Option 1

Answer both questions in a few sentences each.

What is the advantage, for scholarship on transgender, of not reading Man Into Woman as one of the “foundational moments in transgender history” (590)? Why is Lili the “wrong figure to be honored as a foremother of today’s transgender movement” (590)?
What is one historical fact you learned from this article that you found surprising or disturbing?

Option 2

Amin draws on several concepts from other scholars to critique readings of Man Into Woman as an early transgender narrative. How are these concepts defined and why are they problematic?

Presentist history (p. 590) [not history of the present—look it up]
Emotional rescue (Heather Love’s term) (p. 590)
Endochronology (Jordy Rosenberg’s term) (p. 594) [not “endocrinology,” the science]
Genealogy (Michel Foucault’s concept) (pp. 593-594, 602) [not the commonsense understanding of this term]

XSLT assistance outreach -- arbitrary attributes added

Issue:
at //* in output file - A1_paranumber.xml - there are arbitrary attributes added that are not on the descendant::* elements of the input file - A1.xml.

Help request:
Is this a namespace related issue? How do I suppress these auto/default attributes from appearing after running my numberingParagraphs_MIW_A1andB1.xsl (a TEI XML to TEI XML identity transform)?

Files are in the sandbox. Thanks for any advice/assistance.

Danish Letter 19310615

Source Materials:

19310615 Folder
MIWschema.rng

German Letter 2

Source Materials:

German_letter2 Folder
MIWschema.rng

Invite to Rebecca Parker's Defense on 4/26 9-10 AM in Crown 528

👋 Dearest LEDA learners,

@zothman @Tatjanawj @JackieAlfarah @Dadelinee @bcristiana @ElleBromer @alicapati @joaquindavalosponce @Katiegriggs24 @schola0208 @skarrow @kklimek1 @ekupchella @amandallopez @amccann2 @BMiller10 @elenipamboukis @dpedz @wravindran @Samantha9899 @nroyce @kschoen3 @jsteele1 @tinatiehen @anais-turiello @bossa12 @kejcat

I wish to extend a heartfelt, personal invite to you all for my public Digital Humanities MA defense. I will be defending the plain.txt podcast from 9 AM to 10 AM in the Crown Center for Humanities room 528 TOMORROW (Friday, 4/26). In addition to this, I also wanted to (in)formally thank you all for being a part of my graduate school experience and community. From the center to the library and from my mentors and graduate student peers to my students-- I want you each to know that I am extremely appreciative of the valuable contributions you have made towards my education. On that note, I recognize my defense is early in the morning and on the last day of classes before finals week; therefore, I want to relieve all of you of any pressures you might be feeling to attend. While you all are welcome I 💯get the stresses and obligations of this week, in particular, and do not want anyone jeopardizing the completion of their own work or their mental health to be there. Personally, I think the most wonderful thing about my project is that I have worked really hard to make it as accessible as possible -- meaning it is highly documented and can be accessed in many different ways; therefore, anyone interested can "tune in" (😆) anytime. Tomorrow, while important, marks just one milestone of the project's (hopefully) long and prosperous future with endless possibilities for you to connect whenever. THANK YOU ALL for being my knowledge neighbors.

Best wishes to each and every one of you as we "come to term" 😉.
Sincerely,

🤓 Rebecca J. Parker (@RJP43)

BCristiana_Option2

Option 2
Kadji Amin wants to have his cookie and to eat it. In the 2015 movie The Danish Girl, based on an adaptation of Lili Elbe’s life narrative, Man into Woman, he sees an attempt by the mainstream media to conveniently falsify the transgender history, for both commercial and definitional purposes. To prove that this is the wrong narrative, and Lili Elbe the wrong person to inaugurate the pantheon of queer inspirational figures, Amin employs a varied set of conceptual tools and a suitably selected factual base for his arguments. He contends that the glandular rejuvenation in the guise of sex transition therapy (601) is the real drive of Elbe’s tribulations and connects the sex-centered dawn of the last century with a system of “racialized biopolitics and eugenics” (597) for which she serves as an illustration of biologically fit, normative femininity (601).
For Amin, Lili’s death is an emotional rescue device and one of the narrative’s sins. Thus, her shortly lived womanhood unties cathartically the transgender identity from the pathological stigma, while it obscures the positivist belief at the time in biology as the remedy of all the ills that threaten the whites’ racial superiority. Discontented with a film that voids the past of its specificity in order to infuse it with the present day understanding of transsexuality, Amin commits himself the presentism fallacy. In judging Lili as interested rather in rejuvenation than in sex alteration, not only does he replace the effect with the cause, but expects from her a behavior that typifies the present acception of transgender, at a time when its conceptual awareness didn’t exist, much less the language to express it. The way he interprets it, the film asserts a linear determinism that links the problematic past of transsexuality with its present, within an endochronologic framework whose apparent simplicity conceals the sexological and colonial forms of knowledge-power (591) and whitewashes the biopolitical eugenics (594). Thus, Amin argues that Lili’s fictional memoir doesn’t belong to the queer wrong body narrative, but takes the glandular conception of selfhood to its logical limits (596). While Lili’s surgeries closely precede the Nazis’ rise power, and her surgeons’ careers become entangled for the better or for the worse with the state-enforced eugenic project, Amin substitutes again the subsequent for the antecedent and connects speculatively the source of her ovarian transplant with the forced sterilization program (601). He takes the next step and, in a twisted syllogism, links the ovarian transplant to the rejuvenation as part of the efforts to direct reproduction (598), and Lili’s case of sex reassignment surgery to the attempts to fix sexual degeneration and restor[e] . . . ‘healthy’ sex polarity (599).
At times conflating this fictional memoir and its cinematic version, though the latter is one degree farther from the reality than the former, he criticizes a literary discourse with the tools of sociologist when, in yet another anachronistic fallacy, considers the transgenderism of both Man into Woman and The Danish Girl not intersectional enough because it does not deal with the hierarchical structures of value and silent modes of normativity (590). Yet he ignores the influence of Foucault’s systems of power-knowledge in the shaping and creation of the subjectivity, that is, the very mechanism at work in the repudiation of the scientific racism at the end of WWII. It is the French philosopher’s concept of genealogy as historical process subjected to contingent forces that he appeals to in analyzing the relation between this past and contemporary transgender politics (593), as opposed to the endochronological predictability. In this way, he can reveal inconsistencies and uncomfortable truths and demonstrate that there is nothing presumptively innocent about the trans subject across time and place (603). After advancing some very strong conclusions based on speculative conjectures only, in the end, he describes the genealogy that he advocates for as open to multiple ramifications and often contradictory origins (602). If now, as then, the biopolitics of transgenderism involves tensions engendered from the same multiple systems of oppression and privilege (602), maybe this study focuses on the wrong period and with the wrong tools.

Coding segments

I am putting in coding for segments the Sanheden article. Should headlines be included as segments? I thought yes but wanted to check. Thanks.

better way to code TEI header

Becca,

I wrote a note in our meeting that you recommended I look at the TEI header lesson for a different way to include a title that has a translation. I couldn't find anything in the TEI header on this subject. What am I missing?

Thank you!

Kristin

Second Set of German Letters : Bennet, Joaquin, Samantha

Hey there @BMiller10, @joaquindavalosponce, @Samantha9899 👋

Please reference the Facsimile Images and the Transcription-Translation Word documents when encoding these texts. All files for these texts will exist in the Spring2019_SecondBatchGermanLetters folder.

Specific assignments:
1931-12-28SchumannHoyer - @BMiller10
1932-01-21HoyerSchumann - @joaquindavalosponce
1932-06-30SchumannHoyer - @Samantha9899
1932-07-16HoyerSchumann - TBD

In order to complete XML encoding of these texts you will need to do the following for each letter:

As always, please begin by downloading the latest schema as well as your text's images and transcription/translation .docx file.

Go into oXygen and create a new XML file ➡️ in oXygen, click on the icon at top left that looks like a piece of paper with a folded corner (or go to File and New), type XML in the filter window, and click the Create button to launch a new XML document. -- instructions from our XML_Exercise. Be sure to save your new XML in the same folder as you downloaded the schema.
Delete the contents of that new XML file and paste in the TEI header template --- review the template filling in the applicable sections and removing sections that do not apply to letters. Be sure to use the TEI header spreadsheet and our list of <respStmt> team member IDs (both available on issue #35).
Replace the <text> element with the "Texts with Translations" encoding from the guidelines.
Paste the Letter text-type encoding from the guidelines into each of the <div> elements.
Paste the text of the original text from the Word document into the <div type="original"> element. Be sure to paste interior sections of the letter into their respective, different sub-elements. Meaning you should paste the salutation text from the document into the first salute element and so on for each unique part of the letter. You will need to create <p> elements around each of the letter's body paragraphs after the first salute but within the <div rend="body">.
Paste the text of the translation text from the Word document into the <div type="translation"> element. Following the same instruction detailed in step 5.
This is a good point to pause and upload your new XML to GitHub. Newly created .xml files should be uploaded to the Spring2019_SecondBatchGermanLetters folder. XML files should be named the same as the corresponding Word documents except with the .xml file extension instead of the .docx extension.
Once you have uploaded, please update this issue letting us know your progress and I will provide you with next steps.

Politiken : Unassigned

hello 👋

Your team has been assigned the Danish-language Politiken articles and Lili's Obituary. This is marked as your second task while @zothman ties up loose-ends with her encoding. As a team you will need to associate the new project schema to each of these XML files:

coming soon

Then you will need to correct the XML errors (in the entire file for each file - including errors found in the <tei:header> elements). 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.

After you have uploaded the valid and well-formed XML files in each of the articles' and obit.'s respective folders, 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 each of the articles and the obit. -- reporting errors and design concerns regarding the HTML styling to me via this issue (tagging me and again 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 each of the articles' and obit.'s folders (i.e. original transcriptions, facsimile images, etc.) to proof the HTML.

Once each of the articles and obit. have been proofed @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.

rjp43 / lilielbe_engagedlearners Goto Github PK

lilielbe_engagedlearners's People

Contributors

Stargazers

Watchers

Forkers

lilielbe_engagedlearners's Issues

Source Materials:

Source Materials:

Source Materials:

Source Materials:

Source Materials:

Source Materials:

<teiHeader> Template Update

Source Materials:

How to Proof HTML

Preparing to Proof

Proofing HTML and Editing XML

Source Materials:

Source Materials:

Task Types

Available Texts

Danish materials:

German materials:

French materials:

Source Materials:

Source Materials:

@Dadelinee Tasklist

Option 1

Option 2

Source Materials:

Source Materials:

Recommend Projects

Recommend Topics

Recommend Org

`<teiHeader>` Template Update