On Wed, 2006-05-03 at 15:32 -0700, Mark Carlson wrote:
> 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>

But this leaves MARC specific code in the actual text of the finding
aid. This is not a good approach from an interoperability point of view.

An approach recommended for use in the Archives Hub (UK is to wrap the marc subfield analogs in
emph tags and apply an altrender attribute to specify which marc
subfield they apply to. e.g.

<subject source="lcsh" rules="aacr2" encodinganalog="650">School
integration <emph altrender="z">Washington (State)</emph> <emph

If you do this, you don't need to worry about stripping the subfield
codes in non-MARC oriented output.

Relating back to the original question, maybe altrender attributes could
be used to tag subfields of the MARC 530 field.

John Harrison

Special Collections and Archives
University of Liverpool Library
Chatham Street, PO Box 123, Liverpool, L693DA
e: [log in to unmask]
t: 0151 7943142
f: 0151 7942681