Z39.50 search results accumulating in reservoir
Running some tests on 3.22 before we install it in our production site and noticed something that I hadn't seen before. I added a new record using a z39.50 search ran it through the circulation system, etc. as part of my normal test routine. Then I went to pull it up for editing, and ran a search for the title in the Cataloguing module. I was surprised when all the other titles that came up in the original z39.50 search showed up as being in the reservoir! Will these things continue to pile up in the reservoir? Do they drop off after a certain number has accumulated, or time has elapsed? Is there a setting to switch it off? ​My stoic cataloguer hasn't mentioned it, but I personally find it untidy.​ -- Elaine Bradtke Data Wrangler VWML English Folk Dance and Song Society | http://www.efdss.org Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and Song Society in London, England. If you wish to phone me personally, send an e-mail first. I work off site) -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999 --------------------------------------------------------------------------- "Writing about music is like dancing about architecture" --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
Hi, On Thu, May 5, 2016 at 8:54 PM, Elaine Bradtke <eb@efdss.org> wrote:
Then I went to pull it up for editing, and ran a search for the title in the Cataloguing module. I was surprised when all the other titles that came up in the original z39.50 search showed up as being in the reservoir! Will these things continue to pile up in the reservoir? Do they drop off after a certain number has accumulated, or time has elapsed? Is there a setting to switch it off?
Indeed, they'll continue to accumulate. Chris might correct me if I'm wrong, but I believe that caching of Z39.50 results in the reservoir was added years ago to reduce usage of slow (and maybe even fee-based?) Z39.50 targets; the idea is that one would search the reservoir first, then use Z39.50 if a record couldn't be found. The cleanup_database.pl database cronjob can be used to tidy up the reservoir — use the --z3950 switch. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
participants (2)
-
Elaine Bradtke -
Galen Charlton