[ List Archives Home ] [ Thread index for 2008 ]
[ Date index for 2008 ]
[ Author index for 2008 ]
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
- Date: Fri, 12 Sep 2003 08:48:24 -0400
- From: Howard Pasternack <Howard_Pasternack@xxxxxxxxxx>
- Subject: Re: Passing (pre-populating) advanced keyword search page
On our system we initially did a form which on the Innopac mainmenu screen
which did not contain the exact same html coding as the Innopac results
screen. During testing everything seemed fine. However, we discovered
after about a week or so that the Innopac would output results screen which
were badly mangled with pieces of the toplogo appearing at the bottom of
the screen. We also got nohits on the AVS search when there were hits. It
was all random; nothing was replicable on the same search on the same
machine or different machines. The failures occured on less than 5% of the
searches. At first we thought there was a problem with the browser but
when it got reported by staff on more than one machine we knew there was a
problem. Changing the coding of the form solved the problem. -- Howard
At 05:06 PM 9/11/2003 -0400, you wrote:
>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
>
>--
>This message was distributed through the Innovative Users Group INNOPAC list
>Public replies: INNOPAC@xxxxxxxxxx
>Update your subscription options:
>http://innopacusers.org/list/listinfo/innopac