Print

Print


We addressed the granularity problem in <controlaccess> terms by
embedding the actual subfield codes within the EAD elements:

<subject source="lcsh" rules="aacr2" encodinganalog="650">School 
integration$zWashington (State)$zSeattle</subject>

By using a recursive template in XSLT, we can generate correctly tagged
MARC records from our EAD finding aids while also replacing these codes
with the usual -- for public view using different scripts.  Within
controlaccess, using a character such as $ is pretty safe.  Outside of
controlaccess, I would want to utilize a character that would never be 
used in a normal textual string, so $ wouldn't be safe.  Something like 
the pipe | character would, however, and is often used as an alternative 
to the $ character.

However, we have never tried to embed any subfield codes outside of
controlaccess, although it's doable.  Generally, we have relied on the 
encodinganalog attribute for subfield code mapping and worked around the 
other issues (hand coding when necessary). But it certainly wouldn't be 
hard to incorporate a recursive template into the processing of any 
element that contained embedded subfield codes.


=======================================================
Mark Carlson
Computer Support Analyst
Special Collections Division
University of Washington Libraries
BOX 352900
Seattle, WA, 98195
(206) 543-1929
[log in to unmask]

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

-- 

=======================================================
Mark Carlson
Computer Support Analyst
Special Collections Division
University of Washington Libraries
BOX 352900
Seattle, WA, 98195