MacKenzie,
here at Yale, we found it useful to have <head> in <note> too, to
allow some flexibility for squeezing in an 'Overview' section at the
beginning of finding aids in two of our repositories. Taking out the
<head> element certainly isn't an error, it was a deliberate and
documented change in the beta dtd. I'm not clear why.
The good news is that there is way to work around this. You can
display a heading for a <note> element by displaying the value of its
'label' attribute. So instead of something like
<note>
<head>Further Information</head>
...
</note>
you can use the more compact, but more involved
<note label="Further Information">
...
</note>
and then specify in the style sheet that if the label attribute for a
note element is assigned, it should be displayed as a heading.
----
David L. Clough
Reference Assistant, Yale Divinity Library
409 Prospect Street, New Haven CT 06511, USA
email [log in to unmask] tel. (203) 432-5289
MacKenzie Smith wrote:
>
> Hi,
>
> I'm writing a conversion program for an old DataEase database into
> EAD-encoded finding aids, and need to use <note> elements for
> general purpose fields that probably should go into <bioghist> or
> <scopecontent> kinds of elements but can't because we don't know
> for sure without manually looking at their contents. In the draft
> tag library it says you can have <head> elements in <note>s, and
> an earlier beta version of the DTD allowed this, but the newest
> one does not. Was that a conscious decision? Or a mistake in the
> new DTD? It seems pretty useful to me to have headings available
> in note elements, don't you think?
>
> _____________________________________________________________________________
> MacKenzie Smith [log in to unmask]
> Office for Information Systems (617)495-3724
> Harvard University Library %\%\%\%\%\%\%\%\%\%\%\%\%\%
> -----------------------------------------------------------------------------
|