[OPEN-ILS-GENERAL] Z39.50 Searching

[Forrest, Stuart]

Just to note: We at Beaufort are having this problem mainly with OCLC.

I deleted the users profile, created a new one then tried the search process again. It eorked OK for about 5 or 6 tries then went back to what it was doing before.
IE in this order: Search Auth/Title records returned
                  Search ISBN records returned
                  Search Auth/Title no records returned.

Once the client is (Evergreen Staff Client that is) is reset Auth/Title searching works again until an ISBN search is performed and the Auth/Title search no longer works....

Thanks
Stuart

*******************************************************************************
Stuart Forrest PhD
Library Systems Specialist
Beaufort County Library
311 Scott Street
Beaufort
SC 29902

Tel 843 470 6534


-----Original Message-----
From: open-ils-general-bounces at list.georgialibraries.org [mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Mike Rylander
Sent: Monday, October 12, 2009 12:50 PM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Z39.50 Searching

On Mon, Oct 12, 2009 at 12:21 PM, Dan Scott <dan at coffeecode.net> wrote:
> 2009/10/12 Hardy, Elaine <ehardy at georgialibraries.org>:
>> Jason and Don,
>>
>> I just recreated it here.  I was able to correctly re-execute the search
>> after closing and reopening the  z39.50 interface. I did not have to close
>> the entire client. I will test with other title/author and ISBN combinations
>> to see if it holds true for others.
>
> In my case - trunk - I was able to search LoC and get results by
> updating the truncation attribute from a value of '0' (the default in
> Evergreen for attributes) to '1' (to correspond to the LoC-supported
> values of '1' and '100' as documented at
> http://www.loc.gov/z3950/lcserver.html#trua).
>
> The required SQL was:
>
> UPDATE config.z3950_attr SET truncation = 1 WHERE source = 'loc';
>
> Then I shut everything down, wiped my staff client profile, started
> everything back up, and did a successful fresh search of LoC.
>
> This is consistent with what I see in yaz-client:
>
[snip test case]
>
> Soooo, we'll want to add the accepted truncation value to the 950 seed
> data for LoC. This is probably required for 1.6 if the corresponding
> changes from trunk were backported, yes? In which case, I guess we
> won't need to create upgrade scripts as the base data will be correct
> as of 1.6.0.0.
>
> Dan
>

Adding that now, as a part of my 1.6.0.0 polishing.

-- 
Mike Rylander
 | VP, Research and Design
 | Equinox Software, Inc. / The Evergreen Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com