The 'index' parameter in scanRequest should be able to take prefixes in
order to resolve properly ala searching.
eg: ">foo=http://www.loc.gov/zing/srw/dc-indexes/ foo.title"
There are two obvious ways to do this:
1) import searchClause from xcql and ignore relation.
2) allow prefixes in the index string
I initially thought that 1 would be the best, but relation is useless.
Also term is required in searchClause, and would not be required for scan
(?) This makes searchClauseType pretty heavy with unnecessary elements so
I prefer the second option.
Which brings me to which parts of Scan should be optional with defaults.
index is required
term is optional, defaulting to the beginning of the term list
numRequested is optional, defaulting to server defined
position is optional, defaulting to first
stepSize and targetDatabase, if included, should definitely be optional.
,'/:. Rob Sanderson ([log in to unmask])
,'--/::(@)::. 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