- Koha - lists.katipo.co.nz

General IRC meeting tomorrow
by Brendan Gallagher 04 May '16

04 May '16

Hello all - General IRC meeting tomorrow Time converter for your time zone. http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M… Agenda https://wiki.koha-community.org/wiki/General_IRC_meting_4_May_2016 Looking forward to seeing you there. -- Sent from Gmail Mobile

1 0

RCM Libary - Koha Implementation - Server Architecure Set-up Best Practices?
by Craig Butosi 03 May '16

03 May '16

Dear CW, I'm happy to announce that, after considerable deliberation, the Royal Conservatory of Music Library in Toronto is implementing Koha ILS, with a projected go-live date of 1 September 2016. In partnership with our IT department, the library is beginning the first stages of the implementation. Our IT director had a question at a recent meeting regarding common server architecture set-up. We are a small library (+/-170000 lines of data across 6 SQL tables) with a user base of about 600. The library has about 70000 items. He was curious about how Koha libraries who are hosting their own instance have set-up their server in terms of LAMP distribution and redundancy. For example, have you installed everything on one hardened server with some sort of RAID configuration and backup system, or do you have an application server, SQL server, and assets server, each with their own hardening, redundancy, and backup regiment? For vendors on the list who host Koha for client libraries, what is your common architecture set-up at your company? Any information or documentation referrals would be helpful, and off-list replies are welcome, too. Thanks all. Very much looking forward to the RCM being part of the Koha community. C Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER the royal conservatory TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca<http://www.rcmusic.ca/> Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.

1 0

Re: [Koha] Best practices for koha - journal migration using marcedit
by Paul A 03 May '16

03 May '16

