ksd32/george-washington-diaries-

george-washington-diaries-'s Issues

SSI hint

Note that the text that you include as your Server-Side-Include (options.html) does not need to be a well-formed HTML document. That is, it doesn't need the HTML root-element, the head, or the body! ...only the elements that you want to include.

Project Feedback

I love the amount of markup you guys did on this! The ability to find all those references in the letters with one click is awesome.
One thing I noticed is the handwritten background. Are those actual scans of the letters? Would it be possible to put a few full scans of his letters alongside the text copy or are they protected by copyright of whoever owns them? It would be neat to see one or two full samples of his writings on the site.

ODD stuff

@KSD32 Here are some resources for building your ODD:

• You want to have the TEI Guidelines open to browse: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html
• You want the full list of elements and display them module by module:
  http://www.tei-c.org/release/doc/tei-p5-doc/en/html/REF-ELEMENTS.html#

Welcome!!!

Welcome to the repo for George Washington Diaries!!! I'm very excited to be working on this project. I know we're going to have a lot of fun.

Site Index Starter Prepared

@KSD32 Everybody do a git pull on your project repo! Following up on our TEI ODD development meeting on Friday, I've written a little XSLT to run over your collection of XML files and output the base of a site index. The new files are in this commit: a83c0db

• In order to process your XML collection, I had to repair some & characters to convert them to &so that accounts for some of the altered XML files.
• The XSLT I wrote to pull distinct values of the various names is here: https://github.com/KSD32/George-Washington-Diaries-/blob/master/prosopBuilder.xsl You may want to modify it if I didn't catch everything!
• The output starter site index file is in a new siteIndex directory here: https://github.com/KSD32/George-Washington-Diaries-/tree/master/siteIndex
  This starter site index is made from the distinct values of names of people, places, and organizations like we discussed. Let's take a look at the new files together with @Julegirl if we can, and talk about what's next to do. You're going to want to hand-edit these to repair the names and add some more tagging (you can distinguish surname, forename, rolename, etc.), and you'll want to work out together how to develop the file. The key thing we need for your ODD schema, though, is for you to apply a distinct @xml:id to each member of the new site index list.

We can then write another XSLT to take those values and add them to your ODD file. This is a little tricky and I'll help with it like I did this one. It'll be an identity transformation of your ODD file, in which you add your rules for legal @ref attribute values pulling directly from this site index file, once it's ready.

I'm tagging @quantum-satire since I'm pretty sure she'll want to follow along with this process, too.

Links for Diaries/Letters

https://www.loc.gov/collections/george-washington-papers/about-this-collection/#D

https://www.loc.gov/resource/mgw2.041/?sp=1

https://www.loc.gov/resource/mgwd.wd03/?sp=19

https://www.loc.gov/resource/mgw3a.001/?sp=1

https://www.loc.gov/resource/mgw1b.601/?sp=2

Relax NG and TEI

Trying to link a Relax NG Schema file with one of the TEI files. This is what I have.

But when I take out the attribute value, I get the message

Do you have any advice on how to fix this?

Location Codes

• Write XSLT to output list of distinct values of all <placeName> elements from your collection of letters

• Apply <xsl:sort> to this XSLT to sort the output

• Reformat the output to make a placeography (list of places and info about them, and specific one-string (no-white-spaces) location xml:id's

• Write a NEW XSLT to map the location codes back onto the letters.

More Personal Letters

I added three more letters for the Personal Letters. I posted letter for Washington's Brother Samuel, his friend Robert Jackson, and Mrs. George William Fairfax.

Uploading files

Hey,
I've tried to put up new files that I transcribed, but the page says that Uploads are disabled.

Updates from Weekly Meetings?

Please post brief notes each week after your meeting describing what was accomplished, and any new plans or developments. @KSD32 @Julegirl

Question re ODD-Schema

Hi @KSD32 I was noticing you have a sort of double schema line on your project files now, and I'm thinking that's probably not what you want. What I see is this:

<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml"
	schematypens="http://purl.oclc.org/dsdl/schematron"?>

<?xml-model href="../WashLetterTEI.rnc" type="application/relax-ng-compact-syntax"?>

That looks like you're using the TEI-all on the top line--not the ODD-generated customized schema. Underneath it looks like you have the new schema--that's the one from your ODD right?

I think having both may cause some conflicts: TEI all won't know some of the things you've customized, like attribute values. I want to take a closer look, but maybe you can tell me what's going on and how this is working? I might be missing something I should know... I'm getting on a flight now, but I should be able to take a closer look later this evening.

Project Feedback

I really liked your website. I thought you guys did a good job of gathering important data.

Project Checkpoint 4 due on Monday, Dec 3rd

Project Checkpoint 4 is coming-up on Monday, Dec 3rd. Follow our Project Guidelines. In grading this checkpoint, we will be looking for the following:

• 1) XML Markup: Your XML markup of these documents should be about finished. Your collection should consist of well-formed XML documents full of detailed content-level markup inside your paragraphs.

• 2) Schema: EVERY XML-file must be associated (linked-to) a schema that validates its contents. TEI-based projects should also have an ODD that was used to generate the schema.

