 |
 |
Actually, the enumerated value "single" was removed in EAD 2002 (partly since a "single" date could be either inclusive or bulk), so now the options are "inclusive" or "bulk". In particular, the examples below could all be encoded as <unitdate type="inclusive">. Tim Date sent: Mon, 8 Mar 2004 13:42:12 -0800 Send reply to: Encoded Archival Description List <[log in to unmask]> From: Jocelyn Gibbs <[log in to unmask]> Subject: unitdate TYPE attribute question To: [log in to unmask] > How should the TYPE attribute be interpreted/applied to <unitdate>. Are we describing the date or the material? Examples: > > <unitdate>1924</unitdate> > a folder with multiple items all from the year 1924. TYPE = "single" or "inclusive" > > <unitdate>n.d.</unitdate> > a folder with multiple undated items. TYPE = "single" or "inclusive" > > <unitdate normal = "1800/1900">[18--]</unitdate> > 1 single item. TYPE = "single" or "inclusive" > > <unitdate>ca. 1920/1925</uitdate> > 1 single item. TYPE = "single" or "inclusive" > > We can find no guidance in Tag Library, OAC BP, RLG BP, etc.