View on GitHub

NEH Institute materials

July 2022

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

Week 1, Day 1: Monday, July 11, 2022

Synopsis

Fundamentals. The Institute opens with a high-level view of the types of engagement required by a textual editor, beginning (always!) from the research questions and leading to the production of an actual edition. In session two we introduce the computational pipeline as a way of modeling project development. We begin the afternoon by installing the software packages required for our Institute. Finally, we discuss some exemplary digital editions and start using XQuery to explore XML.

Outcome goals

Legend


9:00–10:30: Getting started

Introductions, research questions, schedules, outcome goals.

Edition repo stages for session

Time Topic Type
15 min Introductions. Presentation
30 min Research questions and choosing our technologies. Presentation
15 min Discuss two-week schedule and day plans. Presentation
30 min Review laboratory outcome goals and explore participant goals for their own editions. Talk lab

10:30–11:00: Coffee break

11:00–12:30: The edition as a computational pipeline

Edition repo stages for session

Time Topic Type
30 min We introduce the computational pipeline as a way of modeling the development of a digital edition. Presentation
30 min Initial stages: TEI XML (base view), exploring with XPath, and exploratory data analysis (EDA) with Shakespeare. Presentation
30 min Transformation: how do I transform, what do I transform to? We also introduce the model-view-controller (MVC) architecture we’ll use in app development later on. Presentation

12:30–2:00: Lunch

2:00–3:30: Selecting your tools and software installation best practices

Time Topic Type
90 min Software installation instructions. Code lab

3:30–4:00: Coffee break

4:00–5:30: XQuery and digital editions

Time Topic Type
45 min Exemplary digital editions. Discussion
45 min Exploratory data analysis in eXide (Shakespeare data). Code lab

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).