Thanks,

I think that's what I have to do, just make a new 
index "standardIdentifier" that includes ISBN, ISSN and marc.001. That 
will solve my problems although I haven't got a method to formally explain 
the association between the indexes. After all, what's the benefit of a 
formal explanation in this case? The server should be able to handle a 
separate index. 

  Regards RogerW. 


>Roger,
>Standard Identifier is really a separate index for most servers.
>For LC, for example, Standard Identifier includes ISBN, ISSN,
>as well as LCCN.  While is it also possible to search each of
>those separately.
>
>  <index id="7">
>    <title>isbn</title>
>      <map>
>        <name set="bath">isbn</name>
>      </map>
>  </index>
>  <index id="8">
>    <title>issn</title>
>      <map>
>        <name set="bath">issn</name>
>      </map>
>  </index>
>  <index id="9">
>    <title>lccn</title>
>      <map>
>        <name set="bath">lccn</name>
>      </map>
>  </index>
>  <index id="1007">
>    <title>standardIdentifier</title>
>      <map>
>        <name set="bath">standardIdentifier</name>
>      </map>
>      <map>
>        <name set="dc">resourceIdentifier</name>
>      </map>
>  </index>
>
>It's complicated because the Standard Identifier search is
>part of the Bath Profile, but the ISBN and the ISSN searches
>are part of the US Profile which is an extension to Bath.
>
>http://www.niso.org/standards/resources/Z39_89final.pdf
>
>We support both with the "bath" prefix.
>(I also see that LC is not current with regard to the
>appropriate name for the DC identifier -- we still use
>"dc.resourceIdentifier" and don't yet support "dc.identifier".)
>
>Hope that's somewhat helpful.
>Larry