Metadata and the TEI header

In Part 1 of this exercise, you produced a coded representation of the Cheese Straws documents in the <text> portion of the TEI document. Now we will concentrate on identifying metadata, which literally means data about data. When preparing digital editions, the metadata is information about how documents were prepared, what materials they are made of, how those materials are represented (for example, a photograph of a physical piece of paper, or the piece of paper itself). The metadata also includes information about who prepared the documents, where they are stored, and who is involved in transcribing and representing them in the current document. The people who were involved in producing and reproducing the documents all had a hand in its transmission, and their identities and roles are also part of a document’s metadata.

The TEI Header (or the TEI document encoded in the <teiHeader> element) is designed to store metadata, and it can be very complex when representing a digital edition, because it should contain information about the document being represented and whatever is known of its provenance (or origins), as well as information about the person encoding it now and the date and time of its encoding as a TEI document. Part 2 of this exercise with the TEI is designed to give you experience with thinking about how to encode metadata, following the TEI Guidelines as a standard for sustainable practice. Whether or not you choose to work with the TEI for your course project, the experience of coding metadata should be a useful exercise that you may later adapt in the XML architecture that you design.

Researching the TEI Header and Manuscript Representation

Begin by reviewing the Cheese Straw Recipe documents and jot down some notes about what metadata you have available. Who was writing the various documents? What are the documents made of? What kind of image do you have of the manuscript? What do you know of dates when the documents were found or produced? What else might qualify as metadata here?

Now, read and sift the TEI Guidelines from Chapter 2: The TEI Header and Chapter 10: Manuscript Description, and consider what information to place in the header, and what TEI elements you could use to describe the material and condition of the documents. You may, if you wish, reorganize your TEI document as a whole: Are any parts of the <text> perhaps better represented in the <teiHeader>? Think about how to distinguish between the hands involved in the recipe and its context: How can TEI markup help to distinguish Prof. Triplette’s writing from her grandmother’s?

It may help you to look at an example from a manuscript edition project, so you may want to look now at the TEI header in our sample letter file from the Digital Mitford project. (You can also view how we represented the metadata and the letter in our web rendering.) There is far more metadata on the Mitford letter than we have to record for this small exercise, but we hope it gives you some ideas of metadata to look for.

Coding the TEI Header

Return to your TEI document. The version of the header that you see in <oXygen/> contains only the absolutely minimal necessary information to satisfy the TEI validation, but you will certainly want to add more, concentrating, for example, on fleshing out the <sourceDesc> with <msDesc> elements. Develop the TEI header to represent the metadata you observed about the documents you are coding as well as metadata about your own involvement in coding them in this document. Feel free to revise and reorganize the encoding of the material in the <text> element as you are building up your TEI header.

Submitting your work

When you are ready to turn in your work, rename your file according to the homework file submission rules, and upload it at the appropriate place on Courseweb.