[ 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]
Thank you Maurine,
I think it is a system-wide problem using the advanced search token.
Don Zhou
William Mitchell College of Law
-----Original Message-----
From: innopac-bounces at innopacusers dot org
[
mailto:innopac-bounces at innopacusers dot org] On Behalf Of Maurine McCourry
Sent: Friday, November 17, 2006 11:29 AM
To: IUG INNOPAC List
Subject: RE: [IUG] RightResults problem?
I opened one this morning. Call number is c955824. We're using WebPAC
Pro and are seeing the problem. Here's the text of my problem report:
Advanced searches using more than one search box are not being grouped
with parentheses. The example given yesterday on the IUG listserv
illustrates the problem in our system, too: Enter "Russia or soviet or
USSR" in the first search box on the advanced search page, and enter
"woman or women" in the second search box, leaving the connecting
Boolean "and" selected from the dropdown menu. The search that results
is "Russia or soviet or USSR and woman or women", when it should be
"(Russia or soviet or USSR) and (woman or women)". Seems to be a
problem with the tokens on the search page.
Maurine McCourry
Technical Services Librarian
Hillsdale College, Mossey Library
maurine dot mccourry at hillsdale dot edu
-----Original Message-----
From: innopac-bounces at innopacusers dot org
[
mailto:innopac-bounces at innopacusers dot org] On Behalf Of Sue E Boggs
Sent: Friday, November 17, 2006 11:58 AM
To: IUG INNOPAC List
Subject: RE: [IUG] RightResults problem?
Interesting that it isn't working on your 2006 catalog Bob. I just tried
ours (2006 1.1) and it works fine, adding the parentheses as it should.
We are still using the 2005 javascript for the Advanced Keyword page.
Did you update to the 2006? I was looking at some different Pro sites
and it seems there are a few different versions (dates) of the X page
out there.
That does give me some hope that if we go Pro at the end of finals but
don't make any changes to the live files, which is the tentative plan,
things will be fine while we work out the bugs in staging with our new
design.
Since I'm not actually Pro yet I feel odd opening a call about this.
Would someone else like to do it?
Sue
Sue Boggs
Cataloging & Library Technician
Technical Services
Library
University of Puget Sound
1500 N. Warner St. #1021
Tacoma, WA 98416-1021
(253) 879-2667
boggs at ups dot edu
-----Original Message-----
From: innopac-bounces at innopacusers dot org
[
mailto:innopac-bounces at innopacusers dot org] On Behalf Of Bob Duncan
Sent: Friday, November 17, 2006 7:45 AM
To: IUG INNOPAC List
Subject: Re: [IUG] RightResults problem?
At 05:55 PM 11/16/2006 -0800, David wrote:
> >>> "Sue E Boggs" <boggs at ups dot edu> 11/16/2006 4:25 PM >>>
>On the Advanced Keyword page input in the first search box Russia or
>soviet or USSR leave the Boolean connector at AND and input in the
>second search box woman or women.
><<<
>
>A properly nested version of this submitted from the Main Menu search
>form on the WWU site does work (280 hits):
>
>(russia or soviet or USSR) and (women or woman)
>
>
http://lis.wwu.edu/search~/a?searchtype=X&searcharg=%28russia+or+soviet
+or+USSR%29+and+%28women+or+woman%29&SORT=D
>
>
>On the srchhelp_X.html page, though, the part of the Javascript that is
>supposed to catch boolean operators in the search string appears to be
>working, but only on the modify search page loads and not on the
submits
>of a new blank form search. . . .
Oooo, this is nasty. Couple of observations:
(1) We are on Release 2006 but not WebPAC Pro, and our advanced keyword
search results reflect the same behavior as the problem results that Sue
reported at the two Pro sites, so it's not a RightResults issue.
(2) Paula Hammett reported that the search is working correctly at
Sonoma State. I tried some "fresh" advanced searches there and the
parentheses
are automatically inserted where they should be.
(3) I could swear that prior to our Release 2006 upgrade the parens
were automatically inserted in advanced keyword searches. Not only are
they not being inserted now, but when I modify a search that contains
Boolean operators the terms are split out into separate text input
elements on the search form. And even if I use parens on the search
screen, the terms are still split out into separate inputs when the
search is modified.
(4) When we upgraded to R2006 I edited my srchhelp_X file to use the
"advancedsearchbody" and "advancedsearchformbegin" tokens, which is
where the Javascript comes from, so I'm guessing there's something amiss
with the scripts called by these tokens?
Paula---it appears that perhaps you're not using tokens to create the
search form and call the scripts? Could you share how your page is
coded?
Bob Duncan
~!~!~!~!~!~!~!~!~!~!~!~!~
Robert E. Duncan
Systems Librarian
Editor of IT Communications
Lafayette College
Easton, PA 18042
duncanr at lafayette dot edu
http://www.library.lafayette.edu/
--
This message was distributed through the Innovative Users Group INNOPAC
list Public replies: INNOPAC at innopacusers dot org Update your subscription
options:
http://innopacusers.org/mailman/listinfo/innopac
--
This message was distributed through the Innovative Users Group INNOPAC
list Public replies: INNOPAC at innopacusers dot org Update your subscription
options:
http://innopacusers.org/mailman/listinfo/innopac
--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies: INNOPAC at innopacusers dot org
Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac
_______________________________________________________________________
This email has been scanned for all viruses.
_______________________________________________________________________
This email has been scanned for all viruses.