CDL Encoding Guidelines for the TEI Header

DRAFT

Jared Campbell

Brian Tingle

The encoding guidelines provided here are unedited working drafts produced by CDL's Structured Text Working Group. They should not be treated as final documents. Updated guidelines will be available in November 2004.


Table of Contents

Introduction
1. Encoding Guidelines
1.1. R <teiHeader>
1.2. R <fileDesc>
1.2.1. R <titleStmt>
1.2.2. M <author>
1.2.3. M <editor>
1.2.4. O <funder>, <sponsor>, <principle>
1.2.5. R <respStmt>
1.2.6. R <extent>
1.2.7. R <publicationStmt>
1.2.8. O <seriesStmt>
1.2.9. R <sourceDesc>
1.3. O <encodingDesc>
1.3.1. O <classDecl>
1.4. O <profileDesc>
1.4.1. O <langUsage>
1.4.2. O <textClass>
1.5. M <revisionDesc>
1.5.1. M <change>
Minimum and Full CDL TEI HEADERS
TEI HEADER to DUBLIN CORE CROSSWALK

Introduction

The following is a general guideline for creating the <teiHeader> for documents to be submitted to CDL. Each document header should contain <fileDesc>, <encodingDesc>, and a <profileDesc>.

The following codes are used to indicate whether an element is required or not:

R The element is "REQUIRED"
M The element is "MANDATORY WHEN THE INFORMATION IS AVAILABLE"
O The element is "OPTIONAL"

Chapter 1. Encoding Guidelines

1.1. R <teiHeader>

Use the <teiHeader> type=" " attribute to encode the CDL TEI text type guidelines that are to be used. Type values include CDL-TEI:MS for manuscripts, CDL-TEI:OH oralhist for oral history transcriptions, and CDL-TEI:BK for other texts.

<teiHeader type="CDL-TEI:BK">
        

1.2. R <fileDesc>

The <teiHeader> should provide a relatively complete bibliographic record for both the electronic version and the original source document. The data that describes the electronic text should be encoded in the <fileDesc> section, while data that pertains to the source text should be encoded within the <sourceDesc> (a subsection of <fileDesc>) section. It should be noted that data (such as <author>, <editor>, etc.) will often be identical in both sections. Exceptions include:

  1. The <fileDesc><titleStmt><title> will include a mandatory "electronic version" subtitle.

  2. The <fileDesc><respStmt> will include the name of document encoders and individuals responsible for proofing or making general corrections to the encoded file.

  3. The <extent> in <fileDesc> will encode (in Kb. or Mb.) the size of the electronic file. The <extent> in the <sourceDesc> will record the number of pages, illustrations (if present), and dimensions (see the MARC 260 field).

  4. The <publicationStmt> in <fileDesc> should be used to encode the institution responsible for the creation the electronic text. The <publicationStmt> in <sourceDesc> should record the publication information for the original source text.

  5. <date> in <fileDesc> refers to the date which the electronic version was encoded, while the <date> in <sourceDesc> refers to publication or creation date of the original source text.

  6. <idno> in <fileDesc> should refer to numbers associated with the encoded text, while those in <sourceDesc> should refer to the source text (i.e. call no., manuscript no., etc.)

1.2.1. R <titleStmt>

The first element within a <titleStmt> must be <title>. Enter here the main title, or a supplied title in square brackets [ ], followed by the subtitle(s). Separate all subtitles by a space, colon, space (_:_). Titles should end with the subtitle "electronic version".

<titleStmt>      
  <title>A collection of poems : chiefly manuscript, and from living authors : 
electronic version</title>

<titleStmt>
  <title>[Letter to Chol Soo Lee] : electronic version</title>
        

1.2.2. M <author>

