I wonder now if we could seperate the two. So cataloging updated zebra immediately, but circulation was queued. Would that work? On Fri, 2010-08-20 at 06:53 +1200, Chris Cormack wrote:
On 20 August 2010 05:00, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
Hi everyone, I'm writing a replacement for zebraqueue-daemon.pl so that we can set the reindexing interval for authorities (and biblios) via systempreferences and we can set intervals in seconds (for our impatient librarians) wich cannot be acknowleged using cron jobs. I'll be posting the script soon, but I've been thinking of kind-of refactoring rebuild_zebra into a reusable library so that the daemon doesn't spawn a perl interpreter every (for example) 30 seconds.
A question related to the topic is: why we don't trigger the update whenever a cataloguer click "save" for a biblio or auth record? Perhaps this refactoring serves for an implementation of this.
Because it's slow. Thats why it is done as a seperate process, the index needs to be updated every time an item is issued or returned as well as when it is changed by a cataloguer. It would slow circulation down way too much.
Chris _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
-- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha