<chronitem> Chronology List Item

<chronitem> is a formatting element which keeps a date/date range/date set paired with an associated event or group of events and possibly geographic locations within <chronlist>. Each instance contains a choice of <daterange>, <dateset>, or <datesingle> coupled with either an <event> and optional <geogname> or coupled with one or more <chronitemset> to handle multiple places or events combined with the date/s.

Attributes

  • @altrender – not required. Use if the content of the element should be displayed or printed differently than the rendering established in a style sheet for other occurrences of the element.
  • @audience – not required. Use to set whether the element’s contents will be visible to external users or to internal ones. Possible values are: “internal” and “external.”
  • @id – not required. Creates an ID for element. Can be used for linking.
  • @lang – not required. Three-letter code that indicates the language in which the element’s contents were written. It should come from ISO 639-2b.
  • @localtype – not required. This attribute may be used within a number of elements. Its use and values are not defined by the schema and may be defined locally.
  • @script – not required. Four-letter code that indicates the script in which the element’s contents were written. It should come from ISO 15924.

Child Elements

Data within <chronitem> requires some form of date, either: <daterange>, <dateset>, or <datesingle>. This date must then be combined with either a) an <event> and optionally a <geogname> or b) one or more <chronitemset> elements.

Note on use order: In the case that <geogname> is used in tandem with <event>, it must be used first (including within <chronitemset>). However, <geogname> is also available within <event>.

Examples

<custodhist>
  <head>Custodial History</head>
  <chronlist>
    <chronitem>
      <daterange>
        <fromdate standarddate="1978">1978</fromdate>
        <todate standarddate="1989">1989</todate>
      </daterange>
      <chronitemset>
        <event>Materials held by faculty members.</event>
        <event>Materials collected by departmental secretaries as informal archive</event>	      
      </chronitemset>
    </chronitem>
    <chronitem>
      <datesingle>1989</datesingle>
      <event>Departmental Records Collection Initiative conducted by <corpname normal="University Archives, Piecemaking University"><part>University Archives</part></corpname></event>
    </chronitem>
    <chronitem>
      <daterange>
        <fromdate standarddate="1989">1989</fromdate>
        <todate notbefore="2020">2020</todate>
      </daterange>
      <event>Records held by University Archives</event>
    </chronitem>
  </chronlist>
</custodhist>

Changes from EAD 2002

<chronitem> gained attributes @lang, @localtype, and @script. It got much more complex and faceted by breaking the date down into <datesingle>, <daterange>, and <dateset> as well as the allowing optional <geogname>. It lost the deprecated <eventgroup>, but replaced it with <chronitemset>, which allows for pairing of events and/or places.

EAD3 Tag Library Entry

View the official tag library entry for <chronitem>