- Koha - lists.katipo.co.nz

Tracing cataloguer in KOHA staff client
by hanneke.vansijl＠freshfields.com 23 Jun '14

23 Jun '14

Hi, I am not sure if this is the right place to ask. We are sharing KOHA within our office around the world and decided to use the non-public note to leave initials of the cataloguer. It seems not work as people forget to leave their initials. What we would like to know if there is a system generated way to track the last person who managed/changed a record. Thanks in advance for your help. With kind regards, Hanneke van Sijl Hanneke van Sijl Information Specialist Freshfields Bruckhaus Deringer LLP Strawinskylaan 10 1077 XZ Amsterdam T +31 20 485 7522 hanneke.vansijl(a)freshfields.com<mailto:hanneke.vansijl@freshfields.com> www.freshfields.com<http://www.freshfields.com/> This email is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply email and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your co-operation. Please contact our IT Helpdesk on +44 (0) 20 7785 2000 or email ITHelpdesk(a)freshfields.com if you need assistance. Freshfields Bruckhaus Deringer LLP is a limited liability partnership registered in England and Wales with registered number OC334789. It is authorised and regulated by the Solicitors Regulation Authority. For regulatory information please refer to www.freshfields.com/support/legalnotice. A list of the members (and of the non-members who are designated as partners) of Freshfields Bruckhaus Deringer LLP and their qualifications is available for inspection at its registered office, 65 Fleet Street, London EC4Y 1HS. Any reference to a partner means a member, or a consultant or employee with equivalent standing and qualifications of Freshfields Bruckhaus Deringer LLP or any of its affiliated firms or entities. Freshfields Bruckhaus Deringer LLP's Amsterdam office includes attorneys, civil law notaries, tax advisers and solicitors. Dutch Chambers of Commerce registration number 34368197.

2 1

Re: [Koha] Zebra index - two instances on one Server
by Tomas Cohen Arazi 23 Jun '14

23 Jun '14

If you read te instructions i sent to you, you would notice you need to set one zebra daemon for each configured instance. This means koha-zebra-daemon-ctl.sh is not a good naming schema. Regards To+ Ps. it looks like I sent the email to you instead of the list. El 18/06/2014 07:39, "Tomas Cohen Arazi" <tomascohen(a)gmail.com> escribió: > If you need to keep installing using tarball, you should read and follow > this instructions carefully: > > http://wiki.koha-community.org/wiki/Installing_Multiple_Instances_of_Koha > > Best regards. > El 18/06/2014 06:05, "kamild" <smichaelxx(a)tlen.pl> escribió: > >> Fabio I running koha ver 3.8 - Tarball. >> Is it possible to runing zebra with 2 instances koha? >> thx >> >> >> >> -- >> View this message in context: >> http://koha.1045719.n5.nabble.com/Zebra-index-two-instances-on-one-Server-t… >> Sent from the Koha-general mailing list archive at Nabble.com. >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> http://lists.katipo.co.nz/mailman/listinfo/koha >> >

1 0

Zebra index - two instances on one Server
by kamild 23 Jun '14

23 Jun '14

Hi, On the server I have two instances of Koha (koha1, koha2). Zebra unfortunately indexes only data from database koha1 to instances koha1 and index instance Koha2 is empty KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -r -b or data from database koha2 to instances koha1 and index instance Koha2 is empty KOHA_CONF=/etc/koha2/koha-conf.xml PERL5LIB=/usr/share/koha2/lib /usr/share/koha2/bin/migration_tools/rebuild_zebra.pl -r -b How do to index data for the two instances? Thx. Greets -- View this message in context: http://koha.1045719.n5.nabble.com/Zebra-index-two-instances-on-one-Server-t… Sent from the Koha-general mailing list archive at Nabble.com.

2 5

Re: [Koha] Zebra Rebuild error...
by Paul A 23 Jun '14

23 Jun '14

At 02:41 PM 6/20/2014 +0300, Layale Bassil wrote: >Hello Phillip, > >Thanks a lot for the support. Yes I used to be able to rebuild Zebra many >times, and before getting the error, I did many rebuilds. > >Since I had no root privileges, I asked the support team to do the rebuild >using the sudo -s and the rebuild was successful. I may very well be wrong if your installation was not done with the tarball (I have no experience whatsoever with "packages"), but you should use your koha/zebra user to reindex, not root. It sounds as though your permissions may be wrong. Best -- Paul >My problem now is that the search is still not returning any hit >eventhough the database contains 19000 records and the rebuild was >successful! I would appreciate your suggestions on this matter! > >How can I fix the search in such a case? > >Many thanks, >Layale. > >From: Phillip Ponchot [mailto:pponchot@live.com] >Sent: Thursday, June 19, 2014 5:51 PM >To: Layale Bassil; koha(a)lists.katipo.co.nz >Subject: RE: [Koha] Zebra Rebuild error... >Importance: High > >Have you ever rebuilt Koha Zebra before? > >The errors that you're getting reminds me of the first time I tried to >rebuild zebra (ubuntu ). There was a rights issue. > >To rebuild zebra on ubuntu you have to use sudo -s with the rebuild >command or you get a ton of errors and a failure. > >Hope this helps. > > >Phillip > > From: lb26(a)aub.edu.lb<mailto:lb26@aub.edu.lb> > > To: koha(a)lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz> > > Date: Thu, 19 Jun 2014 13:28:44 +0300 > > Subject: [Koha] Zebra Rebuild error... > > > > Hello, > > > > I am using Koha 3.14 and importing data into it. Everything was working > properly until I tried to rebuild zebra after having around 19000 records > and I got the following error (a part of the error): > > > > *** stack smashing detected ***: zebraidx terminated > > ======= Backtrace: ========= > > /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f9215503807] > > /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f92155037d0] > > /usr/lib/libidzebra-2.0.so.0(+0x17007)[0x7f9215b5d007] > > /usr/lib/libidzebra-2.0.so.0(+0x1712b)[0x7f9215b5d12b] > > /usr/lib/libidzebra-2.0.so.0(heap_cread_item2+0xf2)[0x7f9215b5d2b2] > > /usr/lib/libidzebra-2.0.so.0(isamb_merge+0x5b)[0x7f9215b89c8b] > > /usr/lib/libidzebra-2.0.so.0(heap_inpb+0x193)[0x7f9215b5da23] > > /usr/lib/libidzebra-2.0.so.0(zebra_index_merge+0x258)[0x7f9215b5de38] > > /usr/lib/libidzebra-2.0.so.0(+0x298df)[0x7f9215b6f8df] > > /usr/lib/libidzebra-2.0.so.0(zebra_end_transaction+0x11d)[0x7f9215b7326d] > > /usr/lib/libidzebra-2.0.so.0(zebra_end_trans+0x31)[0x7f9215b733d1] > > zebraidx[0x401884] > > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f921541a76d] > > zebraidx[0x401a0d] > > ======= Memory map: ======== > > 00400000-00403000 r-xp 00000000 08:01 1479 /usr/bin/zebraidx-2.0 > > 00602000-00603000 r--p 00002000 08:01 1479 /usr/bin/zebraidx-2.0 > > 00603000-00604000 rw-p 00003000 08:01 1479 /usr/bin/zebraidx-2.0 > > 009b9000-012d6000 rw-p 00000000 00:00 0 [heap] > > 7f9208000000-7f92082f4000 rw-p 00000000 00:00 0 > > 7f92082f4000-7f920c000000 ---p 00000000 00:00 0 > > 7f920c25c000-7f920db5d000 rw-p 00000000 00:00 0 > > 7f920db5d000-7f920db5e000 ---p 00000000 00:00 0 > > 7f920db5e000-7f920fc5f000 rw-p 00000000 00:00 0 [stack:11507] > > > > > > I cannot search koha anymore as the rebuild is crashing. Is there any > limitation on the number of records that Koha can accept? How can I fix > this error? > > > > Please advise, > > > > Thanks and regards. > > Layale. > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> > > http://lists.katipo.co.nz/mailman/listinfo/koha >_______________________________________________ >Koha mailing list http://koha-community.org >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1

Please - a little bit more help
by Phillip Ponchot 23 Jun '14

23 Jun '14

I've been battling a corrupted koha instance for awhile now. The first time that I realized that something was wrong was when I could no longer do a backup. Everytime the koha backup got the the biblioitems table, there would be an error 2013 Lost connection to server. Thanks to your help and the mysql board I built another table (like bibloitems). Found out that the engine was innodb and set the engine on the new table. I very carefully copied the records until I found out which one was bad and I skipped it. I then renamed this new table to biblioitems. After the koha biblioitems was fixed, I did a dump and then I imported the dump back into the database to fix any tables that might also have issues. I ran a mysqlcheck on koha and all the tables came back OK. Everything is working great, but the cataloger called me and said that when she adds a new record, the item can not be checked out by barcode. She also said that before you could not "duplicate" a bar code or you would get a warning. At this point, I am at a lost on how to fix this issue, I've loaded MYSQLWorkBench on a computer so I can look at the data but I can't understand why the cataloger can enter a new record, search on the record, but the item can not be checked out via its barcode. If you could please please, give me a push in the right direction on how to resolve this issue, I would be forever grateful. Some of my thoughts to repair this issue would be: 1. Install the current version of Koha being used to a new server and then import the dump file in hopes that this issue is koha itself and not the data. 2. Upgrade to 3.2 on a new server and try to import the data. 3. Try to reinstall 3.00.00.107 over the old installation and then import the data. 4. Install the latest version of Koha to a new server and then pay somone to covert the data to the new version of Koha. (If you know of anyone who does the conversions, please let me know as I don't know enough about the data to convert it). Thank you so much for any suggestion or help. I've also posted this email on the forum so that other could benefit from the answer. Phillip

