- Koha - lists.katipo.co.nz

Koha - notices and slips: how to include total amount outstanding on a notice
by Walker-Headon, Niamh - Systems Librarian 06 Jun '18

06 Jun '18

Dear Fellow Koha Users, I was wondering if anyone has managed to figure out how to include the total amount outstanding in a notice. In our case we do not charge fines, but once an item is subjected to the 'longoverdue.pl' process the replacement cost of the item is added to the patrons' accounts. We want to include the total amount in the notice re same, in addition to the replacement cost,[which we have in the notice] but can't seem to find the right table/column to include. I hope that makes sense. Any advice would be very welcome! Yours, Niamh Walker-Headon BA, MSc LIS, ALAI. Systems Librarian | Humanities Subject Liaison Library, Institute of Technology, Tallaght, Dublin 24, Ireland. Niamh Bean Uí hÉidín BA, MSc LIS, ALAI. Leabharlannaí córas |Leabharlannai sainábhair daonnachtaí. An Leabharlann, Institúid Technolaíocha, Tamhlacht, BÁC 24, Éireann. Tel: 00 353 (0)1 4042151 Web: http://library.it-tallaght.ie<http://library.it-tallaght.ie/> Find us on Facebook<https://www.facebook.com/LIbraryittallaght/> | Follow us on Twitter<https://twitter.com/LibraryITT> Tel: 00 353 (0)1 4042151 Idirlíon: http://library.it-tallaght.ie<http://library.it-tallaght.ie/> Ar Facebook<https://www.facebook.com/LIbraryittallaght/> |Ar Twitter<https://twitter.com/LibraryITT> The contents and any attachment of this e-mail are private and confidential. They are intended only for the use of the intended addressee. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are notified that any copying, forwarding, publication, review or delivery of this e-mail or any attachments to anyone else or any other use of its contents is strictly prohibited. You are prohibited from reading any part of this e-mail or any attachments. If you have received this e-mail in error, please notify the system manager. Unauthorised disclosure or communication or other use of the contents of this e-mail or any part thereof may be prohibited by law and may constitute a criminal offence. Internet e-mails are not necessarily secure. The Institute does not accept responsibility for changes made to this message after it was sent. Unless stated to the contrary, any opinions expressed in this message are personal to the author and may not be attributed to the Institute.

2 3

Sponsoring the Koha Community site server
by مسعود محمد الشريف 06 Jun '18

06 Jun '18