• 3) Webpages: The webpages and CSS should well-developed: A descriptive and attractive home page should lead to several NON-EMPTY pages of content that contain links to the HTML-versions (or at least XML-files) of the texts used in this project. Also, supporting text describing the these texts, and what will be displayed in the future (when complete), should be present. Although we don't expect your SVG graphics to be in a finished state, there should be some indication of where they will be located and some description of what they will portray. Again, all of the main web pages should use CSS and SSI's (for your site menu).

• 4) Web space on Newtfire.org: As you upload files to your web space using Filezilla, try to keep your files organized. Because you should not be storing all of your files in the same (root) file-directory on your website, you should have a logical hierarchy of directory folders for different kinds for files (css, letters or other source documents, graphics, etc.). Also, eliminate any duplicate copies of files.

• 5) GitHub Repo: GitHub should be at the core of your project development: Just as your webspace should have a logical structure of directory folders, so too should your project repo on GitHub. Similarly, eliminate any duplicate copies of files, redundant schemas, earlier experimental versions (or put them in a folder called "old".

All of your project files (text, XML, schemas, webpages, CSS, etc.) should be on GitHub so that the entire project team, and your instructors, can access them.

We've designed this as a task list that you can mark off as you complete the tasks. (You can generate one for your team using markdown like we did here. Use the icon above with the checkmark to create a task list entry on a GitHub Issue)
@KSD32 @Julegirl @quantum-satire

Creating Prosopography Lists: People, Orgs, Places, Events

1. To start this, we need to extract (with XSLT) sorted lists of distinct-values() of the following element contents:

listPerson

• persName

listOrg (institutional entities, nation states, etc):

• personGrp
• location/region

listPlace

• placeName
• location[not(region)]

2. We'll output these in a series of TEI formatted lists.

3. You, @KSD32, will then need to add @xml:id values to that list, and lump duplicate values together. A <person> element contains a single @xml:id that can dereference many <persName> elements you hold inside.

4. Last, we will write XSLT to do an identity transformation on your ODD file and add those xml:id values as lists of legal attributes with hashtags attached for @ref on your inline coding of the letters.

New Tasks: Fun with the Site Index

• @Julegirl : Check for new files to contribute in your forked repo. Issue a pull request on this repo for anything new. Wait for @KSD32 to pull in anything new from Julie, OR signal each other that there's nothing new to contribute.
• @Julegirl : "Nuke" your forked repo at home, and clone this repo so you can do a git pull directly on this repo.
• Each of you, @KSD32 and @Julegirl, figure out a workflow to edit the site index base.
  • @Julegirl will start by "de-duping" the entries (see below, due by midnight Wed. 11/7)
• Write a new XSLT to pull events to make a <listEvent>: @KSD32 will try this in a new XSLT, and then paste the output into the siteIndex.xml file. TRY NOT TO OVERWRITE HAND-EDITED CAREFULLY CURATED "GORGEOUS" SITE INDEX CODE.
• Work on modifying the source XML to "clean up" the markup. Example: Do you want to replace<location><region>France</region></location> with <orgName>France</orgName>

Eventually you want <orgName ref="#France"> in your markup of Washington's letters, diaries, etc., so it "points" to your site index entry on

<org xml:id="France">
      <orgName>France</orgName>
      <note>France was involved in the.... </note>
</org>

Project Checkpoint 3 due Mon Oct 29

Project Checkpoint 3 is coming-up on October 29th. In grading this checkpoint, we will be looking for the following:

• 1) Collection: A reasonably complete collection of the documents on which your project will be based. You can always add to these as you discover additional ones, but you should have a functional and representative collection of documents by this point.

• 2) XML Markup: Your XML markup of these documents should be well underway now, so by October 29, your collection should consist of well-formed XML documents with basic structural markup, at least down to the level of paragraphs, and other major parts. We would like to see content markup that you're applying to address your research questions as well, but we do not expect the mark-up of any of these documents to be complete, so plans for later additions are OK. Please document those plans (write up task lists for the team on the repo).

• 3) Schema: This mark-up should be controlled by one or more schema files linked to these documents. Again, we don't expect that the schemas will be complete and fixed-in-stone, but they should conform to the current state of the mark-up at that time.

• 4) Webpages: The development of the webpages should be progressing on-pace with the mark-up. A descriptive and attractive home page should lead to several logical and developing pages of content. Although we don't expect your XML documents to be in a web-ready state, there should be some indication of where they will be located. All of these pages should use CSS and SSI's (for your site menu). Also, because you should not be storing all of your files in the same (root) file-directory on your website, you should have a logical hierarchy of directory folders (which was supposed to be developed for Project Checkpoint 2).

• 5) GitHub Repo: GitHub should be at the core of your project development: Just as your webspace should have a logical structure of directory folders, so too should your project repo on GitHub.
  All of your project files (text, XML, schemas, webpages, CSS, etc.) should be on GitHub so that the entire project team, and you instructors, can access them.

We've designed this as a task list that you can mark off as you complete the tasks. (You can generate one for your team using markdown like we did here. Use the icon above with the checkmark to create a task list entry on a GitHub Issue)

@KSD32 @Julegirl @quantum-satire

Site index

Ok, so I found as many birth and death dates as I could. I can't find any more than this.

Project

The site is up and ready!