> to comprise the response?  Rob originally proposed in his summary:

> termValue
> termFrequency
> displayTerm

> alternativeTerms
> totalTerms                      (I don't understand this)
> CQL for direct access (index and term)

I don't think that these are necessary. I was just quoting from the
various prior proposals rather than advocating them.

> either using the termValue or using the CQL.  There may be more than one
> path (or index) (e.g. authority or bibliographic).  In this case if the CQL

Wouldn't that be two separate databases?
And hence my proposed 'related' tag for explain.
Or if it's indexes then it would be the one specified in the searchClause.

> termFrequency.  It is currently only allowing the equivalent of Z39.50
> globalOccurrences that gives a single count for the term.  It needs to have
> a structure such that it encompasses the occurrence counts for each path (or
> index).

I thought that termFrequency was how many matches a search using the
attribute combination would return for the term.  And you would need to
use the anywhere index to find the count of the term in any index.

> Does the response need to include alternativeTerms?  Isn't this making it a

No :)

> poor man's thesaurus when a proper authority or thesaurus record can be
> retrieved by following the CQL?  Also what purpose does totalTerms serve?

No idea when it's useful to know how many terms are in an index.  Even for
our trick of scanning from beginning to end to create a view of the
database it's not useful as we have to go through it all anyway.

> <By the way>, authority records are of interest to more than just
> cataloguers.  They can provide background information about authors and link
> to photographs and biographies.  There is interesting work being done in

Yep.  See also the EAC initiative.


> this information in the protocol, so what about having an entry in explain
> which points at the related database?
>   <related type="authority"></related>
> should be a more structured way to limit the terms returned.  Perhaps a
> request parameter that carries structureLevel, which would permit limiting

      ,'/:.          Rob Sanderson ([log in to unmask])
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Twin Cathedrals:  telnet: 7777
____/:::::::::::::.              WWW: