Roger Wallin writes:
> 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.
Exactly. So far as the client is concerned, they _are_ all just
separate indexes. If a client explicitly wants to search on both ISBN
and ISSN, then it can just use
issn=123456789 or isbn=123456789
If you invent a new index, remember to put it in a context set that is
identified by a URI that you have responsibility for. In my case, for
example, I might define the Vertebrate Palaeontology context set with
URI http://miketaylor.org.uk/cql/vp/1.0 and then use
vp.age=Kimmeridgian and vp.taxon=Sauropoda
_/|_ ___________________________________________________________________
/o ) \/ Mike Taylor <[log in to unmask]> http://www.miketaylor.org.uk
)_v__/\ "Why does man kill? He kills for food. And not only food:
frequently there must be a beverage" -- Woody Allen, "Without
Feathers"
|