2 1

Away From My Desk
by georgew 23 Jun '14

23 Jun '14

Hello everyone, I will be away from my desk until Tuesday, July 1, 2014. If you need to contact someone immediately, please phone 208-882-3925 and talk to someone at the circulation desk. I will respond to your e-mail as soon as I can when I get back. George

1 0

Looking for a provider
by Phillip Ponchot 22 Jun '14

22 Jun '14

I'm looking for a provider who can transform koha data to move it from Koha 3.00.00.107 to Koha 3.14 or 3.16 and ensure that the new version of Koha is working properly. Please send an email for an estimate of what it would cost. I will be building the server and installing Koha. Just need the data to be transformed and placed in the tables. Thanks, Phillip

1 0

sorting long Cutter's
by Giuseppe Angilella 21 Jun '14

21 Jun '14

Hi, call numbers having Cutter parts made of several substrings currently are not sorted correctly. Here are examples: | itemcallnumber | cn_source | cn_sort | | 530 F435 1996 v1 | ddc | 530_F435_199600000000000_V1 | | 530 F435 1996 v2p1 | ddc | 530_F435_199600000000000_V2P1 | | 530 F435 1996 v2p2 | ddc | 530_F435_199600000000000_V2P2 | Despite being in the Dewey 530 class, these items are sorted after any 530.xy item (and before any 531, which is OK). I suspect this has to do with the additional space separators: more than one seem to be too many. Any hint? What is the actual algorithm used by Koha to evaluate the cn_sort field (within the ddc scheme)? Grouping, or even merging, all the subfields after the Dewey into one single string was of no help. Many thanks and best regards, Giuseppe.

2 1

Barcode issue in Koha
by Phillip Ponchot 21 Jun '14

21 Jun '14

I recently rebuilt the bilioitems table and dumped koha and imported the dump back in. Everything is working great but the cataloger has reported that there is an issue with the barcodes. New imported records with a barcode can not be checked out (not found). Also if a barcode is duplicated, Koha used to indicate that the barcode was already in use but no longer does this. Has anyone had this problem or know how to correct it. Any suggestion on how to fix this would be appreciated as I'm at a lost right now. Phillip

1 0

Zebra Rebuild error...
by Layale Bassil 20 Jun '14

20 Jun '14

Hello, I am using Koha 3.14 and importing data into it. Everything was working properly until I tried to rebuild zebra after having around 19000 records and I got the following error (a part of the error): *** stack smashing detected ***: zebraidx terminated ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f9215503807] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f92155037d0] /usr/lib/libidzebra-2.0.so.0(+0x17007)[0x7f9215b5d007] /usr/lib/libidzebra-2.0.so.0(+0x1712b)[0x7f9215b5d12b] /usr/lib/libidzebra-2.0.so.0(heap_cread_item2+0xf2)[0x7f9215b5d2b2] /usr/lib/libidzebra-2.0.so.0(isamb_merge+0x5b)[0x7f9215b89c8b] /usr/lib/libidzebra-2.0.so.0(heap_inpb+0x193)[0x7f9215b5da23] /usr/lib/libidzebra-2.0.so.0(zebra_index_merge+0x258)[0x7f9215b5de38] /usr/lib/libidzebra-2.0.so.0(+0x298df)[0x7f9215b6f8df] /usr/lib/libidzebra-2.0.so.0(zebra_end_transaction+0x11d)[0x7f9215b7326d] /usr/lib/libidzebra-2.0.so.0(zebra_end_trans+0x31)[0x7f9215b733d1] zebraidx[0x401884] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f921541a76d] zebraidx[0x401a0d] ======= Memory map: ======== 00400000-00403000 r-xp 00000000 08:01 1479 /usr/bin/zebraidx-2.0 00602000-00603000 r--p 00002000 08:01 1479 /usr/bin/zebraidx-2.0 00603000-00604000 rw-p 00003000 08:01 1479 /usr/bin/zebraidx-2.0 009b9000-012d6000 rw-p 00000000 00:00 0 [heap] 7f9208000000-7f92082f4000 rw-p 00000000 00:00 0 7f92082f4000-7f920c000000 ---p 00000000 00:00 0 7f920c25c000-7f920db5d000 rw-p 00000000 00:00 0 7f920db5d000-7f920db5e000 ---p 00000000 00:00 0 7f920db5e000-7f920fc5f000 rw-p 00000000 00:00 0 [stack:11507] I cannot search koha anymore as the rebuild is crashing. Is there any limitation on the number of records that Koha can accept? How can I fix this error? Please advise, Thanks and regards. Layale.

3 3