.
Cheers!
Scott
-Original Message-
From: dc...@prosentient.com.au
Sent: Monday, June 6, 2022 6:34 PM
To: koha@lists.katipo.co.nz; skaman...@gmail.com
Subject: RE: [Koha] Zebra indexing error on upgrade to 22.05.00.000
Hi Scott,
I would say that you have bad data in at least one of your
Hi Erlanda,
it looks like you have a few items in your database that have no item
type set in the item. If you fix them, the warnings shown below should
disappear.
A report like this should help you locating them:
SELECT itemnumber, barcode, itemcallnumber FROM items WHERE itype is
NULL or
I think no
Le 26/03/2014 20:53, Paul A a écrit :
At 07:02 PM 3/26/2014 +0100, Fridolin SOMERS wrote:
The stop words are indeed obsolete, they where used by NoZebra mode,
which has been removed in 3.14.
Is 245 second indicator not used at all? MARC definitions give it as:
Second Indi
At 07:02 PM 3/26/2014 +0100, Fridolin SOMERS wrote:
The stop words are indeed obsolete, they where used by NoZebra mode, which
has been removed in 3.14.
Is 245 second indicator not used at all? MARC definitions give it as:
Second Indicator
Nonfiling characters
0 - No no
The stop words are indeed obsolete, they where used by NoZebra mode,
which has been removed in 3.14.
Le 17/02/2014 09:23, Fischer, Katrin a écrit :
Hi Ann,
I can confirm that Zebra doesn't use the stop word list - it doesn't need one
:) But I am surprised the configuration did effect the sear
Hi Ann,
I can confirm that Zebra doesn't use the stop word list - it doesn't need one
:) But I am surprised the configuration did effect the search, did you change
the SearchEngine or some other of the search system preferences?
Katrin
> -Original Message-
> From: koha-boun...@lists.k
It looks like this was tracked to a problem with paths and environment.
I found that the testing which worked was when I was running
interactively, whereas the times which did not work were when I was
running using cron. Once I made sure my base shell was getting the
right paths and environme
Tom Hanstra schreef op ma 06-01-2014 om 13:35 [-0500]:
> Has anyone seen such indexing problems before? What can I be
> checking
> to track this problem down and address it?
What do your logs say? In particular, is the cron job for indexing
actually running, and are emails from cron (which will
Thanks everyone, I've resolved this issue.
From: pponc...@live.com
To: koha@lists.katipo.co.nz
CC: ta...@livingstonpubliclibrary.org
Subject: Zebra Indexing
Date: Mon, 19 Aug 2013 06:33:35 -0700
Koha installed version:
3.00.00.107
I'm trying to re-index my catalog and of course, something i
Paul Poulain schreef op vr 31-05-2013 om 13:56 [+0200]:
> Could you share the script you've made to check that ? We're also using
> nagios to monitor, and that would be useful.
Of course. They're pretty straight forward. You can find our nagios
stuff in the catalyst Koha git repo, in the 'nagios'
We'de also be interesting in that zebra monitoring script...
I imagine many of the community are using Nagios for monitoring and this
isn't something I'de got round to implementing myself (and sharing) yet
either.
Cheers
On 31 May 2013 12:56, Paul Poulain wrote:
> Le 31/05/2013 00:51, Robin S
Dear Paul,
Recently I installed koha 3.12 on Debian Squeeze,
I had problems with opac not showing results.(No results found)
I even posted the error log here, and was waiting for reply from many days.
Thank you so much for your reply, I tried the steps mentioned by you, and
now am successful for s
Le 31/05/2013 00:51, Robin Sheat a écrit :
> Elaine Bradtke schreef op do 30-05-2013 om 16:59 [+0100]:
>> The indexing process seems to be a weak spot in Koha.
>
> When we set up nagios monitoring for Koha instances, one of the things
> we include is checking that there is nothing in the zebra que
Elaine Bradtke schreef op do 30-05-2013 om 16:59 [+0100]:
> The indexing process seems to be a weak spot in Koha.
When we set up nagios monitoring for Koha instances, one of the things
we include is checking that there is nothing in the zebra queue more
than about an hour old. This ensures that th
Just to say, it may not be the Koha upgrade that caused the problem.
We haven't upgraded our Koha system lately (we're running 3.10.02) but the
server that it runs on recently had a system upgrade. We thought Koha came
through without any problems (search and display seemed fine), but newly
catal
At 05:43 PM 5/29/2013 -0700, David Whelchel wrote:
[snip]
At this point I can go into either the OPAC or ADMIN client and successfully
search. BUT once I execute any rebuild_zebra.pl command (all finish without
any errors) upon searching the search results show the number of items
returned but
Hi.
The first place to try is the search FAQ at:
http://koha-community.org/documentation/faq/ (scroll down to the Searching
section)
The second place to try is the mailing list archive (use the search box on
the front page of the Koha community website).
There can be a lot of reasons why indexin
Hi,
I had the same problem.
My Framework had Koha field *biblionumber* mapped to *999$9* so ha had to
add: /melm 999$9Local-number,Local-number:n/ to
/etc/koha/zebradb/marc_defs/unimarc/biblios/record.abs
One very good help is here: http://www.len.ro/2010/06/koha-search-2/
Thanks,
JA
--
18 matches
Mail list logo
