Re: Passing (pre-populating) advanced keyword search page

[Karl Fattig <kfattig@xxxxxxxxxx>]

First, Sara Amato is the resourceful person who actually brought this to 
fruition here, with involvement from our Online Public Interface Group 
(OPIG). I should have mentioned that in the earlier email.

We are curious about your question though. Since our script merely 
passes the search (modified or not) on to the innopac server, 
theoretically it shouldn't introduce any problems of its own. Unless, of 
course there were major changes to the values in the form... but we are 
aware of this.

We would like to know more about the kinds of problems others were 
reporting with their quick search forms.

We have only had this up for a couple of weeks, but it has been getting 
use... with no reports of patrons being disadvantaged or error messages.

Karl



Howard Pasternack wrote:
> Karl and Bowdoin are to be once again commended for creativity!  I have 
> a question about this which others might be interested in.  It has been 
> discussed several times on this list that a quick search form needs to 
> have more or less the same html coding as the results screen or problems 
> may result with follow-on searches.  We discovered this here at Brown 
> and several others posted "why is my form doing this" messages all of 
> which got more or less the same answer.  Bowdoin is clearly departing 
> from this model.  Are there any unusual events which occur when a user 
> does some follow-on searching or paging through the results.  -- Howard
>