I agree with Mark's conclusions here. Seems like you'd only use the
<dao> at the point in the finding aid where you're actually describing
the image as a component in a multilevel collection description, so
somewhere in a <c0x> component. Once it is described and has an id and
description within the context of the finding aid, it seems logical to
use an <extptr> to embed it for illustrative purposes elsewhere in that
same, or a different, finding aid.
Mark Carlson wrote:
>Personally, after seeing the proposed solutions, I would opt to just use
><extptr>. Especially in a case where presentation is the final result and
>you are probably going to have a mixture of <dao> or <extptr> depending on
>whether the items displayed are from the collection of materials being
>described. Looking over <dao> in the EADTL, it states that it is to be
>used "...to connect the finding aid information to electronic
>representaions of the described materials". This seems to imply that the
><dao> will somehow be a representation of the textual context in which it
>occurs, which may or may not be the case.
>The images may be part of the collection described, but they may not
>necessarily be related to the *information* being conveyed. The images
>may be for presentation purposes only, so tagging them as <dao> vs.
><extptr> may not be as important if you don't need (or desire) to maintain
>a relationship between the DAO and the textual context in which it occurs.
>I suspect that this was one of the main purposes for creating the
>distinction between DAO vs. other links in the first place.
>Interesting discussion. Thanks for your comments.
| Bill Landis
| Manuscripts Librarian, Special Collections and Archives
| The UCI Libraries, University of California
| P.O. Box 19557, Irvine, CA 92623-9557
| 949 824.3113 Voice | 949 824.2472 Fax
| [log in to unmask]