Record here the name, in the catalog form, of the author(s), personal or corporate, of the work that has been encoded. Ideally, names entered here should be selected from a national name authority such as the LC Name Authority File. If a personal name authority record cannot be found, it should be entered as prescribed in ACCR2 2nd Ed. Chapter 22 "Headings for Persons (usually Lastname, Firstname form, with the Middle (Initial or Name) and birth/death dates (YYYY-YYYY) added when required for further clarification). If a corporate name heading cannot be found in the authority files, consult ACCR2 2nd ed. Chapter 24 (Headings for Corporate Bodies).

Texts that emanate from multiple authors should include multiple <author> elements. This rule does not apply to anthologies or collections of works formed around a paticular literary theme or form.

<titleStmt>
  <title>[Letter to Chol Soo Lee]</title> 
  <author>Lee, K. W. (Kyung Won)</author>
          

1.2.2.1. ** Optional Use of the <name> element **

Encoders who wish to record names in both catalog form and the direct form (Firstname Lastname) can use the <name> element within <author> element. The catalog form of the name should be encoded using the <name>'s reg=" " attribute. The direct form will be encoded within the <name> element.

<titleStmt>
  <title>[Letter to Chol Soo Lee]</title>
    <author>
	<name reg="Lee, K. W. (Kyung Won)">K. W. Lee</name>
    </author>
          

1.2.3. M <editor>

Record here the name of the editor(s) of the work. Consult national name authority files or, if no authority record exists, ACCR2 2nd ed. to construct a heading.

1.2.3.1. ** Optional Use of the <name> element **

Encoders who wish to record names in both catalog form and the direct form (Firstname Lastname) can use the <name> element within <editor> element. The catalog form of the name should be encoded using the <name>'s reg=" " attribute. The direct form will be encoded within the <name> element.

1.2.4. O <funder>, <sponsor>, <principle>

Should encoders feel the need to use these elements they should follow the same guidelines set out in the <author> and <editor> elements (including the optional use of the <name> element) as they pertain to the form and source of the names used.

1.2.5. R <respStmt>

Group here other individuals or organizations that have contributed to intellectual or artistic content of the work.

All documents should have at least one <respStmt> for the individual responsible for the encoding of the electronic text. Each <respStmt> should contain a least one pair of <resp> and <name> elements. The <resp> element should contain a statement that indicates the nature of the contribution. Each <name> element should contain the name as it appears in on the work. Within <respStmt>, repeat <resp> and <name> for each contributor that is to be included in the description.

1.2.5.1. ** Use of the <name>'s reg=" " attribute. **

Names that are recorded solely in the <respStmt> (those that have not been already entered in catalog form in the <titleStmt>) that encoders wish to have appear as access points in the Dublin Core record (as dc:contributor) should use the <name>'s reg=" " attribute to encode the catalog form of the name. Do not use the reg=" " for names that have been recorded in the <titleStmt> (author, editor, funder, sponsor, principle), since they will be entered as dc:creator (<author>) or dc:contributor (<editor>, <funder>, <sponsor>, and <principle>) in the Dublin Core record (see Appendix B for a Tei Header to Dublin Core Crosswalk).

<titleStmt>. . .
  <respStmt>
    <resp>Encoded by</resp>
    <name reg="Rios, Leigh">Leigh Rios</name>
    <resp>Proofing and Corrections to markup by</resp>
    <name reg="Payne, Charlotte">Charlotte Payne</name>
  <respStmt>
</titleStmt>
            

1.2.6. R <extent>

Record here the approximate size of the TEI XML file to nearest 10 Kb for files under 100 Kb, to the nearest 50 Kb for files over 100 Kb, and to the nearest 100 Kb for files over 1 Mb. Always precede the entry with "ca."

If the encoded text includes images, follow the file size statement with a space, semicolon, space (_:_) and an approximate number of images associated with the file ( ; ca. 1200 images).

<extent>ca. 30 Kb</extent>
<extent>ca. 150 Kb</extent>
<extent>ca. 1.3 Mb</extent>
<extent>ca. 2.2 MB ; ca. 1100 images</extent>
            