At 09:39 PM 4/28/2016 +0000, Karl Holten wrote: >The MARC format has an individual record size limit of 99999 bytes, but >big serials in Koha can eclipse that size. The result is that really big >serials don't compile as valid MARC if you have a ton of items attached to >them. Thanks for the comment. I think that Indranil Das Gupta was proposing a direct intervention at MySQL level -- that's certainly what I am looking for. I'm uncertain as to _where_ the limit of 99999 bytes applies; it's the formal definition and MarcEdit probably respects that (I only have a very old version, and know very little about it, so cannot properly verify) but I don't think MySQL has any hard limits, nor has Koha unless I'm mistaken. Not at all sure about Zebra... I've just looked at one rather large record <http://opac.navalmarinearchive.com/cgi-bin/koha/opac-detail.pl?biblionumber…> but it has only 94 items (and MarcEdit swallows it, but it's only 31242 bytes, so nowhere near "the limit." We're looking at quite a few serial runs of over 100 years of monthly issues! already in ODS format so a direct import into MySQL might be the fastest way. I keep pushing this project to the back of the queue, but will have to face it sooner or later. Paul >You could try compiling to MARCXML, but I don't think the file importer >for Koha can handle MARCXML. > >The closest I got to creating a massive MRC serials record was to use >YAZ-MARCDUMP (http://www.indexdata.com/yaz/doc/yaz-marcdump.html) to >convert the big MARCXML record into MARC21. It seemed to compile but it >was hard to tell. It wasn't valid MARC after all, and I couldn't exactly >look at it in MARCEDIT. > >Regards, >Karl Holten >Systems Integration Specialist >SWITCH Inc >414-382-6711 > >-----Original Message----- >From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Paul A >Sent: Thursday, April 28, 2016 2:39 PM >To: koha <koha(a)lists.katipo.co.nz> >Subject: Re: [Koha] Best practices for koha - journal migration using marcedit > >At 08:24 PM 4/28/2016 +0530, Indranil Das Gupta wrote: >[snip > > > I would like to know how to covert excel data of journals especially > > > with large number of issues(having more than 600 issues) for each > > > journal. Tried using marcedit and it is giving error - 501 when > > > trying to covert mrk to mrc format. >[snip] > > > Is there any other way how I can covert this data to mrc format. > > > >Yes, if you do programming or have access to a programmer adept at > >handling MARC21 data, you can. > >If you have details, please make them available. We looked into this >(again after MarcEdit attempts), but ran into problems (from memory, >more_subfields_xml) ... and we've got about .25 million items to add ;=} > >Thanks -- Paul > >_______________________________________________ >Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz >https://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 2

Catalogue Items Quality Check.
by Decka David 03 May '16

03 May '16

During the course of setup in our library setup, cataloguers wish to have their work file created for catalogue purposes before a chief cataloguer do quality check for items then transfer of items to be displayed on the OPAC. Is there such as cataloguers work files in Koha and how can this be created? Any advice will be appreciated on how best I can advice the cataloguers or the chief cataloguer to use Koha about items quality check before displayed in OPAC. Thanks once again all. Decka PNG

3 3

Merge Records via List not working in Koha 3.22.x
by Sunil Sharma 01 May '16

01 May '16

Hello Friends, I am using Koha 3.22.5 on Debian 8 OS. I have many duplicate title in my catalog, So I want to merge such records through Koha List module using merge function, At the end of the process it will show succesfully merged. But in actual it will neither merge items from source to destination record nor it will delete the other records except reference as it worked in previous version Koha 3.18 or koha 3.20. Any pointers would be of help. -- Thanking you, Sunil Sharma

2 1

Re: [Koha] Koha Digest, Vol 126, Issue 46
by kinby elly 30 Apr '16

30 Apr '16

Thank you for inviting me .as long as possible try to give me the rules On Apr 30, 2016 2:54 AM, <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 > https://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. Merge Records via List not working in Koha 3.22.x (Sunil Sharma) > 2. Search By Barcode having 1, 2 or 3 digit not working in Koha > 3.20 or in 3.22 (Sunil Sharma) > 3. Re: Search By Barcode having 1, 2 or 3 digit not working in > Koha 3.20 or in 3.22 (Katrin Fischer) > 4. Re: Best practices for koha - journal migration using > marcedit (Karl Holten) > 5. Error thrown when updating items (wildness) > 6. Re: Error thrown when updating items (Indranil Das Gupta) > 7. Re: Error thrown when updating items (wildness) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 29 Apr 2016 16:39:36 +0530 > From: Sunil Sharma <koha.sunil007(a)gmail.com> > To: koha <koha(a)lists.katipo.co.nz> > Subject: [Koha] Merge Records via List not working in Koha 3.22.x > Message-ID: > < CACZW6WvxsjYdfLJoBYZNDDO5sDiPLXtJD1f-fnXiFFec8AHbOg(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Friends, > > I am using Koha 3.22.5 on Debian 8 OS. > > I have many duplicate title in my catalog, So I want to merge such records > through Koha List module using merge function, At the end of the process it > will show succesfully merged. But in actual it will neither merge items > from source to destination record nor it will delete the other records > except reference as it worked in previous version Koha 3.18 or koha 3.20. > > Any pointers would be of help. > > -- > Thanking you, > Sunil Sharma > > > ------------------------------ > > Message: 2 > Date: Fri, 29 Apr 2016 16:46:14 +0530 > From: Sunil Sharma <koha.sunil007(a)gmail.com> > To: koha <koha(a)lists.katipo.co.nz> > Subject: [Koha] Search By Barcode having 1, 2 or 3 digit not working > in Koha 3.20 or in 3.22 > Message-ID: > < CACZW6WvSUxabuZJPPNG_Fo96pTgY8-4qqTSRS8WEYzWWRTe5EA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Friends, > > I checked both Koha 3.20.x as well as Koha 3.22.x on Debian 8 OS, Zebra > version 2.0.61. My other search is working fine but when I search any > barcode having 1, 2 or 3 digit, the search result page will not reflect > proper search result both in Koha OPAC as well as on Staff-Admin page. > > For example, when I search 123 it will give the records having barcode as > 1231, 1232, 1233, same as if I will search for barcode 121 then it will > give result for biblio having accession no. 121220, 121121 and so on. Even > these barcodes (121 or 123) are present in Koha. > > Any pointers would be of help. > > -- > Thanks & Regards > Sunil Sharma > > > ------------------------------ > > Message: 3 > Date: Fri, 29 Apr 2016 16:11:09 +0200 > From: Katrin Fischer <Katrin.Fischer.83(a)web.de> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Search By Barcode having 1, 2 or 3 digit not > working in Koha 3.20 or in 3.22 > Message-ID: <57236B7D.2030503(a)web.de> > Content-Type: text/plain; charset=utf-8 > > Hi, > > How are you searching for the barcode? > Did you turn on the QueryAutoTruncate system preference? > > Hope this helps, > > Katrin > > Am 29.04.2016 um 13:16 schrieb Sunil Sharma: > > Hello Friends, > > > > I checked both Koha 3.20.x as well as Koha 3.22.x on Debian 8 OS, Zebra > > version 2.0.61. My other search is working fine but when I search any > > barcode having 1, 2 or 3 digit, the search result page will not reflect > > proper search result both in Koha OPAC as well as on Staff-Admin page. > > > > For example, when I search 123 it will give the records having barcode as > > 1231, 1232, 1233, same as if I will search for barcode 121 then it will > > give result for biblio having accession no. 121220, 121121 and so on. Even > > these barcodes (121 or 123) are present in Koha. > > > > Any pointers would be of help. > > > > > > ------------------------------ > > Message: 4 > Date: Fri, 29 Apr 2016 18:06:54 +0000 > From: Karl Holten <kholten(a)switchinc.org> > To: Paul A <paul.a(a)navalmarinearchive.com>, koha > <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Best practices for koha - journal migration using > marcedit > Message-ID: > < DM2PR0501MB1310C00218989F1E3515B919A7660(a)DM2PR0501MB1310.namprd05.prod.outlook.com > > > Content-Type: text/plain; charset="utf-8" > > As far as I know, Koha converts the MRC file into MARCXML format and populates the MySQL database with the information in it. So perhaps he wouldn't need to compile to MRC at all if he went that route. > > If I'm reading schemaspy right, MySQL has a hard limit of 2147483647 bytes, which is good enough for anyone's needs, I would hope. Zebra has a lower ceiling. I don't know what that is, but we ran into it after migration when we discovered that large serials were not showing up in search results. We deleted some legacy data, which pushed us below that size limit. We're moving to ElasticSearch soon enough and I'm hoping it's not going to be an issue there. (Knock on wood) > > Regards, > Karl Holten > Systems Integration Specialist > SWITCH Inc > 414-382-6711 > > -----Original Message----- > From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Paul A > Sent: Thursday, April 28, 2016 5:44 PM > To: koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Best practices for koha - journal migration using marcedit > > At 09:39 PM 4/28/2016 +0000, Karl Holten wrote: > >The MARC format has an individual record size limit of 99999 bytes, but > >big serials in Koha can eclipse that size. The result is that really > >big serials don't compile as valid MARC if you have a ton of items > >attached to them. > > Thanks for the comment. I think that Indranil Das Gupta was proposing a direct intervention at MySQL level -- that's certainly what I am looking for. > > I'm uncertain as to _where_ the limit of 99999 bytes applies; it's the formal definition and MarcEdit probably respects that (I only have a very old version, and know very little about it, so cannot properly verify) but I don't think MySQL has any hard limits, nor has Koha unless I'm mistaken. > Not at all sure about Zebra... > > I've just looked at one rather large record < http://opac.navalmarinearchive.com/cgi-bin/koha/opac-detail.pl?biblionumber… > > but it has only 94 items (and MarcEdit swallows it, but it's only 31242 bytes, so nowhere near "the limit." > > We're looking at quite a few serial runs of over 100 years of monthly issues! already in ODS format so a direct import into MySQL might be the fastest way. I keep pushing this project to the back of the queue, but will have to face it sooner or later. > > Paul > > > >You could try compiling to MARCXML, but I don't think the file importer > >for Koha can handle MARCXML. > > > >The closest I got to creating a massive MRC serials record was to use > >YAZ-MARCDUMP (http://www.indexdata.com/yaz/doc/yaz-marcdump.html) to > >convert the big MARCXML record into MARC21. It seemed to compile but it > >was hard to tell. It wasn't valid MARC after all, and I couldn't > >exactly look at it in MARCEDIT. > > > >Regards, > >Karl Holten > >Systems Integration Specialist > >SWITCH Inc > >414-382-6711 > > > >-----Original Message----- > >From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Paul A > >Sent: Thursday, April 28, 2016 2:39 PM > >To: koha <koha(a)lists.katipo.co.nz> > >Subject: Re: [Koha] Best practices for koha - journal migration using > >marcedit > > > >At 08:24 PM 4/28/2016 +0530, Indranil Das Gupta wrote: > >[snip > > > > I would like to know how to covert excel data of journals > > > > especially with large number of issues(having more than 600 > > > > issues) for each journal. Tried using marcedit and it is giving > > > > error - 501 when trying to covert mrk to mrc format. > >[snip] > > > > Is there any other way how I can covert this data to mrc format. > > > > > >Yes, if you do programming or have access to a programmer adept at > > >handling MARC21 data, you can. > > > >If you have details, please make them available. We looked into this > >(again after MarcEdit attempts), but ran into problems (from memory, > >more_subfields_xml) ... and we've got about .25 million items to add > >;=} > > > >Thanks -- Paul > > > >_______________________________________________ > >Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > >https://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> > > _______________________________________________ > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha > > ------------------------------ > > Message: 5 > Date: Fri, 29 Apr 2016 15:39:43 -0700 (MST) > From: wildness <lauraerinmann(a)gmail.com> > To: koha(a)lists.katipo.co.nz > Subject: [Koha] Error thrown when updating items > Message-ID: <1461969583153-5886331.post(a)n5.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Hi, > I'm running Koha 3.18.12.000 and I can this error when I try to update > items for a record: > > :21: parser error : Opening and ending tag mismatch: record line 6 and > datafield > </datafield> > ^ > :22: parser error : Opening and ending tag mismatch: collection line 2 and > record > </record> > ^ > :23: parser error : Extra content at the end of the document > </collection> > > the url pattern is something like this: > ../cgi-bin/koha/cataloguing/ additem.pl?op=edititem&biblionumber=''&itemnumber=''#edititem > > When I edit one of the fields on this screen it throughs the error above. > It seems like a xml error, but after some internet sleuthing I came up with > nothing. Can anyone help me out? Thanks! > > > > -- > View this message in context: http://koha.1045719.n5.nabble.com/Error-thrown-when-updating-items-tp588633… > Sent from the Koha-general mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 6 > Date: Sat, 30 Apr 2016 04:40:27 +0530 > From: Indranil Das Gupta <indradg(a)gmail.com> > To: wildness <lauraerinmann(a)gmail.com> > Cc: koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Error thrown when updating items > Message-ID: > < CAEm3SZ3nFruZkY+iRjv4BW4G-XXpjRCJaTTVWPOmnjyHccWTmw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > Just a hunch... did you by any chance edit / change your marc > framework or edit the xsl files or upgrade your Koha, before this > error started showing up? > > regards > -idg > > > > > On Sat, Apr 30, 2016 at 4:09 AM, wildness <lauraerinmann(a)gmail.com> wrote: > > Hi, > > I'm running Koha 3.18.12.000 and I can this error when I try to update > > items for a record: > > > > :21: parser error : Opening and ending tag mismatch: record line 6 and > > datafield > > </datafield> > > ^ > > :22: parser error : Opening and ending tag mismatch: collection line 2 and > > record > > </record> > > ^ > > :23: parser error : Extra content at the end of the document > > </collection> > > > > the url pattern is something like this: > > ../cgi-bin/koha/cataloguing/ additem.pl?op=edititem&biblionumber=''&itemnumber=''#edititem > > > > When I edit one of the fields on this screen it throughs the error above. > > It seems like a xml error, but after some internet sleuthing I came up with > > nothing. Can anyone help me out? Thanks! > > > > > > > > -- > > View this message in context: http://koha.1045719.n5.nabble.com/Error-thrown-when-updating-items-tp588633… > > Sent from the Koha-general mailing list archive at Nabble.com. > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > -- > 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 > > > ------------------------------ > > Message: 7 > Date: Fri, 29 Apr 2016 16:53:27 -0700 (MST) > From: wildness <lauraerinmann(a)gmail.com> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Error thrown when updating items > Message-ID: <1461974007897-5886333.post(a)n5.nabble.com> > Content-Type: text/plain; charset=us-ascii > > What's the path to these files? > > > > -- > View this message in context: http://koha.1045719.n5.nabble.com/Error-thrown-when-updating-items-tp588633… > Sent from the Koha-general mailing list archive at Nabble.com. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 126, Issue 46 > *************************************

1 0

Book Status shown as "Available" for checkout books
by Sunil Sharma 30 Apr '16

30 Apr '16

Hello Friends, I am using Koha 3.22.6 on Debian jessie. I am facing a major issue in Koha staff page. For example, if I have 5 copies under a record and I issued 4 books out of 5. Then when I search for this record in opac the opac search result page display result fine like 4 books check-out, 1 book available. But the same record on staff page display that 5 books as available. Even when I check the detail for that record under status it display checkout barcode status as checkout to "xyz" due date "xxxx" with Available under it, means both status. Is this any bug in Koha 3.22.x or any other reason. Any pointers would be of help. -- Thanks & Regards Sunil Sharma

1 0

Search By Barcode having 1, 2 or 3 digit not working in Koha 3.20 or in 3.22
by Sunil Sharma 30 Apr '16

30 Apr '16

Hello Friends, I checked both Koha 3.20.x as well as Koha 3.22.x on Debian 8 OS, Zebra version 2.0.61. My other search is working fine but when I search any barcode having 1, 2 or 3 digit, the search result page will not reflect proper search result both in Koha OPAC as well as on Staff-Admin page. For example, when I search 123 it will give the records having barcode as 1231, 1232, 1233, same as if I will search for barcode 121 then it will give result for biblio having accession no. 121220, 121121 and so on. Even these barcodes (121 or 123) are present in Koha. Any pointers would be of help. -- Thanks & Regards Sunil Sharma

2 2

Koha Community Newsletter: April 2016
by kohanews 30 Apr '16

30 Apr '16

Fellow Koha users: The Koha Community Newsletter for April 2016 is here: https://koha-community.org/koha-community-newsletter-april-2016/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Documentation for SIP2 support
by Hans Hvelplund Odborg 29 Apr '16

29 Apr '16

Hello Where can I find documentation for KOHA SIP2 support ? E.g. What fields are supported? Explanation of non-standard fields? Etc... Hans Hvelplund Odborg VP Software Development e: h.h.odborg(a)bibliotheca.com t: +45 30 23 59 40 | m: +45 30 23 59 40 linkedIn | facebook | youtube | website Vallensbækvej 22A, 2. th. | DK – 2605 Brøndby | Danmark bibliotheca

3 3