- Koha - lists.katipo.co.nz

Re: [Koha] Koha Digest, Vol 104, Issue 54
by Ilesanmi S. Olawale 25 Jun '14

25 Jun '14

Hi , We would like to upgrade the version of our Koha 3.12 to 3.16 Will this affect any configurations we have on the 3.12 ??. I mean will it affect the patrons data ??. Thanks Olawale Ilesanmi S. Olawale Web & Systems Admin. ZACCHEUS ONUMBA DIBIAEZUE MEMORIAL LIBRARIES 196, Awolowo Road, Ikoyi, P O Box 52829, Ikoyi Lagos State, Nigeria. RC 12224 ----- Original Message ----- From: koha(a)lists.katipo.co.nz To: Cc: Sent:Wed, 25 Jun 2014 12:00:01 +1200 Subject:Koha Digest, Vol 104, Issue 54 Send Koha mailing list submissions to koha(a)lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Re: Wipe Koha database (just auth and biblio records) (Pablo Bianchi) 2. Re: Wipe Koha database (just auth and biblio records) (Tomas Cohen Arazi) ---------------------------------------------------------------------- Message: 1 Date: Tue, 24 Jun 2014 16:38:59 -0300 From: Pablo Bianchi To: Robin Sheat Cc: Koha-org - List Subject: Re: [Koha] Wipe Koha database (just auth and biblio records) Message-ID: Content-Type: text/plain; charset=UTF-8 Hi Robin, I'm aware about turning foreign keys constrains off is risky, what I was trying to know is how risky could be, but OK, I realize that depends of each database, and always a bad idea. So at least we can say manual (and also bulkmarkimport.pl -d option) should be updated (MySQL >~5.5)* adding a note about DELETE FROM biblio way not always will work right away. This bring us to: > In some cases the constraints will propagate the delete, > in other cases they won't. These differences are by design. There are good design reasons for no letting "delete biblio" table propagate in all/any cases? Propagation in any case will make really simple to update manual and bulkmarkimport. *I'll then fill a bug report about this two issues (manual and bulkmarkimport -d option) update. ?Regards, Pablo ? ------------------------------ Message: 2 Date: Tue, 24 Jun 2014 16:42:09 -0300 From: Tomas Cohen Arazi To: Pablo Bianchi Cc: Koha-org - List Subject: Re: [Koha] Wipe Koha database (just auth and biblio records) Message-ID: Content-Type: text/plain; charset=UTF-8 Pablo, you might as well import using the web tool, which handles deletion too. On Tue, Jun 24, 2014 at 4:38 PM, Pablo Bianchi wrote: > Hi Robin, > > I'm aware about turning foreign keys constrains off is risky, what I was > trying to know is how risky could be, but OK, I realize that depends of > each database, and always a bad idea. > > So at least we can say manual (and also bulkmarkimport.pl -d option) > should > be updated (MySQL >~5.5)* adding a note about DELETE FROM biblio way not > always will work right away. This bring us to: > > > In some cases the constraints will propagate the delete, > > in other cases they won't. These differences are by design. > There are good design reasons for no letting "delete biblio" table > propagate in all/any cases? Propagation in any case will make really simple > to update manual and bulkmarkimport. > > *I'll then fill a bug report about this two issues (manual and > bulkmarkimport -d option) update. > > ?Regards, > Pablo > ? > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > -- Tom?s Cohen Arazi Prosecretar?a de Inform?tica Universidad Nacional de C?rdoba ? +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 104, Issue 54 *************************************

1 0

REMINDER: North American Koha Users Group, August 6 - 8
by Chad Roseburg 25 Jun '14

25 Jun '14

Come join us in NCW for the 2014 North American Koha Users Group. Meet with support vendors and fellow Koha users while we cover the following topics in round table discussions and presentations: * Using Koha as CMS * Using Koha with DSpace * Testing bugs * Workflow with git * Upcoming features – demos * Future of Koha – elasticsearch, plack …other improvements. * Overview of Bootstrap in OPAC * Permissions in Koha Information on lodging and directions here: http://ncrl.org/nakug Register here: http://ncrl.org/nakug_2014_reg Share your expertise with other Koha users and register as a presenter here: http://ncrl.org/nakug_2014_presenter Looking forward to seeing you there! -- Chad Roseburg Systems Librarian Automation Dept. North Central Regional Library

1 0

Wipe Koha database (just auth and biblio records)
by Pablo Bianchi 24 Jun '14

24 Jun '14