1.2.7. R <publicationStmt>

Record here the publication information for the electronic version of the document. Within the <publicationStmt> use <publisher> to encode the name of the person or organization responsible for to production of the electronic text, <pubplace> for the City and State where the publisher is located, <date> for year of the file's creation, and <idno> for any identifying numbers related to the digital text.

1.2.7.1. ** Note On <date> Normalization **

Normalize dates using the value=" " attribute. Use ISO 8601 : 2000 to formulate the attribute value. The following format is recommended YYYY-MM-DD (using 4 digits for years and hyphens between the two digit month and date elements). For example March 6, 1975 would be normalized as value="1975-03-06", April 2004 as value="2004-04-00", and 1942 as value="1942-00-00".

1.2.7.2. R <idno>

An <idno> element that records the CDL System ARK key is REQUIRED for all CDL TEI texts. This <idno> should be qualified with the type="ARK" attribute. Local <idno>'s should use the type="LOCAL" attribute.

<publicationStmt>
  <publisher>University of California, Davis</publisher>
  <pubPlace>Davis, Calif.</pubPlace>
  <date>2004</date>
  <idno type="ARK">ark:/13030/kt8n39p8kw</idno>  
  <idno type="LOCAL">81</idno>
</publicationStmt>
          

1.2.8. O <seriesStmt>

Record here information describing the bibliographic series that the electronic text is a part. At a minimum the <seriesStmt> should include <title>, and <respStmt>. Include an <idno>, using the type="VOL" attribute, if the text is part of a numbered series.

If available, encode the series' homepage using the <xref> element within the <title>. Guidlines for <xref>/<xptr> linking can be found in Section 2.14 of the CDL TEI Base Encoding Guidelines.

<seriesStmt>
  <title>
    <xref href="http://digital.lib.ucdavis.edu/projects/bwrp/index.html"
type="url" rend="new">British Women Romantic Poets</xref>
  </title>
  <respStmt>
    <resp>General Editor</resp>
      <name reg="Kushigian, Nancy">Nancy Kushigian</name>
    <resp>Managing Editor</resp>
      <name reg="Payne, Charlotte">Charlotte Payne</name>
  </respStmt>
  <idno type="VOL">81</idno>
</seriesStmt>
            

1.2.9. R <sourceDesc>

The <sourceDesc> contains bibliographical information pertaining to the original source of the encoded text. Within <sourceDesc>, record bibliographic information in the in the <bibl> or <bibFull> subelement.

R <bibl> or <biblFull>

The choice of bibliographic citation subelement to be used is up to encoders. The <bibl> allows for loosely structured bibliographical data. This option may be more useful for projects dealing with source texts that have not been formally published (such as manuscript materials). The <biblFull> provides for a fully-structured bibliographic citation, in which all components of the TEI <fileDesc> are present. The choice of which type of bibliographical citation is to be used, is up to encoders, project managers, etc.

<sourceDesc>
  <bibl> or <biblFull>
          

1.2.9.1. Guidelines for the use of subelements within <biblFull>

Elements in this section follow the same guidelines as the <fileDesc> unless otherwise noted.

1.2.9.1.1. R <titleStmt>

Must include minimally a <title> child element.

1.2.9.1.2. R <title>

Within the <title> subelement, transcribe the title as it appears in the source document, using "_:_" for each subtitle. Supplied titles should be placed within [ ]'s. Do not include the "electronic version" subtitle.

1.2.9.1.3. M <author> and <editor>

Enter names, personal or corporate, in CATALOG FORM.

Texts that emanate from multiple authors should be encoded using multiple <author> or <elements>.

Optionally: Encoders may use <name> as a child element of <author> or <editor> and its reg=" " attribute to encode both the catalog and direct forms of author names. *NOTE: This optional encoding has no effect on the Dublin Core access points.

<author>Acton, Eliza, 1799-1859</author>
              
