Getting Started
What to do...
The WWP training process involves learning several different kinds of things, all at the same time. We recognize that this is difficult! Here is a quick summary of what you’ll be focusing on as you get started:
- Learning how to use the emacs text editor. This is the editing environment we use to do the encoding; it’s very powerful, and hence takes some practice to get used to. The first thing you’ll probably do is take the emacs introductory tutorial. To do this, log onto the WWP server and launch emacs). Then type Control-h t and the tutorial will launch. Do what it says, and stop when your head is full. You can come back to the tutorial later on. When you’re done for the day, quit emacs and log off from the server.
- Learning some basic information about the XML and the TEI. We’ll cover some of this in person, and a list for further reading is below.
- Begin encoding your first text. First, choose a text from the Transcription database and update the record to indicate that you are claiming it. Next, log into the server and find the starter file for your text. There are instructions on how to open and manage files on the server. We also have a sample to look at, and some pointers on how to proceed with the basic encoding. As you encode, look up unfamiliar elements both in the TEI guidelines (see below) and in the WWP’s own documentation, and ask questions often. You can post questions to the WWP tagging list, WWPTAG-L@listserv.brown.edu.
- As you work on your file, you should check frequently to make sure it is valid. (A good rule of thumb is to validate every time you save, and to save often!). Validate your file by typing Control-c Control-v and then press Return at the next two prompts. The instructions here will tell you how to interpret any error messages you receive.
- When you’ve finished your first text, it’s time to supravalidate it: this is a process that will check for certain kinds of errors and inconsistencies that are not caught by validation alone. Run supravalidation by typing Control-c Control-x, and fix any errors that are reported. The instructions here will help you interpret the error messages and decide what to do to about them.
- When your file is as good as you can make it, update the Transcription database with the date of completion; the text will then be printed for proofreading.
Pointers and samples
- How to log onto the WWP server and launch emacs
- Sample encoding
- Encoding pointers (under construction)
- Validation instructions
- Supravalidation instructions
Readings
Some people learn best by reading first, then practicing; some people prefer to practice and read when they need to find something specific. The readings below are the main sources of information on text encoding at the WWP and you’ll probably need to cover most of them during the course of your training.
- A Gentle Introduction to XML, Chapter v of the TEI Guidelines. This provides a basic grounding in the concepts of XML.
-
TEI Guidelines, P5 version. The chapters that apply most directly to the WWP’s work are:
- Chapter 3, Elements available in all TEI documents
- Chapter 4, Default text structure
- Chapter 7, Performance texts
- Chapter 11, Representation of primary sources
- Chapter 16, Linking, segmentation, and alignment
- Chapter 17, Simple analytic mechanisms
- Chapter 13, Names, dates, people, and places
- TEI element list, Appendix C of the TEI Guidelines, provides a complete list of TEI elements with links to reference documentation for each one.
- WWP Encoding Documentation
Where things are
The texts we use to transcribe from are called “OTs” (“Office Texts”) and are stored in the file cabinets in the encoding room. Each one has a unique “OT number” (OT00001, etc.) that serves as a catalogue number.
All encoding progress is tracked in a Filemaker database called “WWP_Transcription”. To find it, launch Filemaker, then choose “Hosts” and select WWP_Transcription from the list.
Time sheets are in the black binder on top of the file cabinet in the encoding room.
