<chronitemset> is a new element in EAD3, used in place of the deprecated <eventgrp> within a <chronitem> element. It allows multiple places and/or locations to be combined with a single date.
Without its use, <chronitem> must contain a single <event> and up to one <geogname>. <chronitemset> pairs the date element in <chronitem> with one or more <event> elements and zero or more <geogname> elements. If more than one event or more than one <geogname> should be included in a <chronitem>, <chronitemset> must be used.
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.
- @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
<chronitemset> must contain at least one <event> element. It may then contain a) further <event> elements, or b) further <event> elements and a <geogname> element, or c) multiple <geogname> elements (even if only a single <event> element is used). See below for examples of cases when it needs to be used:
In these cases, chronitemset does not need to be used:
- chronitem: some kind of date, geogname, event
- chronitem: some kind of date, event
However chronitemset must be used in the following cases:
- chronitem: some kind of date, (chronitemset: event, event)
- chronitem: some kind of date, (chronitemset: geogname, geogname, event)
- chronitem: some kind of date, (chronitemset: geogname, event, event)
- chronitem: some kind of date, (chronitemset: geogname, geogname, event, event, etc.)
Note on use order: In the case that <geogname> is used in tandem with <event>, <geogname> must be used first (including within regular <chronitem>). However, <geogname> is also available within <event>.
- <geogname> (may be repeated)
- <event>* (may be repeated)
Example
<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> |