>
> Has anyone experimented with using the encodinganalog attribute for the
> various EAD elements with a view to possibly extracting a MARC record (or
> most of a MARC record) from an encoded finding aid. As we have developed
> a template for encoding Bentley Library finding aids we have tried to map
> appropriate EAD elements to MARC fields. For example, were are using
>
> <ARCHDESC>
> <DID>
> <origination> mapped as MARC 100/110
> <unittitle> mapped as NARC 245 del-a
> <unitdate> mapped as MARC 245 del-f
> <physdesc><extent> mapped as MARC 300
> </DID>
>
> The <controlaccess><corpname|persname|subject> tags are mapped to MARC
> 600/610 and 700/710 as appropriate with source= attributes
>
>
> Some of these are obvious analogs but problems arise when an EAD element
> cannot contain a sub-element comparable to a MARC sub-field, e.g,
> <corpname> can contain <subarea> but <persname> cannot contain a <date>
>
> What we have not been able to figure out is exactly how the encodinganalog
> attibute is supposed to be used. The Gilliland-Swetland/LaPorte EAD
> Applications Guidelines suggests possibilities but offers no practical
> instruction. Few of the finding aids I have looked at on-line have used
> the encodinganalog attribute. If anyone has given this matter any
> thought or experimented with a script to extract a MARC record I would
> appreciate hearing from you.
>
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> | Greg Kinney e-mail: [log in to unmask] |
> | Bentley Historical Library phone: (313) 764-3482 |
> | University of Michigan fax: (313) 936-1333 |
> | 1150 Beal Ave. |
> | Ann Arbor, MI 48109 |
> | _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _|
>
>
|