1.2.9.1.4. M <respStmt>

Transcribe responsibility statements as they appear in the source text. Statements that describe the nature of the intellectual or artistic contribution should be encoded in <resp>. Names of people or organizations should be placed in <name>. Repeat <resp> and <name> for each contributor.

Optionally: Encoders may use <name>'s reg=" " attribute to encode both the catalog and direct forms of names. *NOTE: This optional encoding has no effect on access points in the Dublin Core record.

<respStmt>
  <resp>By</resp>
  <name>Mrs. Addison</name>
<respStmt>
              
1.2.9.1.5. M <editionStmt>

Using the <edition> subelement, transcribe the edition statement if one appears in the source document.

<editionStmt>
  <edition>3rd ed.</edition>
</editionStmt>
              
1.2.9.1.6. R <extent>

Minimally, enter the number of pages of the source document. If a page approximation if being encoded use "ca." Ideally, encode extent in AACR2 form if available.

<extent>50 p.</extent>
<extent>ca. 600 p.<extent>
<extent>100 p. : ill ; 32 cm</extent>
              
1.2.9.1.7. R <publicationStmt>

Encode the name of the publisher <publisher>, place of publication <pubPlace>, date of publication <date>, and any identification numbers (such as a call number) <idno>.

Materials that have not been previously published (letters, reports, memos, etc.) may not contain publisher or place of publication information. For this reason <date> is the only required element.

Supplied information should be enclosed in [ ]'s. Date approximations should be encoded with a ca. before the date. Dates that are uncertain should be followed by a question mark (?).

1.2.9.1.7.1. ** Note On <date> Normalization **

Normalize dates using the value=" " attribute. Use ISO 8601 : 2000 to formulate the attribute value. The following format is recommended YYYY-MM-DD (using 4 digits for years and hyphens between the two digit month and date elements). For example March 6, 1975 would be normalized as value="1975-03-06", April 2004 as value="2004-04-00", and 1942 as value="1942-00-00".

1.2.9.1.8. M <seriesStmt>

Encode information about the bibliographical series that source text may be part of. Use same <seriesStmt> guidelines as described in the <fileDesc>. For the series <title>, consult national authority files and use the established form of the series title if available.

1.2.9.2. Guidelines for the use of subelements within <bibl>

Encoders using <bibl> have much more flexibility in the how they can construct citations of source texts.

For example, within <bibl>, encoder may transcribe a simple text citation


<sourceDesc>
  <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in
English (Yale, 1990)</bibl>
</sourcedesc>
            

Encoders may also use many of the elements available in the <fileDesc>:


<sourcedesc>
  <bibl>
    <title>TITLE</title>
    <author>
      <name reg="LASTNAME, FIRSTNAME, YYYY-YYYY">FIRSTNAME LASTNAME</name>
    </author>
    <respStmt>
      <resp>Revisions by:</resp>
      <name reg="LASTNAME, FIRSTNAME, YYYY-YYYY">FIRSTNAME LASTNAME</name>
    </respStmt>
    <extent># of pages, leaves, etc.</extent>
    <date value="YYYY-MM-DD">DATE OF CREATION</date>
    <idno type="LOCAL">LOCALLY DEFINED ID#</idno>
  </bibl>
</sourceDesc>
            

1.3. O <encodingDesc>

Institutions should consult specific local guidelines and CDL TEIFORM Guidlines for the encoding of <projectDesc>, <editorialDecl>, <refsDecl>, <samplingDecl>, and <tagsDecl>

1.3.1. O <classDecl>

If keywords from a controlled vocabulary are to be applied to the description the source, they should be declared in the <classDecl> section. For each subject or name thesaurus that is going to be referenced use the element <taxonomy>. Within each <taxonomy> enter a <bibl> element. Finally, embed <title> within the <bibl> tags. Encode the title of the thesaurus in the <title> element.

