I am migrating book records via z39.50 searches and am finding it very slow going. Seems like I read somewhere in the various manuals, etc., that Koha ran slowly on Safari. Has anyone else had this experience? Or is it probably just my network. Shelley
On 30 December 2010 13:23, Shelley & Kurt Kemperman <ksckemperman@chartermi.net> wrote:
I am migrating book records via z39.50 searches and am finding it very slow going. Seems like I read somewhere in the various manuals, etc., that Koha ran slowly on Safari. Has anyone else had this experience? Or is it probably just my network.
Is it the searching that is slow? Or is it the loading of the cataloguing form that is slow? If its the former, most likely network related or the z3950 servers you are querying are slow, if its the latter then it could be safari. Chris
Hi Shelley, On most occasions, I find that Koha loads faster when using Safari compared to other browsers (Firefox, Google Chrome, Internet Explorer). But, that is just my personal experience. Kindest Regards,Joel
From: ksckemperman@chartermi.net To: koha@lists.katipo.co.nz Date: Wed, 29 Dec 2010 19:23:39 -0500 Subject: [Koha] slow koha on Safari
I am migrating book records via z39.50 searches and am finding it very slow going. Seems like I read somewhere in the various manuals, etc., that Koha ran slowly on Safari. Has anyone else had this experience? Or is it probably just my network.
Shelley _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
On Wed, Dec 29, 2010 at 9:23 PM, Shelley & Kurt Kemperman <ksckemperman@chartermi.net> wrote:
I am migrating book records via z39.50 searches and am finding it very slow going. Seems like I read somewhere in the various manuals, etc., that Koha ran slowly on Safari. Has anyone else had this experience? Or is it probably just my network.
Z39.50 record import involves a communication with a remote server so if that's the only slow behaviour the candidate answer is that there is a network / remote server problem. You can check it trying another browser (firefox?). To+
participants (4)
-
Chris Cormack -
Joel Harbottle -
Shelley & Kurt Kemperman -
Tomas Cohen Arazi