- Koha - lists.katipo.co.nz

Re: [Koha] Koha Digest, Vol 100, Issue 3
by Sami M. Rasheed 03 Feb '14

03 Feb '14

Dear sir, I install koha, and everything working fine, but call number doesn't display, in call number column in OPAC search result, I customized all setting for LOC and use 050ab. please give me your help. Thanks. Sami On Monday, February 3, 2014 3:00 AM, "koha-request(a)lists.katipo.co.nz" <koha-request(a)lists.katipo.co.nz> wrote: 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. Reminder: the next general IRC meeting is on 5th February 2014 02:00 UTC (David Nind) 2. how to fix encoding of biblioitems.kohaxml (moving to latest Koha) (Giuseppe Angilella) 3. Edition/Deletion of Field in Patron Module (Zewar Khan) 4. Re: Edition/Deletion of Field in Patron Module (David Nind) 5. Re: Edition/Deletion of Field in Patron Module (Sue McMillan) ---------------------------------------------------------------------- Message: 1 Date: Sun, 2 Feb 2014 18:06:49 +1300 From: David Nind <david.nind(a)gmail.com> To: koha(a)lists.katipo.co.nz Subject: [Koha] Reminder: the next general IRC meeting is on 5th February 2014 02:00 UTC Message-ID: <CAK5OMPfeTTwa63K=VrNXy8kUaJQvAvwYc-7PviW5-pN0TVT0UA(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 This is a reminder that the next general IRC meeting is on the 5th February 2014 at 02:00 UTC. Koha community members are encouraged to attend. To find out what time the meeting is in your time zone go to: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M… Please add any items that you have to the agenda at: http://wiki.koha-community.org/wiki/General_IRC_meeting_5_February_2014 Updates from current role holders - please add an update to the agenda if you are expected to give an update but cannot attend (current role holders - http://wiki.koha-community.org/wiki/Roles_for_3.16) Information about IRC - if you are new to IRC see http://koha-community.org/get-involved/irc/ and http://www.wikihow.com/Get-Started-with-IRC-%28Internet-Relay-Chat%29 David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 h. +64 4 9720 600 | m. +64 21 0537 847 | w. +64 4 8906 098 ------------------------------ Message: 2 Date: Sun, 2 Feb 2014 07:11:48 +0100 (CET) From: Giuseppe Angilella <Giuseppe.Angilella(a)ct.infn.it> To: koha(a)lists.katipo.co.nz Subject: [Koha] how to fix encoding of biblioitems.kohaxml (moving to latest Koha) Message-ID: <alpine.LFD.2.10.1402020642430.2353@localhost> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Hi, I'm upgrading to Koha latest release (3.14.01.000) from a quite old one (2.x). I've imported the old database, let the web installation procedure perform the automatic steps to upgrade the sql structure, then launched the convert_to_utf8.pl tool in .../migration_tools/22_to_30/ My stuff (items, patrons, several configuration parameters) seems to be there. However, koha_rebuild_zebra fails, because of "wide characters" present in the database: specific error is Wide character in subroutine entry at /usr/share/perl5/MARC/Charset/Table.pm line 96 This results in a (hopefully) consistent, but unsearchable database. A closer inspection of the biblioitems table reveals that several (140 out of some 2800) items contain "accented characters" in various fields. These may have crept in at various stages, e.g. when inserting new records using a Mac keyboard, or on the occasion of not so careful upgrades. Although I had set the default character set as UTF8 (both for the locale, apache and mysql, let alone Koha itself), when I try to insert in the database a new record (containing accented letters in the title field, say) from the web interface, the title looks ok when accessing the newly created record (cgi-bin/koha/catalogue/detail.pl?biblionumber=...), whereas the "MARC Preview" shows corrupted accented letters, as if they weren't encoded in UTF8. An even closer inspection suggests that the encoding might indeed be UTF8, but that some characters follow the NFD, rather than NFC, convention (accented characters are represented as two separate characters). Is there a way to fix my biblioitems table? Is there a way to have new records entered correctly, at least? (I've even tried ALTER'ing the table to binary, then back to text with the correct encoding, field by field.) I could in principle go and fix each of the 140 corrupted MARC's via the web interface, if that's the only way, but the point is that, seemingly, even newly entered accented characters produce fancy output in the marcxml field. (The same may possibly apply also to the marc field, but that's a binary sql LONGBLOB, therefore possibly uneditable, but I assume it should be harmless to koha_rebuild_zebra .) Many thanks for all your suggestions and help. Regards, Giuseppe. ------------------------------ Message: 3 Date: Sun, 2 Feb 2014 06:26:59 +0000 (GMT) From: Zewar Khan <zewarnwfp(a)yahoo.co.uk> To: "Koha(a)lists.katipo.co.nz" <Koha(a)lists.katipo.co.nz> Subject: [Koha] Edition/Deletion of Field in Patron Module Message-ID: <1391322419.80112.YahooMailNeo(a)web171806.mail.ir2.yahoo.com> Content-Type: text/plain; charset=utf-8 Dear colleagues, how can i add or delete a field in Patron Module of Koha. Zewar khan ------------------------------ Message: 4 Date: Sun, 2 Feb 2014 21:56:46 +1300 From: David Nind <david.nind(a)gmail.com> To: Zewar Khan <zewarnwfp(a)yahoo.co.uk> Cc: "Koha(a)lists.katipo.co.nz" <Koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Edition/Deletion of Field in Patron Module Message-ID: <CAK5OMPcH62cqTP202oWuj-XGQDdk_HfF8Bd6uwHRcA4ra+7yiA(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 > > how can i add or delete a field in Patron Module of Koha. > If you mean adding and deleting custom fields for patrons, see: http://manual.koha-community.org/3.14/en/patscirc.html#patronattributetypes David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 h. +64 4 9720 600 | m. +64 21 0537 847 | w. +64 4 8906 098 ------------------------------ Message: 5 Date: Sun, 2 Feb 2014 18:58:06 +0000 From: Sue McMillan <sue.mcmillan(a)STDC.govt.nz> To: 'Zewar Khan' <zewarnwfp(a)yahoo.co.uk>, "Koha(a)lists.katipo.co.nz" <Koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Edition/Deletion of Field in Patron Module Message-ID: <F080C0113CF5F741BE2B9541CA30ACDA88F0CFF8(a)STDCEXCH02.internal.stdc.govt.nz> Content-Type: text/plain; charset="us-ascii" In Global System preferences look for BorrowerUnwantedField Enter the names of the fields you do not want , separated by a | Susan McMillan Cataloguing and Systems Administrator| South Taranaki District Council 105-111 Albion St, Hawera 4610 | Private Bag 902, Hawera 4640, NZ Phone: +64 6 278 0555 | Cell: | www.southtaranaki.com -----Original Message----- From: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Zewar Khan Sent: Sunday, 2 February 2014 7:27 p.m. To: Koha(a)lists.katipo.co.nz Subject: [Koha] Edition/Deletion of Field in Patron Module Dear colleagues, how can i add or delete a field in Patron Module of Koha. Zewar khan _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorised and may be illegal. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. ------------------------------ _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha End of Koha Digest, Vol 100, Issue 3 ************************************

1 0

Koha Community Newsletter: January 2014
by Chad Roseburg 03 Feb '14

03 Feb '14

Fellow Koha users: The Koha Community Newsletter for January 2014 is here: http://koha-community.org/koha-community-newsletter-january-2014/ We really appreciate the submissions we've gotten. Keep 'em coming! Thanks! Chad Roseburg Joanne Dillon Editors, Koha Community Newsletter

1 0

Edition/Deletion of Field in Patron Module
by Zewar Khan 02 Feb '14

02 Feb '14

Dear colleagues, how can i add or delete a field in Patron Module of Koha. Zewar khan

3 2

how to fix encoding of biblioitems.kohaxml (moving to latest Koha)
by Giuseppe Angilella 02 Feb '14

02 Feb '14

Hi, I'm upgrading to Koha latest release (3.14.01.000) from a quite old one (2.x). I've imported the old database, let the web installation procedure perform the automatic steps to upgrade the sql structure, then launched the convert_to_utf8.pl tool in .../migration_tools/22_to_30/ My stuff (items, patrons, several configuration parameters) seems to be there. However, koha_rebuild_zebra fails, because of "wide characters" present in the database: specific error is Wide character in subroutine entry at /usr/share/perl5/MARC/Charset/Table.pm line 96 This results in a (hopefully) consistent, but unsearchable database. A closer inspection of the biblioitems table reveals that several (140 out of some 2800) items contain "accented characters" in various fields. These may have crept in at various stages, e.g. when inserting new records using a Mac keyboard, or on the occasion of not so careful upgrades. Although I had set the default character set as UTF8 (both for the locale, apache and mysql, let alone Koha itself), when I try to insert in the database a new record (containing accented letters in the title field, say) from the web interface, the title looks ok when accessing the newly created record (cgi-bin/koha/catalogue/detail.pl?biblionumber=...), whereas the "MARC Preview" shows corrupted accented letters, as if they weren't encoded in UTF8. An even closer inspection suggests that the encoding might indeed be UTF8, but that some characters follow the NFD, rather than NFC, convention (accented characters are represented as two separate characters). Is there a way to fix my biblioitems table? Is there a way to have new records entered correctly, at least? (I've even tried ALTER'ing the table to binary, then back to text with the correct encoding, field by field.) I could in principle go and fix each of the 140 corrupted MARC's via the web interface, if that's the only way, but the point is that, seemingly, even newly entered accented characters produce fancy output in the marcxml field. (The same may possibly apply also to the marc field, but that's a binary sql LONGBLOB, therefore possibly uneditable, but I assume it should be harmless to koha_rebuild_zebra .) Many thanks for all your suggestions and help. Regards, Giuseppe.

