Hi Richard,

Thanks for your suggestion.

I should have mentioned in my original email that we intend to serve the
files on the archives hub, and consequently it is not the files we need
to link but the none static urls that are created by the hub software.

I do however intend to link the files using <eadgrp> although I have
never used this before. Has anyone had any experience of using <eadgrp>?
thanks again
Roy


Archivist

Special Collections and Archives
Sydney Jones Library
University of Liverpool
PO Box 123
Liverpool
L69 3DA

tel: 0151 794 2696

http://sca.lib.liv.ac.uk/collections/index.html


On Thu, 23 Sep 2004, Richard Davis wrote:

>Roy Lumb wrote:
> > Hello,
> >
> > I am working on a large electronic finding aid, which has been split up
> > into 52 separate ead files. I would like to link these files together
> > as they represent one archival collection. The obvious choice to link
> > these files would be using <extref> and then using the entityref
> > attributes.
> >
>
>Hi Roy
>
>Why not instead use the HREF attribute of <extref>, with the filename of
>the target file *relative* to the starting file?
>
>Keep the target files in the same directory as the starting document, or
>a subdirectory thereof, and that ought to be enough to forge meaningful,
>navigable relationships between them.
>
>Generally, XML and HTML s/w I've used copes fine with relative
>addresses, i.e. "look in the current directory first". If the files ever
>go on a web server in the same arrangement, the links will still be
>meaningful, though you might then choose to do a global replace to
>prepend the full path.
>
>This would be (has been) my approach, so if it's completely
>wrong-headed, I hope someone will put me straight!
>
>Richard
>
>--
>/
>\ Richard M Davis
>/ Digital Archives
>\ University of London Computer Centre
>/ Tel: +44 (0) 20 7692 1350
>\ mailto: [log in to unmask]
>/
>