One thing you might have missed is escaping the query URL. "&" and ":"
characters will need escaping in your query string, so instead of

&q=Wants&[Sufficiency]:SU

you would need

&q=Wants%26[Sufficiency]%3ASU

Let me know if this doesn't solve your problem and I'll look into it
further.

Regards,

Michael

Bradley Wangia wrote:

>I've followed the suggested steps outlined for context search to no avail
>1. Set up hierarchy classifier based on the subject
> Used MGPP by enabling advanced searching in GLI
> Set up ex.subject and text in the index
>2. I've changed the interface to only display the form on the
>appropriate pages.
>3. I've used javascript to find out which node is open.
>4. I've also used javascript to create a search string that appends the
> keywords entered by the user to the normal search string
> &q=Wants&[Sufficiency]:SU
>
>However, my searches return results that are global to the collection.
>I've experimented with my form's hidden fields the current settings are
>
><form name=QueryForm method=get
>onsubmit="window.open(buildQueryURL(this.q1.value, this))" action="">
><input type=hidden name="a" value="q">
><input type=hidden name="r" value="1">
><input type=hidden name="b" value="1">
><input type=hidden name="hs" value="1">
><input type=hidden name="e"
>value="p-0-00-ssl--00-1-0--0prompt-10---4------0-1l--1-en-50---20-about---00011-001-1-0utfZz-8-00">
><table align="right">
><tr><td> Search documents in this category</td></tr>
><tr><td>
><tr><td><nobr><input name="q1" type="text" id="tbox" value="" size="25">
></td></tr>
><tr><td>
>
><input type="submit" value="Begin Search" ></nobr>
>
></td></tr></table>
>
></form>
><!-- end of query form -->
>
>I suspect that my compressed arguments, e, is the cause of my undoing.
>How do I decipher compressed arguments ...
>
>Also could I use cgiargcl to tell the search engine where in the
>hierarchy to find the document I am searching for?
>
>
>On 5/17/05, Katherine Don <kjdon@cs.waikato.ac.nz> wrote:
>
>
>>Hi Bradley
>>
>>This is not something that we currently support. However, we think you
>>should be able to implement it by doing something like the following
>>example.
>>
>>The example is a subject hierarchy based on dc.Subject metadata, which,
>>once the user has browsed to a node, they can search the full text of
>>documents in that node for some terms which they enter.
>>
>>1. set up the collection classifiers and indexes.
>>You'll need a hierarchy classifier on dc.Subject.
>>for the indexes, you'll need to use mgpp - in the GLI, enable advanced
>>searching. you need to have dc.Subject and text in the index.
>>
>>2. change the interface. You'll need to add a little search form onto
>>the classifier page - in gsdl/macros/document.dm, in the

oops