Bah.

Actually, the easiest way to parse the prefixes and index is probably to
use a CQL parser to create a search clause.

Secondly, we need the relation and relation modifiers to determine which
terms to return.  For example:

dc.title any/stem fishes
dc.title exact fishes

as searches will be very different, and hence scan will need them as well
to know what to return.

So, we should put a <searchClause> into scanRequest. Meaning that we need
also need a string version for SRU and XCQL-challenged SOAP clients.

Say ... searchClause and xSearchClause ?

Rob

--
      ,'/:.          Rob Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Twin Cathedrals:  telnet: liverpool.o-r-g.org 7777
____/:::::::::::::.              WWW:  http://liverpool.o-r-g.org:8000/
I L L U M I N A T I