Hi Michele,
Thanks for the example. I think <archref> is used in more specific circumstances -
Extref: A linking element that can include text and subelements as part of its reference to an electronic object that is external to the EAD document.
Archref: A reference element that provides a citation and/or an electronic link to separately described archival materials of special interest. Examples of such materials include a record group and one of its large series (which might have separate EAD-encoded finding aids) and a general reference to a collection with similar content.
So <archref> is the right one to go for. Did you use any attributes other than href?
Cheers,
Jane.
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]]
> On Behalf Of Michele R Combs
> Sent: 19 May 2008 21:29
> To: [log in to unmask]
> Subject: Re: Linking to sections of an EAD finding aid
>
> We've done this in order to link to, for example, excel
> spreadsheets for collections whose information seems better
> represented that way. I can't recall if we have used archref
> or extref -- I know we use archref to link to finding aids
> for related collections, but I think we use extref for more
> detailed information (I need to brush up on the differences
> between the two tags...). For an example, see the American
> Book Company records,
> http://library.syr.edu/digital/guides/a/amer_book_co.htm and
> look either under "Related Finding Aids" or under General
> Correspondence, Books, or Illustrations. We chose to do
> these as spreadsheets to allow researchers to sort the
> information bu author, title, subject, or publication date.
>
> Michele
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]]
> On Behalf Of Jane E. Stevenson
> Sent: Monday, May 19, 2008 12:03 PM
> To: [log in to unmask]
> Subject: Linking to sections of an EAD finding aid
>
> Hi there,
>
> At the UK Archives Hub we are thinking about breaking up long
> descriptions in order to make them easier to navigate through
> and to address the problem of huge files (sometimes 4-5 Mb and over).
>
> The idea is that a link within the EAD record could take the
> user to a more detailed description - for example a
> description of a component within <dsc> or a description of a
> child record. This type of link would use <archref> but it
> would be useful for us to find out if any other repositories
> have linked to fuller descriptions in this way and how they
> have used <archref> attributes to do this.
>
> Many thanks,
> Jane.
>
>
|