With a little trouble, your stylesheet that converts EAD to MARC could be adjusted to add some of the granularity you're seeking, especially with your recusive use of <altformavailable>
Conisdering adding these additional encodinganalog attributes to drive the transformation.
<altformavail id="a17" encodinganalog="530">
<head>Alternative Forms Available</head>
<altformavail type="microfilm" encodinganalog="530$3">
<p encodinganalog="503$a">The collection is available on 35 mm microfilm reels xxxx-xxxx at
Archives of American Art offices, and through interlibrary loan.</p>
</altformavail>
<altformavail type="digital" encodinganalog="530$3">
<p encodinganalog="503$a">Portions of the collection have been digitized and digital surrogates are
hyperlinked to this finding aid in the Container List below.</p>
</altformavail>
</altformavail>
Actually, you may not even need to add these additional encoding analogs.
If there is a @TYPE attribute in every instance of altformavail/altformavail, one can by default automatically map the value of @TYPE to MARC 530$3.
If the contents of every altformavail/altformavail/p goes into MARC 530$a, then the stylesheet can automatically make that transfermation as well.
If every situation is consistent and predicable, a lot can be done by default though this approach carries an obvious risk.
Michael
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]]On Behalf Of
Chris Prom
Sent: Wednesday, May 03, 2006 3:54 PM
To: [log in to unmask]
Subject: Re: mapping <altformavail> to MARC
Stephanie,
I looked into this issue as part of a project I am currently
working on. The essential probelem is that the EAD encoding
analog does not allow as much granularity as the subfield
indicators in MARC allow on the 530 field. ($3=materials
specificed; #c=availablity conditions, $u=url,etc). So in the
end we decided the best one could do is something very similar to
what you are suggesting, e.g. just mapping the whole content of
the <altformavail> element over to the 530 element, without
further specification.
Thanks,
Chris
--
Christopher J. Prom
Assistant University Archivist
University of Illinois Archives
19 Library
1408 W. Gregory Dr.
Urbana, IL 61801
phone: 217.333.0798
fax: 217.333.2868
e-mail: [log in to unmask]
web: http://web.library.uiuc.edu/ahx
On Wed, 3 May 2006, Stephanie Ashley wrote:
> Hello all,
>
> We regularly use <altformavail> to mention the availability of microfilm and
> digital surrogates of our collections and we're attempting to improve the
> way our EAD finding aids map to MARC. Can anyone share examples of how
> they've used type attributes (or any other method) to differentiate between
> types of available alternative formats for their collections within one
> <altformavail> element? Also, has anyone used 530 subfields in their
> encoding of this element and if so, how?
>
> Currently we're thinking about something like this, and although it parses
> correctly I'm wondering if it's okay. Could I just repeat the encodinganalog
> with an appropriate subfield (if there is one?) inside the <altformavail
> type=""> tags?
>
> <altformavail id="a17" encodinganalog="530">
> <head>Alternative Forms Available</head>
> <altformavail type="microfilm">
> <p>The collection is available on 35 mm microfilm reels xxxx-xxxx at
> Archives of American Art offices, and through interlibrary loan.</p>
> </altformavail>
> <altformavail type="digital">
> <p>Portions of the collection have been digitized and digital surrogates are
> hyperlinked to this finding aid in the Container List below.</p>
> </altformavail>
> </altformavail>
>
> Thanks in advance for any help you can offer.
>
> Stephanie Ashley
> Archives of American Art
> Smithsonian Institution
>
|