1 0

Reminder: the next general IRC meeting is on 5th February 2014 02:00 UTC
by David Nind 02 Feb '14

02 Feb '14

This is a reminder that the next general IRC meeting is on the 5th February 2014 at 02:00 UTC. Koha community members are encouraged to attend. To find out what time the meeting is in your time zone go to: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M… Please add any items that you have to the agenda at: http://wiki.koha-community.org/wiki/General_IRC_meeting_5_February_2014 Updates from current role holders - please add an update to the agenda if you are expected to give an update but cannot attend (current role holders - http://wiki.koha-community.org/wiki/Roles_for_3.16) Information about IRC - if you are new to IRC see http://koha-community.org/get-involved/irc/ and http://www.wikihow.com/Get-Started-with-IRC-%28Internet-Relay-Chat%29 David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 h. +64 4 9720 600 | m. +64 21 0537 847 | w. +64 4 8906 098

1 0

Restoring the koha database
by Sandeep Bhavsar 01 Feb '14

01 Feb '14

Respected All I have taken the backup of our school library database in sql from koha ver 3.07.00.017 and installed koha 3.12 now. When I am restoring the database I am getting the error in rebuild_zebra.pl line 539 for few records. Is it the error of mysql database structure, Please help me to solve this problem. -- *Regards * *Sandeep Bhavsar* B.com, M.Lib.I.Sc SET, M.Phil, American Library Association - FERA 2011 fellow Librarian Dr. V N Bedekar Institute of Management Studies Thane (W) 400601 Mumbai INDIA Mobile : 9987049099 www.vpmthane.org

