Re: /search/X? urls and default search options (adjacency, and ...)

[Elizabeth Thomsen <et@xxxxxxxxxx>]

We had the same experience, and found we had to add the "&SORT=D" to all
URLs, too.  And we've found it problematic for all the same reasons.  We
had lots of booklists out there with w? links that needed to be changed
to X? links, a task made more complicated by the need to add that SORT
thing to all those URLs.  

No solution to offer, just confirming that you're not alone!

Elizabeth

-- 
Elizabeth Thomsen, Member Services Manager
NOBLE: North of Boston Library Exchange
Danvers MA 01923
et@xxxxxxxxxx

On Fri, 26 Mar 2004 16:58:07 -0500 Sara Amato wrote:

> In constructing urls to do Adv. Keyword searches, we came across the 
> following oddity:
> 
> If we make a simple URL such as:
> 
> http://phebe.bowdoin.edu/search/X?imperialism+india
> 
> the system defaults to an OR search, searching imperialism OR india. 
> This is NOT the default when searching directly in the webpac.  We 
> discovered if we added even one of the other parameters on, such as 
> SORT, e.g.
> 
> http://phebe.bowdoin.edu/search/X?imperialism+india&SORT=D
> 
> the system did the "right thing" and first tried and adjacency search, 
> and failing that moved onto an "and" search.
> 
> While this isn't really a problem, we can of course add the SORT or 
> other values on to the url, it is sort of a mystery to us.  We had been 
> teaching faculty and librarians that they could construct URLs to search 
> the catalog using the simple /search/indextag?search+words structure.
> 
> Anyone have any thoughts on this and why it works this way?
> 
> 
> --
> This message was distributed through the Innovative Users Group
> INNOPAC list
> Public replies:  INNOPAC@xxxxxxxxxx
> Update your subscription options:
> http://innopacusers.org/mailman/listinfo/innopac