Hi Liz, Thank you a million for sponsoring the Koha Community site all this time. I will be very happy to help too. A cost sheet per year for hosting, running the site, and for maintaining the Koha portal content, etc. will help contributors decide on the period of sponsoring the site for. Thanks, Massoud Alshareef KnowledgeWare Technologies Est. > On 6 Jun 2018, at 2:56 PM, 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. Re: Help with funding the koha-community.org webserver > (Chris Brown) > 2. Re: Help with funding the koha-community.org webserver (Liz Rea) > 3. Re: Help with funding the koha-community.org webserver > (Michael Kuhn) > 4. Re: Help with funding the koha-community.org webserver > (Narcis Garcia) > 5. Re: Help with funding the koha-community.org webserver (Liz Rea) > 6. Koha - notices and slips: how to include total amount > outstanding on a notice (Walker-Headon, Niamh - Systems Librarian) > 7. SQL report with Comma Delimited Paramater (ksorbo) > 8. Re: Import the MARC21 with Item details (Laxmi Lal Menaria) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 6 Jun 2018 06:33:31 +0100 > From: Chris Brown <chris(a)stayawake.co.uk> > To: Liz Rea <wizzyrea(a)gmail.com> > Cc: koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Help with funding the koha-community.org webserver > Message-ID: > <CANo1qi2tyir0G=PBM-PFz18ZsKj5BHrREUrx12HdErjzLuinTg(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Liz, > > I would be happy to chip in if you come up with an easy way to pay. Perhaps > you could set up a PayPal account? > > Best Regards, > > Chris Brown > > >> On Tue, Jun 5, 2018 at 10:21 PM, Liz Rea <wizzyrea(a)gmail.com> wrote: >> >> Hi all, >> I've been funding the koha-community web server for about 5 years now, and >> I've been happy to have the disposable income available to me to do that >> personally. As it turns out, this year I don't really have that and I could >> really use some help paying for it. >> >> The server is paid for yearly, this year it was $308 NZD It's all paid up >> until June of next year. >> >> If you'd be interested in tossing a few dollars my way to support running >> the website, I'd be really grateful. I think it would be better to have a >> community funded server anyway. I'm happy to keep looking after the server >> and website too. >> >> I don't have a plan currently for how best to receive the funds - ideas >> welcome on this front as well. >> >> Thanks for your consideration, >> >> Cheers, >> Liz >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > > > ------------------------------ > > Message: 2 > Date: Wed, 6 Jun 2018 17:41:22 +1200 > From: Liz Rea <wizzyrea(a)gmail.com> > To: Chris Brown <chris(a)stayawake.co.uk> > Cc: koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Help with funding the koha-community.org webserver > Message-ID: > <CAD+xdkT_uvy1LAPTzbQ71uryj8yD2gvh9R7g8Di4CCQ9dULPQQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Oh everyone, you are really the best folks anywhere. > > I have set up a ko-fi at https://ko-fi.com/lizrea and you can contribute > there > > Why don't you all chip in a little and we can get this done lickety split > and tjay way nobody gets stuck with it all <3 <3 > > Thank you all so much! > > Liz (wizzyrea) > > On 6 Jun 2018 17:33, "Chris Brown" <chris(a)stayawake.co.uk> wrote: > > Liz, > > I would be happy to chip in if you come up with an easy way to pay. Perhaps > you could set up a PayPal account? > > Best Regards, > > Chris Brown > > >> On Tue, Jun 5, 2018 at 10:21 PM, Liz Rea <wizzyrea(a)gmail.com> wrote: >> >> Hi all, >> I've been funding the koha-community web server for about 5 years now, and >> I've been happy to have the disposable income available to me to do that >> personally. As it turns out, this year I don't really have that and I could >> really use some help paying for it. >> >> The server is paid for yearly, this year it was $308 NZD It's all paid up >> until June of next year. >> >> If you'd be interested in tossing a few dollars my way to support running >> the website, I'd be really grateful. I think it would be better to have a >> community funded server anyway. I'm happy to keep looking after the server >> and website too. >> >> I don't have a plan currently for how best to receive the funds - ideas >> welcome on this front as well. >> >> Thanks for your consideration, >> >> Cheers, >> Liz >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Search error
by Thirunagalingam S.S. 06 Jun '18

06 Jun '18

Hi, We are from India. We are using 3.20.08.000 on Ubuntu server. We encounter the below mentioned error when we search the catalogue. Software error: Illegal division by zero at /usr/share/koha/intranet/cgi-bin/catalogue/search.pl line 631. For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. Need help urgently. SIDO

2 1

Framework warnings on upgrade to 18.05 (From 17.11.04)
by Elaine Bradtke 05 Jun '18

05 Jun '18

Background: We have a test system that we run on a different server. When we first installed Koha (3.?) many years ago, I managed to corrupt the default framework. I then overwrote the default framework with a clean one in the production site. We periodically clone the database from production to the test site to keep it fairly current. However, it appears that the framework isn't being copied (otherwise, I don't know how to explain the differences - the items in the list are not things we've changed, but may have resulted when the framework was corrupted). Below is a message generated while upgrading the test site to 18.05. Comparing this list to the production site, I find that the production site is 'standard' and test site deviates from this. *Question 1:* If I import the (standard) Default framework from production and overwrite the one in test, will this correct the problem, or do I need to import and overwrite all the frameworks? Do we need to do anything with the system to implement the changes in the subsidiary frameworks? *Question 2:* If you clone the database, does it not include the frameworks? (warning, I'm not the one who does this task, so I don't fully understand it). Is there something we need to do to make sure that it does copy the frameworks? Here's the message from the test site: WARNING: The Default framework is now considered as authoritative for Koha to MARC mappings. We have found that your additional frameworks contained 43 mapping(s) that deviate from the standard mappings. Please look at the following list and consider if you need to add them again in Default (possibly as a second mapping). Field 250$a in framework ART: Mapping to biblioitems.volume has been adjusted. Field 250$b in framework ART: Mapping to biblioitems.number has been adjusted. Field 490$a in framework ART: Mapping to biblio.seriestitle has been adjusted. Field 650$a in framework ART: Mapping has been reset. Field 700$a in framework ART: Mapping has been reset. Field 942$e in framework ART: Mapping has been reset. Field 942$k in framework ART: Mapping has been reset. Field 942$s in framework ART: Mapping has been reset. Field 952$f in framework ART: Mapping has been reset. Field 700$a in framework BKS: Mapping has been reset. Field 942$e in framework BKS: Mapping has been reset. Field 942$k in framework BKS: Mapping has been reset. Field 650$a in framework CF: Mapping has been reset. Field 942$e in framework CF: Mapping has been reset. Field 942$k in framework CF: Mapping has been reset. Field 245$b in framework FA: Mapping has been reset. Field 952$x in framework FA: Mapping to items.paidfor has been adjusted. Field 245$b in framework PRG: Mapping has been reset. Field 650$a in framework PRG: Mapping has been reset. Field 700$a in framework PRG: Mapping has been reset. Field 774$w in framework PRG: Mapping to biblio.biblionumber has been adjusted. Field 942$e in framework PRG: Mapping has been reset. Field 942$k in framework PRG: Mapping has been reset. Field 952$f in framework PRG: Mapping has been reset. Field 264$a in framework RDA: Mapping to biblioitems.place has been adjusted. Field 264$b in framework RDA: Mapping to biblioitems.publishercode has been adjusted. Field 264$c in framework RDA: Mapping to biblio.copyrightdate has been adjusted. Field 700$a in framework RDA: Mapping has been reset. Field 942$e in framework RDA: Mapping has been reset. Field 942$k in framework RDA: Mapping has been reset. Field 952$f in framework RDA: Mapping has been reset. Field 942$e in framework SER: Mapping has been reset. Field 942$k in framework SER: Mapping has been reset. Field 245$b in framework SR: Mapping has been reset. Field 650$a in framework SR: Mapping has been reset. Field 700$a in framework SR: Mapping has been reset. Field 774$w in framework SR: Mapping to biblio.biblionumber has been adjusted. Field 942$e in framework SR: Mapping has been reset. Field 942$k in framework SR: Mapping has been reset. Field 952$f in framework SR: Mapping has been reset. Field 650$a in framework VR: Mapping has been reset. Field 942$e in framework VR: Mapping has been reset. Field 942$k in framework VR: Mapping has been reset. Thanks! Elaine Bradtke 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 2

Is zebra server needed when using Elastic Search with 17.11-02 ?
by David Holoshka 05 Jun '18

05 Jun '18

Hi, Starting from version 17.11-02 we have made extensive changes to koha to get elastic search working in koha. We don't run the zebra server but we see an error in the about box saying that it is not running. Everything seems to work but we are wondering what functions need zebra even though we only use ES ? Best Regards, Dave

2 1

Error when searching using Zebra index 'arp'
by Barton Chittenden 04 Jun '18

04 Jun '18

I'm trying to trouble-shoot an error with the 'arp' index (accelerated reading point -- indexed at 526$d). I'm searching for arp:14 In the staff client and opac and getting no results. I added 'request' to zebra_loglevels in $KOHA_CONF and found the following error: 09:30:50-04/06 zebrasrv(98) [request] Search biblios ERROR 114 1 1+0 RPN @attrset Bib-1 @attr 1=9013 @attr 2=3 14 A google search for 'zebra ERROR 114' lead me to https://lists.katipo.co.nz/public/koha/2015-September/043604.html Which fixed the error by switching from GRS to DOM ... I didn't think that was the problem, but I checked anyway, $KOHA_CONF *does* show <zebra_bib_index_mode>dom</zebra_bib_index_mode> http://lists.indexdata.dk/pipermail/zebralist/2009-November/002326.html Says "I am told by those in the know that the ERROR 114 refers to an unknown / unmapped MARC field." Here's how it's indexed in biblio-koha-indexdefs.xml:  <index_subfields tag="526" subfields="d"> <target_index>arp:w</target_index> <target_index>arp:n</target_index> </index_subfields> in biblio-zebra-indexdefs.xsl: <xslo:for-each select="marc:subfield"> <xslo:if test="contains('d', @code)"> <z:index name="arp:w arp:n"> <xslo:value-of select="."/> </z:index> </xslo:if> </xslo:for-each> According to indexdata's git site: "error 114 - unsupported use attribute." http://git.indexdata.com/?p=idzebra-moved-to-github.git;a=commit;h=10d6601c… Looking in ccl.properties and bib1.att, I see that we have two indexes using attribute 9013; I'm not sure if that's the problem or not... grep 9013 /etc/koha/zebradb/ccl.properties not-onloan-count 1=9013 4=109 arp 1=9013 r=r grep 9013 /etc/koha/zebradb/biblios/etc/bib1.att att 9013 not-onloan-count att 9013 arp Any suggestions welcome! Thanks, --Barton

1 1

Possible Bug in bulkmacimport.pl
by ksorbo 04 Jun '18

04 Jun '18

When running bulkmarcimport.pl with the -d option (truncate tables), I get an error stating Foreign Key violation. Is it possible that the foreign keys are not set to 0 before the truncate commands are given? -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

2 2

cover images
by Lisa Peel 04 Jun '18

04 Jun '18

Hello I am in the process of preparing to migrate one library catalogue (non-koha) into another (koha) and have a question regarding cover images. One location/library is using Google Images for their cover images but the new one would like to add their own to any records where an image is not available from Google. Is it possible to do this? So for example, koha would initially look for a local cover image and if there is not one available pull the one from Google Images. They also have some issues regarding some of the Google images which are not a consistent size (some seem to come out as small thumb nails rather than the ‘regular’ size but I don’t know if there is something in koha to standardise this. Any help appreciated! Regards Lisa Ms Lisa Peel, Head of Learning Resources, SEG Services Swiss Education Group Rue du Centre 1 CH-1820 Montreux, Switzerland Mobile: +41 (0)79 228 0151 Email: lpeel(a)swisseducation.com<mailto:lpeel@swisseducation.com> Skype: biblio1897<skype://biblio1897> Web: www.swisseducation.com<http://www.swisseducation.com/> [http://signature.swisseducation.com/SEG.jpg]<http://signature.swisseducation.com/link.php?l=SEG> Confidentiality and Disclaimer: This message contains confidential information and is intended only for the individual named. Email messages are provided for informational purposes, therefore the sender does not accept liability for any errors or omissions in the contents of this message.

2 3

Serials data migration
by Puneet Saini 04 Jun '18

04 Jun '18

Dear Sir/ Madam, Kindly clear my below mentioned doubts, 1. currently we are using easy lib software and trying to migrate data from easylib to KOHA. We have successfully migrate our easylib data into KOHA like Books/ Bound journals etc. 2. Help me, how to migrate current subscription data into KOHA with below mentioned process. * What will be process to maintain current print subscription journals price along with all information. * Process to manage if any issue is missing in current year subscription then how to calculate KOHA automatically missing issue price ( Yearly Journal price/ No of issues) * Every year print Journals price varies because of USD. then what will be the process to manage every year journal price. * This will help us to take report of current year and past year missing issue cost for claim purpose. 3. We are using KOHA 17.11 Version 4. Through serial module in KOHA we can manage all bibliographic data but i am unable to find out where we have put in journal price every year to get above mentioned reports. Looking forward a positive reply. Have a nice day !! Regards, Puneet Kumar

1 0

Single Sign-On via Drupal
by Michael Kuhn 03 Jun '18

03 Jun '18

Hi The KDZ Zentrum für Verwaltungsforschung in Vienna (Austria) is trying to connect Koha to the user database of a Drupal 7 instance via CAS. The goal would be to have a Single Sign-On / SSO solution with the user database of Drupal. No Koha-only user accounts would be required. At the moment we are using the CAS module of Drupal, which provides a CAS server, and have connected it with the CAS authentication plugin of Koha. Authentication and login works, however only if users are already existing in Koha. The problem is: users are not automatically created in Koha, so the actual solution does not work without manually creating the user in Koha first. Thus, for the solution to properly work we'd need to find a way to auto-create the user accounts in Koha. 1. We've noted that the Shibboleth plugin has some auto-create option, that the CAS plugin seems to miss. Is there a way to have auto-creation work via CAS also? 2. Instead of the auto-create option, we've been thinking about some automated cron job that imports users in CAS on a regular basis based upon some CSV export provided by Drupal. A delay of a few hours until user accounts are created would be acceptable. Bug 12598 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12598) mentions that Koha 18.05 comes with CLI support for the user import tool ("import_patrons.pl"), so we have been considering using that for repetitive user imports. For that purpose, we could easily provide a CSV file in the desired format with Drupal. Does that seem like a doable approach? 3. Besides creating users with the correct user name, we'd have to map access levels to Koha as well. Would that be doable with the CSV import? 4. Setting a password on users in Koha is not necessary, as login should happen via the CAS interface. Is there a way to disable the password? Else we'd consider to just set an impossible-to-guess password for the accounts, so login would only work via Drupal. Has anybody done something like this before? Any hints or ideas would be highly appreciated! Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

2 1