Use the <taxonomy> attribute id="" to encode an identifier that will allow subject headings (in <textClass>) to be linked to their source thesauri. Repeat <taxonomy>/<bibl>/<title> elements for each controlled vocabulary to be used.

<classDecl>
  <taxonomy id="lcsh">
    <bibl>
      <title>Library of Congress Subject Headings</title>
    </bibl>
  </taxonomy>
  <taxonomy id="lcnaf">
    <bibl>
      <title>Library of Congress Name Authority File</title>
    </bibl>
  </taxonomy>
</classDecl>
          

Encoders who wish to encode local or project defined <taxonomy>'s can do so using the <category> and <catDesc> elements. Like other taxonomy encodings, an id=" " attribute must be encoded so that terms in <textClass> can be linked to their source vocabulary. Use <catDesc> to record a description or title of the thesauri or categorical system.

<classDecl>
  <taxonomy id="DwCollection">
    <category>
      <catDesc>Original UC Berkeley Dynaweb collection structure. July 
2002</catDesc>
    </category>
  </taxonomy>
  <taxonomy id="lcnaf">
    <bibl>
      <title>Library of Congress Name Authority File</title>
    </bibl>
  </taxonomy>
</classDecl>
          

1.4. O <profileDesc>

1.4.1. O <langUsage>

Encode in <profileDesc> one <langUsage>. Embed in each <langUsage> a <language> element for each language that is used.

1.4.1.1. ** Note on <langUsage> **

