View on GitHub

NEH Institute materials

July 2022

Home | Call | Admin | Week 1 | Week 2 | References | Slides | App development

Week 1, Day 3: Wednesday, July 13, 2022

Synopsis

Moving from model to implementation. The third day is devoted to developing the digital editing workflow as a computational pipeline. Session one extends the command line skills introduced Tuesday. In session two we discuss applications of modeling to our laboratory edition, explore alternatives to TEI, and encode a sample document together. In the afternoon, we return to XQuery to create our first computational step in the pipeline. In a special topic session, Patrick Juola introduces stylometry as an example of integrating statistical description and evaluation into the perspectives exposed within an edition.

Outcome goals

Legend


9:00–10:30: Command line

Practice navigating your file system and using tools at the command line, including Git.

Edition repo stages for session

Time Topic Type
20 min Command line basics. Code lab
25 min Working on the command line. Code lab
15 min Generating your personal access token. Code lab
30 min Practice Git on the command line. Code lab

10:30–11:00: Coffee break

11:00–12:30: Modeling the data for the edition

Edition repo stages for session

Time Topic Type
30 min TEI XML in context: rationales, alternatives. Presentation
40 min Encoding data in TEI XML together in small groups. Code lab
20 min Building a title list with XQuery: Plan goals, pipeline, and find the data. Discussion

12:30–2:00: Lunch

2:00–3:30: Creating a pipeline with XQuery: you are the controller (Ghost Hoax data).

Edition repo stages for session

Time Topic Type
30 min Translating your research goals into your work plan. Talk lab
60 min Building a title list with XQuery: Create the model, part 2: construct model in model namespace. Code lab

3:30–4:00: Coffee break

4:00–5:30: Special topic: Stylometry with Patrick Juola

Time Topic Type
90 min Stylometric authorship attribution. Presentation

We’ll end each day with a request for feedback, based on a general version of the day’s outcome goals, and we’ll try to adapt on the fly to your responses. Links to the feedback forms are in our Slack workspace in the #daily-feedback channel (posting from Mason on Mon, July 11).