Difference between revisions of "TEI Header (Mondrian)"

From XML
Jump to: navigation, search
 
Line 1: Line 1:
−
De <teiHeader> bevat de metadata van de brief. In grote lijnen ziet deze er als volgt uit:
+
== The teiHeader ==
 +
The <teiHeader> contains the letter's or manuscript's metadata. In an earlier stage of the
 +
project we used encoding guidelines for the header derived from the [https://ctb.kantl.be/project/dalf/dalfdoc/index.html DALF project].
 +
We switched to a more modern encoding that uses the <correspDesc> element.
 +
The elements of the teiHeader that we use are the:  
 +
* fileDesc
 +
* profileDesc
 +
* revisionDesc
  
 +
This looks as follows:
 
<pre>
 
<pre>
 
<teiHeader>
 
<teiHeader>
−
<fileDesc>
+
  <fileDesc>
−
  <titleStmt></titleStmt>
+
    ...
−
   <publicationStmt></publicationStmt>
+
   </fileDesc>
−
   <sourceDesc>
+
   <profileDesc>
−
  <md:letDesc>
+
     ...
−
     <md:letIdentifier>
+
  </profileDesc>
−
    <idno type="pilot"></idno>
+
  <revisionDesc>
−
    <idno type="letterId"> </idno>
+
     ...
−
    <idno type="whereabouts"> </idno>
+
   </revisionDesc>
−
    <idno type="def"></idno>
+
−
     </md:letIdentifier>
+
−
    <md:letHeading>
+
−
    <author></author>
+
−
    <md:addressee></md:addressee>
+
−
    <md:placeLet attested="yes">Parijs</md:placeLet>
+
−
    <md:dateLet></md:dateLet>
+
−
    </md:letHeading>
+
−
    <md:letPhysDesc>
+
−
    <md:type></md:type>
+
−
    <md:decoration>
+
−
      <md:decoList>
+
−
      <md:decoItem>
+
−
        <md:letDecoDesc></md:letDecoDesc>
+
−
      </md:decoItem>
+
−
      </md:decoList>
+
−
    </md:decoration>
+
−
    </md:letPhysDesc>
+
−
    <md:letContents></md:letContents>
+
−
    <md:envOcc occ=""/>
+
−
  </md:letDesc>
+
−
   </sourceDesc>
+
−
</fileDesc>
+
 
<teiHeader>
 
<teiHeader>
 
</pre>
 
</pre>
  
−
====Some remarks====
+
== The fileDesc ==
 +
A typical fileDersc will contain a fileStmt, a publicationStmt and sourceDesc. The sourceDesc
 +
will contain a msDesc (manuscript description) that contains an msIdentifier detailing the location of the manuscript
 +
as well as alternate identifiers. The msDesc will also contain a physDesc (physical description) that identifies the type of
 +
the manuscript (brief or briefkaart) and describe decoration, if any.
  
−
*<dateLet>: The text of dateLet is what you want to appear in the edition. Attributes indicate the precise date using the when attribute and possible notBefore and notAfter (in this case, the when attribute is what will be used for sorting). In the attributes, the dates are entered as jjjj-mm-dd. 
+
It may look like this:
−
** Single date:
+
<pre>
−
<pre><md:dateLet attested="yes" when="1935-03-13">March 13, 1935</md:dateLet></pre>
+
<fileDesc>
−
** Date range:
+
  <titleStmt>
−
<pre><md:dateLet attested="no" when="1935-03-13" notAfter="1935-03-14"
+
    <title>Briefkaart aan <ref target="bio.xml#MondriaanCarel">Carel</ref> en <ref target="bio.xml#MondriaanLouis">Louis Mondriaan</ref>. Hengelo, maandag 22 oktober 1906 (poststempel).</title>
−
  notBefore="1935-03-13">March 13 or March 14, 1935</md:dateLet></pre>
+
    <editor xml:id="wc">Wietse Coppes</editor>
−
*<publicationStmt>: <authority>Coppes/Jansen</authority>
+
    <editor xml:id="lj">Leo Jansen</editor>
 +
    <sponsor>Mondriaan Editieproject</sponsor>
 +
  </titleStmt>
 +
  <publicationStmt>
 +
    <p>(to be provided later)</p>
 +
  </publicationStmt>
 +
  <sourceDesc>
 +
    <msDesc>
 +
      <msIdentifier>
 +
        <country>Nederland</country>
 +
        <settlement>Den Haag</settlement>
 +
        <institution>RKD</institution>
 +
        <idno>150.558</idno>
 +
        <altIdentifier><idno type="letterId">19061022_MOND_C+L_0012</idno></altIdentifier>
 +
        <altIdentifier><idno type="def"/></altIdentifier>
 +
      </msIdentifier>
 +
      <physDesc>
 +
        <objectDesc form="briefkaart"/>
 +
        <decoDesc>
 +
          <decoNote/>
 +
        </decoDesc>
 +
      </physDesc>
 +
    </msDesc>
 +
  </sourceDesc>
 +
</fileDesc>
 +
</pre>
 +
 
 +
== The profileDesc ==
 +
The profileDesc describes the 'correspondence actions'. For example:
  
−
* Informatie over de decoratie ziet er bijvoorbeeld zo uit:
 
 
<pre>
 
<pre>
−
<decoration>
+
<profileDesc>
−
<decoList>
+
  <correspDesc>
−
  <decoItem id="fig1">
+
    <correspAction type="sent">
−
  <decoDesc>
+
      <name key="56854">Piet Mondriaan</name>
−
    <p>small black/white drawing of a tree</p>
+
      <date when="1906-10-22">maandag 22 oktober 1906</date>
−
  </decoDesc>
+
      <placeName>Hengelo</placeName>
−
  </decoItem>
+
    </correspAction>
−
  <decoItem id="fig2">
+
    <correspAction type="received">
−
  <decoDesc>
+
      <name key="...">Carel Mondriaan</name>
−
    <p>small color drawing of suggested page layout, containing some text</p>
+
      <name key="...">Louis Mondriaan</name>
−
  </decoDesc>
+
    </correspAction>
−
  </decoItem>
+
  </correspDesc>
−
</decoList>
+
</profileDesc>
−
</decoration>
+
 
</pre>
 
</pre>
 +
 +
====About the dating====
 +
 +
The text of <date>  in <correspAction type="sent"> is what you want to appear in the edition. The @when attribute indicates the precise
 +
date; if necessary use @notBefore and/or @notAfter to indicate a range (in this case, the @when attribute is what will be used for sorting).
 +
In the attributes, the dates are entered as yyyy-mm-dd. 
 +
* Single date:
 +
<pre><date when="1935-03-13">March 13, 1935</date></pre>
 +
* Date range:
 +
<pre><date when="1935-03-13" notAfter="1935-03-14"
 +
  notBefore="1935-03-13">March 13 or March 14, 1935</date></pre>
 +
 +
 +
== The revisionDesc ==
 +
The revisionDesc is used to track the progress of the editorial work on the specific letter or manuscript.
 +
 +
 +
 +
====Some remarks====
  
 
The md:type attribute contains the type of document and has one of the values: letter, postcard, telegram (or manuscript, article?)
 
The md:type attribute contains the type of document and has one of the values: letter, postcard, telegram (or manuscript, article?)

Latest revision as of 16:44, 22 January 2020

The teiHeader

The <teiHeader> contains the letter's or manuscript's metadata. In an earlier stage of the project we used encoding guidelines for the header derived from the DALF project. We switched to a more modern encoding that uses the <correspDesc> element. The elements of the teiHeader that we use are the:

  • fileDesc
  • profileDesc
  • revisionDesc

This looks as follows: 

<teiHeader>
  <fileDesc>
    ...
  </fileDesc>
  <profileDesc>
    ...
  </profileDesc>
  <revisionDesc>
    ...
  </revisionDesc>
<teiHeader>

The fileDesc

A typical fileDersc will contain a fileStmt, a publicationStmt and sourceDesc. The sourceDesc will contain a msDesc (manuscript description) that contains an msIdentifier detailing the location of the manuscript as well as alternate identifiers. The msDesc will also contain a physDesc (physical description) that identifies the type of the manuscript (brief or briefkaart) and describe decoration, if any.

It may look like this: 

<fileDesc>
  <titleStmt>
    <title>Briefkaart aan <ref target="bio.xml#MondriaanCarel">Carel</ref> en <ref target="bio.xml#MondriaanLouis">Louis Mondriaan</ref>. Hengelo, maandag 22 oktober 1906 (poststempel).</title>
    <editor xml:id="wc">Wietse Coppes</editor>
    <editor xml:id="lj">Leo Jansen</editor>
    <sponsor>Mondriaan Editieproject</sponsor>
  </titleStmt>
  <publicationStmt>
    <p>(to be provided later)</p>
  </publicationStmt>
  <sourceDesc>
    <msDesc>
      <msIdentifier>
        <country>Nederland</country>
        <settlement>Den Haag</settlement>
        <institution>RKD</institution>
        <idno>150.558</idno>
        <altIdentifier><idno type="letterId">19061022_MOND_C+L_0012</idno></altIdentifier>
        <altIdentifier><idno type="def"/></altIdentifier>
      </msIdentifier>
      <physDesc>
        <objectDesc form="briefkaart"/>
        <decoDesc>
          <decoNote/>
        </decoDesc>
      </physDesc>
    </msDesc>
  </sourceDesc>
</fileDesc>

The profileDesc

The profileDesc describes the 'correspondence actions'. For example: 

<profileDesc>
  <correspDesc>
    <correspAction type="sent">
      <name key="56854">Piet Mondriaan</name>
      <date when="1906-10-22">maandag 22 oktober 1906</date>
      <placeName>Hengelo</placeName>
    </correspAction>
    <correspAction type="received">
      <name key="...">Carel Mondriaan</name>
      <name key="...">Louis Mondriaan</name>
    </correspAction>
  </correspDesc>
</profileDesc>

About the dating

The text of <date> in <correspAction type="sent"> is what you want to appear in the edition. The @when attribute indicates the precise date; if necessary use @notBefore and/or @notAfter to indicate a range (in this case, the @when attribute is what will be used for sorting). In the attributes, the dates are entered as yyyy-mm-dd.

  • Single date:
<date when="1935-03-13">March 13, 1935</date>
  • Date range:
<date when="1935-03-13" notAfter="1935-03-14"
   notBefore="1935-03-13">March 13 or March 14, 1935</date>


The revisionDesc

The revisionDesc is used to track the progress of the editorial work on the specific letter or manuscript.


Some remarks

The md:type attribute contains the type of document and has one of the values: letter, postcard, telegram (or manuscript, article?)

The elements <author> and <addressee> are required to have a @key, which points to a resource about the person mentioned (in this case, the RKDartists inventory)

<author> and <addressee> can also have @attested and @accepted; <placeLet> and <dateLet> can just have @attested. We vullen attested/accepted in. (Attested: expliciet gedocumenteerd; accepted: inductief)

More information on how these elements are used is available in Creating Mondrian: further guidelines

In <letContents>, informations can be organized in one or more paragraphs

, keywords <keywords> or as notes <note>.</s> We probably won't use this. <envOcc> is a required element, with a required @occ, to encode the presence of an envelope.

See also

Retrieved from "https://xml.huygens.knaw.nl/index.php?title=TEI_Header_(Mondrian)&oldid=637"