We routinely encode multiple accessions into a single finding aid. Our
encoding at the <c01> level is thus:
<c01 level="otherlevel" otherlevel="accession">
A standard HTML example can be found here:
http://www.lib.washington.edu/specialcoll/findaids/docs/uarchives/UA18_10_3252SteinbrueckVictor.xml
We are also in the process of implementing and tweaking DLXS, and that
example can be found here:
http://tinyurl.com/yhdcv2c
I'm not sure why this causes problems with your OPAC link. We basically
link from a single bibliographic record in our OPAC to the finding aid.
We don't change the name of the filename when we add a new accession
which is the real key to not having to update your links when the file
changes. Here is how the link from the bibliographic record looks:
http://catalog.lib.washington.edu/record=b4470625
Mark
Ferry, Jacquelyn M - WHS wrote:
>
>
> Hi all,
>
>
>
> We’re beginning to encode collections with multiple accessions (some
> “processed” and some “unprocessed”—we’ve been a minimum processing
> institution for over 12 years so the line is a bit blurry). In any case,
> we’ve routinely created separate finding aids for each new accession
> that comes in, rather than amending the original finding aid. I’m
> looking for examples from other institutions that are attempting the
> same thing. My preference would be to amend the original EAD finding aid
> to include all accessions, but this gets messy when linking to/from our
> OPAC. Does anybody have any good examples to share? I’d be especially
> interested to hear from any DLSX users.
>
>
>
> Thanks,
>
> Jacqie
>
>
>
> Jacquelyn M. Ferry
>
> Cataloging Archivist and EAD Coordinator
>
> Wisconsin Historical Society
>
> 816 State Street
>
> Madison , WI 53706
>
> Phone: (608) 264-6453
>
> Email: [log in to unmask]
> <mailto:[log in to unmask]>
>
> Website: www.wisconsinhistory.org <http://www.wisconsinhistory.org>
>
>
>
> Collecting, Preserving and Sharing Stories Since 1846
>
>
>
>
>
|