The <langUsage> element is required when the lang=" " attribute has been used within the <foreign> that requires special fonts, left-right handling, or other special treatment. Encode the name of the Unicode chart (http://www.unicode.org/charts/) needed to render the character data.

<profileDesc>
  <langUsage>
    <language id="el">(Range: 0370-03FF)</language>
    <language id="he">(Range: 0400-04FF)</language>
  </langUsage>
          

1.4.2. O <textClass>

Use <textClass> to wrap <keywords> subelement headings that come from the controlled vocabularies referenced in the <classDecl>. The <keywords> element is always required as the root element for grouping a list of headings from a particular controlled vocabulary. Use the <keywords> attribute scheme="" to identify the thesaurus that is to be used for the list. The value for the scheme="" attribute should be taken from one of the <taxonomy> attribute id=" "'s that were declared in the <classDecl>. Within <keywords> use <list> and its subelement <item> to form a list of headings.

Separate subdivisions with "--" (do not insert spaces between headings and subdivisions " -- ").

<textClass>
  <keywords scheme="lcsh">
    <list>
      <item>Scottish Poetry--Women Authors--18th century</item>
      <item>Scottish Poetry--Women Authors--History and criticism</item>
    </list>
  </keywords>
  <keywords scheme="lcnaf">
    <list>
      <item>Bannerman, Anne, 1765-1829</item>
      <item>Blamire, Susanna, 1747-1794</item>
    </list>
  </keywords>
</textClass>
            

1.5. M <revisionDesc>

Record here any significant changes made to encoding or the content of the file.

1.5.1. M <change>

Record each revision using the <change> element. List all changes in order from most recent to the earliest. Each <change> should include <date>, <respStmt>, <resp>, and <item> in that order. The <item> element should contain an explanation of the revision that has been made to the text.

<revisionDesc>
  <change>
    <date>02/28/2004</date>
    <respStmt>
      <name>Charlotte Payne</name>
      <resp>Project Manager</resp>
    </respStmt>
    <item>Converted SGML to XML</item>
  </change>
  <change>
    <date>06/14/1999</date>
    <respStmt>
      <name>Charlotte Payne</name>
      <resp>Project Manager</resp>
    </respStmt>
    <item>Revised teiHeader</item>
  </change>
</revisionDesc>
          

Minimum and Full CDL TEI HEADERS

STWG Header: Minimum

<teiHeader type="CDL/TEI text type">
  <fileDesc>
    <titleStmt>
      <title>TITLE OF TEXT : ELECTRONIC VERSION</title>
      <respStmt>
        <resp>Text encoder:</resp>
        <name reg="LASTNAME, FIRSTNAME, YYYY-YYYY">FIRSTNAME LASTNAME</name>
     </respStmt>
    </titleStmt>
    <extent>in Kb. or Mb.</extent>
    <publicationStmt>
      <publisher>NAME OF PUBLISHER</publisher>
      <pubPlace>PLACE OF PUBLICATION<pubPlace>
      <date reg="YYYY-MM-DD">DATE OF PUBLICATION</date>
      <idno type="ARK">OAC ARK#</idno>
    </publicationStmt>
    <sourceDesc>
      <bibl>BIBLIOGRAPHIC CITATION</bibl> 
    </sourcDesc>
  </fileDesc>
</teiHeader>
          

STWG Header: FULL

<teiHeader type="CDL/TEI text type">
  <fileDesc>
    <titleStmt>
      <title>TITLE OF TEXT : ELECTRONIC VERSION</title>
      <author>LASTNAME, FIRSTNAME, YYYY-YYYY</author>
      <editor> LASTNAME, FIRSTNAME, YYYY-YYYY </editor>
      <respStmt>
	<resp>by</resp>
	<name>Firstname Lastname of AUTHOR</name>
        <resp>Text encoder:</resp>
        <name reg="LASTNAME, FIRSTNAME, YYYY-YYYY">FIRSTNAME LASTNAME</name>
      </respStmt>
    </titleStmt>
    <editionStmt>ELECTRONIC EDITION STMT</editionStmt>
    <extent>in Kb. or Mb.</extent>
    <publicationStmt>
      <publisher>NAME OF PUBLISHER</publisher>
      <pubPlace>PLACE OF PUBLICATION<pubPlace>
      <date reg="YYYY-MM-DD">DATE OF PUBLICATION</date>
      <idno type="ARK">OAC ARK#</idno>
      <idno type="LOCAL">Local ID#</idno> 
    </publicationStmt>
    <seriesStmt>
      <title>
        <xref href="Series or Collection URL"
type="url" rend="new">SERIES TITLE</xref>
      </title>
      <respStmt>
        <resp></resp>
        <name reg="LASTNAME, FIRSTNAME, YYYY-YYYY">FIRSTNAME LASTNAME</name>
      </respStmt>
      <idno></idno>
    </seriesStmt>
    <sourceDesc>
      <biblFull>
        <titleStmt>
	  <title>TITLE</title>
	  <author>LASTNAME, FIRSTNAME, YYYY-YYYY</author>
          <editor> LASTNAME, FIRSTNAME, YYYY-YYYY </editor>
          <respStmt>
            <resp>By </resp>
            <name reg="LASTNAME, FIRSTNAME, YYYY-YYYY">FIRSTNAME LASTNAME</name>
          </respStmt>
  	</titleStmt>
	<editionStmt>
	  <p> ed.</p>
	</editionStmt>
	<extent>p. : ill. ; cm</extent>
        <publicationStmt>
          <publisher>NAME OF PUBLISHER</publisher>
	  <pubPlace>PLACE OF PUBLICATION<pubPlace>
	  <date reg="YYYY-MM-DD">DATE OF PUBLICATION</date>
          <idno type="LOCAL">LOCALLY DEFINED ID#</idno>  
	</publicationStmt>
        <seriesStmt>
          <title>SERIES TITLE</title>
          <respStmt>
            <resp></resp>
            <name reg="LASTNAME, FIRSTNAME, YYYY-YYYY">FIRSTNAME LASTNAME</name>
          </respStmt>
        </seriesStmt>
      </biblFull>
    </sourceDesc>
  </fileDesc>
  <encodingDesc>
    <projectDesc>
      <p> </p>
    </projectDesc>
    <editorialDecl>
      <p></p>
    </editorialDecl>
    <refsDecl>
	<p></p>
    </refsDecl>
    <classDecl>
      <taxonomy id="CONTROLLED VOCAB ID #1">
        <bibl>
          <title>NAME OF CONTROLLED VOCAB</title>
        </bibl>
      </taxonomy>
      <taxonomy id="CONTROLLED VOCAB ID #2">
        <bibl>
          <title>NAME OF ANOTHER CONTROLLED VOCAB</title>
        </bibl>
      </taxonomy>
      <taxonomy id="LOCAL OR PROJECT DEFINED CONTROLLED VOCAB ID #3">
        <category>
          <catDesc>NAME OF LOCAL OR PROJECT DEFINED CONTROLLED VOCAB</catDesc>
        </category>
      </taxonomy>
    <classDecl>  
  </encodingDesc>
  <profileDesc>
    <creation>
      <date></date>
    </creation>
    <langUsage>
      <language id="el">(Range: 0370-03FF)</language>
    </langUsage>
    <textClass>
      <keywords scheme="ID# FROM ONE OF THE <TAXONOMY ID="">'S">
	  <list>
  	    <item>NAME OR SUBJECT HEADING</item>
          <item> </item>
        </list>
	</keywords>
      <keywords scheme="ID# FROM A SECOND <TAXONOMY ID="">">
        <list>
          <item>NAME OR SUBJECT HEADING</item>
          <item> </item>
        </list>
	</keywords>
    </textClass>
  </profileDesc>
   <revisionDesc>
    <change>
      <date>Date of revision</date>
      <respStmt>
	<name>PERSON RESPONSIBLE FOR REVISION</name>
      </respStmt>
      <item>EXPLANATION OF REVISION</item>
    </change>
   </revisionDesc>
</teiHeader>
      

TEI HEADER to DUBLIN CORE CROSSWALK

The following crosswalk describes the how data encoded in the TEI Header is used to create Dublin Core records that will be used in the texts' Metadata Encoding and Transmission Standard (METS) records. The Dublin Core record will be used witreignhin the METS descriptive metadata section (<dmdSec>)

DC:ELEMENTLOCATION OF DATA IN TEI HEADER
dc:titletei.2/teiHeader/fileDesc/titleStmt/title
dc:creatortei.2/teiHeader/fileDesc/titleStmt/author
dc:subjecttei.2/teiHeader/profileDesc/textClass/keywords/list/item
dc:description
tei.2/teiHeader/encodingDesc/projectDesc
tei.2/teiHeader/encodingDesc/editorialDesc
tei.2/teiHeader/encodingDesc/refsDecl
Others?
dc:publishertei.2/teiHeader/fileDesc/publicationStmt/publisher/publisher and pubplace
dc:contributor
tei.2/teiHeader/fileDesc/titleStmt/editor
tei.2/teiHeader/fileDesc/titleStmt/funder
tei.2/teiHeader/fileDesc/titleStmt/sponsor
tei.2/teiHeader/fileDesc/titleStmt/principle
tei.2/teiHeader/fileDesc/respStmt/name/@reg

(Names from the respStmt will only be pulled in the DC record when the catalog form of the name has been entered in the @reg)

dc:datetei.2/teiHeader/fileDesc/publicationStmt/date
dc:typetei.2/teiHeader/@type (for CDL TEI Form)
dc:formattext/xml
dc:indentifiertei.2/teiHeader/fileDesc/publicationStmt/idno/@type="ARK"
dc:source
tei.2/teiHeader/sourceDesc/bibful/publicationStmt/publisher, pubPlace, and date
tei.2/teiHeader/sourceDesc/bibl
dc:languagetei.2/teiHeader/profileDesc/langUsage/language
dc:relationtei.2/teiHeader/fileDesc/seriesStmt/title OR title/xref/@href="url"
dc:coverageN/A
dc:rights
tei.2/teiheader/fileDesc/publicationStmt/availability
Or does CDL boilerplate this?