2 1

Re: [Koha] Upgrading from 3.02.02 (tarball install) to latest
by Steven Nickerson 31 Jan '14

31 Jan '14

THANK YOU Robin!!! That worked and did exactly what I needed it to and was now able to successfully complete my upgrade. I really appreciate the help! Steve -----Original Message----- Date: Fri, 31 Jan 2014 11:31:12 +1300 From: Robin Sheat <robin(a)catalyst.net.nz> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Upgrading from 3.02.02 (tarball install) to latest (package install) Message-ID: <1391121072.890.1.camel@zarathud> Content-Type: text/plain; charset="UTF-8" On do, 2014-01-30 at 17:07 -0500, Steven Nickerson wrote: > So, > when I run the 'koha-create' on the new system the DB schema isn't > named the > same as the one contained in the MySQL backup that is restored in the > next > step and I therefore don't have any data in the "new" version. Anyone > have > any suggestions on how to resolve this properly? Oh, easy. Where the instructions say: $ sudo koha-mysql <instancename> < mybackup.sql instead do: $ sudo koha-mysql <instancename> ... mysql> \. mybackup.sql This will mean the whole thing doesn't run in a transaction, and the CREATE DATABASE and USE lines will fail, but this won't abort the whole import like it does the first way. -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

1 0

Upgrading from 3.02.02 (tarball install) to latest (package install)
by Steven Nickerson 30 Jan '14

