Dear all We had 3.02, 3.05 and 3.06 running for quite a while with Zebra. All three versions made some problems with deleting, reindexing or performance. We recently switched to NoZebra. Things are working better in functionality, maintainability and performance by now. Since we do not use Koha as search interface, I can't say if Zebra is giving an advantage for (OPAC) end users. But Koha with NoZebra is still worth a try. Regards, Stefan
Hello Stefan, I also had a similar approach. I started with NoZebra because it was much easier to configure but soon I run into troubles. The problems where mainly related to Search.pm. One problem for instance was related to multiple 650 fields. I even tried to fix myself the code in GetMarcSubjects but after some discussions on the koha channel everybody told me NoZebra is no longer supported so I switched to zebra. The only problem since was related to the fact that re-indexing is not in real-time and one should get used to wait until the data is available for search. Len www.len.ro On 08/24/2010 09:34 PM, stefan wrote:
Dear all
We had 3.02, 3.05 and 3.06 running for quite a while with Zebra. All three versions made some problems with deleting, reindexing or performance. We recently switched to NoZebra. Things are working better in functionality, maintainability and performance by now. Since we do not use Koha as search interface, I can't say if Zebra is giving an advantage for (OPAC) end users. But Koha with NoZebra is still worth a try.
Regards, Stefan _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Marilen Corciovei wrote:
told me NoZebra is no longer supported so I switched to zebra. The only problem since was related to the fact that re-indexing is not in real-time and one should get used to wait until the data is available for search.
There are currently some discussions on the koha-devel email list about making reindexing happen in realtime, rather than the current configurable "every N minutes". How big an issue is that for libraries? Do people know which other LMSes are really in realtime and which only claim to be? (Koha is one of very few which you can check the code.) Is any (group of) library(/ies) willing to fund this change? Or is someone already doing so? Curiously, -- MJ Ray (slef) Webmaster and developer for hire at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op
On 08/25/2010 11:41 AM, MJ Ray wrote:
Marilen Corciovei wrote:
told me NoZebra is no longer supported so I switched to zebra. The only problem since was related to the fact that re-indexing is not in real-time and one should get used to wait until the data is available for search.
There are currently some discussions on the koha-devel email list about making reindexing happen in realtime, rather than the current configurable "every N minutes". How big an issue is that for libraries?
Do people know which other LMSes are really in realtime and which only claim to be? (Koha is one of very few which you can check the code.)
Is any (group of) library(/ies) willing to fund this change? Or is someone already doing so?
Curiously,
Actually the problem of re-indexing was only critical in a single point: adding authorities and reusing them on the spot. This happens when manually adding a biblio which cannot be found in z3950. The librarians could not understand why to wait a few minutes in the process between adding the authority and using it. In the end they got used to it. For other things, I don't think real-time is really a problem. Only when you expect to re-use the info you just added immediately. Of course one will argue that you should add the authorities in advance but this is not always the case especially if you are having a specialized library with no available list of authorities before. As I said, it is a very specific case. Len
Marilen Corciovei wrote:
On 08/25/2010 11:41 AM, MJ Ray wrote:
There are currently some discussions on the koha-devel email list about making reindexing happen in realtime, rather than the current configurable "every N minutes". How big an issue is that for libraries? Actually the problem of re-indexing was only critical in a single point: adding authorities and reusing them on the spot. [...]
Thank you for the feedback. I will feed this example into the development discussions. Would anyone else like to mention others, or is this the only place realtime would really help? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Webmaster, Debian Developer, Past Koha RM, statistician, former lecturer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
participants (3)
-
Marilen Corciovei -
MJ Ray -
stefan