Hi all, Once in a while I need to erase / clean / reset Koha database, and with this I mean to remove bibliographic and authority records (leaving systempreference intact). Some years ago it works just TRUNCATE TABLE biblio, biblioitems, items; then with foreign key constraint the harder DELETE FROM biblio; seems to do the job. cleaning all other tables in cascade. But now (with Koha v3.16) I just want to say that *Appendix F. Resetting the Koha Database <http://manual.koha-community.org/3.16/en/resetkohadb.html>* might be not exactly right, but with this trick <http://stackoverflow.com/questions/5452760/truncate-foreign-key-constrained…> (disable foreign key constraint checks) seems to work: *SET FOREIGN_KEY_CHECKS=0;TRUNCATE TABLE biblio;TRUNCATE TABLE biblioitems;TRUNCATE TABLE items;TRUNCATE TABLE auth_header;TRUNCATE TABLE sessions; TRUNCATE TABLE zebraqueue;SET FOREIGN_KEY_CHECKS=1;* And of course then: *koha-rebuild-zebra --verbose --full $(koha-list)* Am I right? This could be risky, having side effects? Regards, Pablo

3 6

Athena to Koha
by Manny Tamayao 24 Jun '14

24 Jun '14

Good day Fiji, We did it two years ago. >From Athena, you can export your marc data from Cataloging>Export MARC Records>select range "Barcode", put a filename then choose where to save your data and finally I do suggest choose "Export as multiple MARC records". You can use MarcEdit http://marcedit.reeset.net/ to clean and map your MARC data in preparation for import in Koha (e.g. 852 to 952, adding your homebranch, etc..). It would be easier if you have a librarian or someone with you who understand MARC. Hope it helps, Manny Message: 2 Date: Fri, 20 Jun 2014 05:13:17 +0000 From: Gyaneshwar Narayan <gyaneshwar.narayan(a)usp.ac.fj> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Athena to Koha Message-ID: <488B8BBDFE95BB428ECE31177AF0901F47256E15(a)suvxch10mb1.usp.ac.fj> Content-Type: text/plain; charset="us-ascii" Good afternoon from Fiji May I ask if anyone has done a migration from Athena 9.2 to the Koha??? If yes, then is there a documentation of the steps used??? Also, is there a PDF or webpage I can view to help me in doing cosmetic changes to the Koha site and the OPAC??? In addition, is there a list of all the features of Koha??? Sorry about asking so many questions but could anyone help please. Regards. ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 104, Issue 49 *************************************

2 1

MARC Framework
by Elaine Bradtke 23 Jun '14

23 Jun '14

Would someone please export and send me a (MARC 21) copy of their Sound Recordings format? (CSV please). Our Sound Recordings Framework was mangled a while ago due to some overenthusiastic and under informed tinkering. Now that we're getting around to cataloguing sound recordings, it's time to fix it. As the IT guru is up to his eyeballs in other things right now, this would be the quickest way to fix the problem (with my limited tech skills). Yes, I know, back ups. . . there was a backup file, but it seems to have vanished. In atonement for my sins, I will add our version to the wiki ( http://wiki.koha-community.org/wiki/MARC_frameworks) once I've edited and tested it. We have a lot of archival recordings which will require some of the less commonly used fields. Thanks! -- Elaine Bradtke Data Mangler VWML English Folk Dance and Song Society | http://www.efdss.org Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and Song Society in London, England. If you wish to phone me personally, send an e-mail first. I work off site) -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999 --------------------------------------------------------------------------- "Writing about music is like dancing about architecture" --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)

1 0

Re: [Koha] Tracing cataloguer in KOHA staff client
by Indranil Das Gupta 23 Jun '14

23 Jun '14

Hi, On Mon, Jun 23, 2014 at 2:12 PM, <hanneke.vansijl(a)freshfields.com> wrote: > Thanks for sending these links leading to some information. > > What I do not get yet if it is possible to see within a record/ item who last changed a specific record . I guess we will just have to try it out. > I think the Cataloguing Log might not be such a good option because of the possibility of slowing down the system. If the code doesn't serve you, you could look at modifying it. The logging code is quite simple. Just to give you an idea how the logviewer would display the logs, have a look at http://snag.gy/vca9M.jpg >From the image, you can see the who, when, what and on which record details of the operation in question. In my case, I needed my custom plugins (.kpz files) to be logged, so I simply added another option to the logviewer script and added the brief logging code to my plugin code. You *could* override what CatalogingLog logs and have it do your thing! :-) just my 2p. cheers, -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

1 0

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