30 Jan '14

Hi everyone, I'm managing an older, running 3.02.02 install that was done via tarball install and I'd like to both move to the package install and upgrade to the latest 3.14.x version. I've tried following the instructions at http://wiki.koha-community.org/wiki/Moving_an_installation_from_a_regular_in stall_to_the_Debian_packages to migrate from tarball to package installs but find that my DB schema in MySQL doesn't seem to follow the current naming "standards" and is named 'kohadb' instead of 'koha_<sitename>'. So, when I run the 'koha-create' on the new system the DB schema isn't named the same as the one contained in the MySQL backup that is restored in the next step and I therefore don't have any data in the "new" version. Anyone have any suggestions on how to resolve this properly? I also then received errors during the "sudo koha-upgrade-schema <instancename>" step, but I'm pretty sure that was because of the issue with the schema names. Sound familiar to anyone (has anyone upgraded from 3.02.02 directly to some fairly recent version or have most people done "incremental" upgrades along the way so they didn't have this issue? Thanks for any help anyone can offer! Steve

2 1

Duplicate checks in acquisitions module
by Manos PETRIDIS 30 Jan '14

30 Jan '14

Hi people, just a question on duplicate checks: Trying to use koha bit by bit, I've been lately adding my Amazon wishlists to koha suggestions. The other day I bought a book from my suggestions list and marked the suggestion as accepted. Upon the book's arrival, I entered it in koha. Then, some days later, I decided to use the acquisitions module for the first time, taking this last book as an example. Well, to make a short story shorter, koha let me enter a duplicate entry, at least as ISBN is concerned. https://dl.dropboxusercontent.com/u/22465174/20140125_koha_a.JPG https://dl.dropboxusercontent.com/u/22465174/20140125_koha_b.JPG https://dl.dropboxusercontent.com/u/22465174/20140125_koha_c.JPG https://dl.dropboxusercontent.com/u/22465174/20140125_koha_d.JPG Koha usually checks for similar entry attempts, but apparently not when one does it via acquisitions. Is this normal, do I miss something? I use the latest koha packages, on debian, and have only a single library defined. Kind regards, Manos PETRIDIS http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8631

1 0

Re: [Koha] barcode
by Sina Stewart 30 Jan '14

30 Jan '14

no i did't think so , the field null in myql Date: Thu, 30 Jan 2014 20:29:01 +0530 Subject: Re: [Koha] barcode From: shiv.mail(a)gmail.com To: sina_sina1984(a)live.com it may be a blank space before the barcode On 30 January 2014 18:44, Sina Stewart <sina_sina1984(a)live.com> wrote: still not working , the field of barcode in items NULL , not saving any data ! Date: Thu, 30 Jan 2014 15:05:24 +0530 Subject: Re: barcode From: vishal.patil(a)osslabs.biz To: sina_sina1984(a)live.com CC: koha(a)lists.katipo.co.nz Reindex the zebra using/misc/migrationtools/rebuild_zebra.pl -b -r -v -x Then start zebra using, zebrasrv -f /koha/etc/koha-conf.xml & hope this work for you!!!!!!!!! On Thu, Jan 30, 2014 at 2:58 PM, Sina Stewart <sina_sina1984(a)live.com> wrote: i'm using koha V.3.14 , Ubuntu 12.04 ,latest V. of zebra , there are a big problem for me , i can't search by barcode , i have 3.8 and no problem with barcode indexing , any help -- Regards, Vishal Patil Landline number:02232080161 E-Mail: vishal_wpatil(a)nucsoft.co.in vishal.patil(a)osslabs.biz. _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Shivendra 9815526163 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation

1 0