- Koha - lists.katipo.co.nz

Loading of remote hosted XSLT failing for both http / https
by Indranil Das Gupta 10 Dec '18

10 Dec '18

Hi all, Trying to load a remote XSLT via XSLTResultsDisplay syspref as given in 18.05 user manual. Neither http nor https works (FWIW, I'm aware of the FQA status of bug #12758) With https i'm hitting line 310 of XSLT_Handler.pm and with http it is line 320. Enviroment: Debian 8.10 / Koha 18.05.06; plack enabled, memcached enabled, site on LE cert with perm re-direct to https. Does this work? tia -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

Subject Headings Display in OPAC
by Tami Wilkerson 08 Dec '18

08 Dec '18

Hello, Koha newbie here, so please pardon my ignorance! Is there a way to choose which 650 fields display in the OPAC? I would like ours to only show Library of Congress subjects (650 0_0) and suppress all others. Thank you, Tami Tami Wilkerson Library Program Lead/Librarian Columbia River Inter-Tribal Fish Commission StreamNet Regional Library 700 NE Multnomah St. Suite 515 Portland, OR 97232 twilkerson(a)critfc.org<mailto:twilkerson@critfc.org> / 503.736.3581

4 3

import with file.xsl
by anabela semedo 07 Dec '18

07 Dec '18

hi i need to import data with z39.50 from Library of Portugal with file.xsl because the tags is not a same. hi have a problem when import the their field 700 to our field 100 because their are the subfields 700$a$b and we are only 100$a and i can not calling de firstname of authors.  <xsl:call-template name="transform-personal-name"> <xsl:with-param name="srcTag">700</xsl:with-param> <xsl:with-param name="dstTag">100</xsl:with-param> <xsl:with-param name="srcCodes">abf</xsl:with-param> <xsl:with-param name="dstCodes">ad</xsl:with-param> </xsl:call-template>  <xsl:call-template name="transform-personal-name"> <xsl:with-param name="srcTag">701</xsl:with-param> <xsl:with-param name="dstTag">700</xsl:with-param> <xsl:with-param name="srcCodes">ab</xsl:with-param> <xsl:with-param name="dstCodes">a</xsl:with-param> </xsl:call-template>  <xsl:call-template name="transform-personal-name"> <xsl:with-param name="srcTag">702</xsl:with-param> <xsl:with-param name="dstTag">700</xsl:with-param> <xsl:with-param name="srcCodes">ab</xsl:with-param> <xsl:with-param name="dstCodes">a</xsl:with-param> </xsl:call-template> It's the same with 701 and 702. can someone help me? Ana Bela

2 2

Load Balancing with Koha
by Mutsikiwa Admire 07 Dec '18

07 Dec '18

Hi Just wondering if it is possible to have a Koha implementation in which we have a front-end Load Balancer such as NGINX or HAProxy, several Koha web server instances powered by one database server running on a separate server with balancing from source with stick-table in the case of HAProxy. <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=18&cad=rja&ua ct=8&ved=2ahUKEwj_gtyilobfAhVqSBUIHeMLADsQFjARegQIABAB&url=http%3A%2F%2Fngin x.org%2Fen%2Fdocs%2Fhttp%2Fload_balancing.html&usg=AOvVaw1SHZO_7iym933we-rYd FYt> <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=18&cad=rja&ua ct=8&ved=2ahUKEwj_gtyilobfAhVqSBUIHeMLADsQFjARegQIABAB&url=http%3A%2F%2Fngin x.org%2Fen%2Fdocs%2Fhttp%2Fload_balancing.html&usg=AOvVaw1SHZO_7iym933we-rYd FYt> nginx Kind Regards, Admire Mutsikiwa ICT Projects Manager Libraries University of Zimbabwe <Tel:+263-4-303276> Tel:+263-4-303276 "It is easy to dodge our responsibilities, but we cannot dodge the consequences of dodging our responsibilities." Josiah Charles Stamp, 1880-1941, former director of the Bank of England

3 5

Opac issue after upgrade to 18.1
by Hugo Páscoa 07 Dec '18

07 Dec '18

Hi koha community I am using debian 9 with mariadb and upgraded to 18.11. The OPAC can query the database and returns the total number of results. But it doesnt shows biblio description, like title, autor, etc,... However it shows in place of every biblio description "place hold", "save to lists" and "Add to your card". And this options actualy work if use any. Can you please advice? Thanks in advance Hugo Páscoa

2 1

3M Bibliotheca self-check with Koha
by Peter Lau 07 Dec '18

07 Dec '18

We have bought a new 3M self-check machine from the Bibliotheca to work with Koha. Unfortunately, the vendor said that they cannot ping the IP with the port no but there is no response and show wrong IP no. Just wonder if there should be a way to find the correct IP & port no to use and also how to set it up properly in Koha. The self-check vendor has shown us that the self-check by itself can work but just can’t communicate with Koha. Thanks & regards, *Peter Lau* Librarian Tel: (852) 3977 9868 | Email: Peter.Lau(a)yccece.edu.hk | Fax: (852) 23384320 [image: https://docs.google.com/uc?export=download&id=1wiYZQsqhNTJZjyNbLJx-6ODZyoYE…] 2 Tin Wan Hill Road, Tin Wan, Aberdeen *YCCECE, Here We Grow Our Future | *www.yccece.edu.hk

3 2

Re: [Koha] Self Check - "Outsdanding fines block issue"
by Michael Kuhn 07 Dec '18

07 Dec '18

Hi Uğur Bulgan We had already set the Koha preference "AllFinesNeedOverride" to "don't require". But yes, a restart of the Koha SIP server did the trick. Thank you very much! (I also send this e-mail to the mailinglist "Koha" so it will be in the archive there, just in case anyone else will experence this problem in the future) Best wishes: Michael Kuhn -- 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 Am 07.12.18 um 07:38 schrieb Uğur BULGAN: > Hi Michael Kuhn > > You must set the "AllFinesNeedOverride" setting to "don't require" the system preferences. > Then you need to restart "SIP Server". It was solved this way. > > > Uğur BULGAN > Library Director > Suleyman Demirel University > > > -----Original Message----- > From: Michael Kuhn <mik(a)adminkuhn.ch> > Sent: Thursday, December 6, 2018 10:55 PM > To: Uğur BULGAN <ugurbulgan(a)sdu.edu.tr> > Cc: Uwe Böttcher <uwe.boettcher(a)whu.edu> > Subject: Re: [Koha] Self Check - "Outsdanding fines block issue" > > Hi Ugur Bulgan > > On 27 July 2017 you wrote the following to the mailinglist "Koha": > > ##### BEGIN ##### > > We are recently using Koha 3.14.02. version and we updated this version to the 16.11.07 version and we begun testing this newer version. But we ran into a problem with selfcheck device in the tests we did. > > Our library users can borrow and place holds on materials until the overdue fine is 10 TL. They can not borrow when the overdue fine is over > 10 TL. When we operate on the staff client there is no problem in the new version and the system is running properly. > > However when we operate with the SelfCheck (3M) device, we get "outstanding fines block issue" error when library users' overdue fine is below 10 TL. Why do we get this error on selfcheck when there is no problem on staff client? Could there be a situation related to SIP2 server settings? > > ##### END ##### > > Our library using Koha 17.11 seems to experience exactly the same problem. > > Unfortunately the thread doesn't give a solution to the described problem so I don't know if it still exists or if you were able to solve it. Would you maybe care to share your solution with us if there is any? > > Best wishes: Michael Kuhn > -- > 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

1 0

DEV IDEA: Ability to specify number of purchase suggestion a patron can make in a specified rolling number of weeks
by Rhonda Kuiper 07 Dec '18

07 Dec '18

Hi All, We at Round Rock would like to co-sponsor a development that would allow a library to specify the number of purchase suggestions a patron can make in a specified number of weeks. The weeks would be rolling. Example: Library specifies that patron can have 3 purchase suggestions in 4 rolling weeks. Patron A submits a suggestion on November 28. They then submit another 2 suggestions on December 14. Koha will not allow them to make another suggestion until December 26. If they submit a purchase suggestion on December 26, Koha will not allow the next suggestion until January 11. Bywater estimated this development at $2,500. Is anyone interested in co-sponsoring this with us? Rhonda Kuiper Collection Development & Technical Services Manager | Round Rock Public Library (512) 218-3283 | fax: (512) 218-7061 | http://www.roundrocktexas.gov/library What I'm reading now: The Leadership Challence by James M. Kouzes and Barry Z. Posner The Great Alone by Kristin Hannah (listening on RBdigital)

1 0

DEV IDEA: Sysprefs to specify what gets copied for a duplicate patron and a child patron
by Rhonda Kuiper 07 Dec '18

07 Dec '18

Hi All, We at Round Rock are looking at co-sponsoring a development that would create two new system preference. One that lets the library specify which fields get copied when creating a duplicate patron and one that lets the library specify which fields get copies when creating a child patron. Bywater gave us an estimate of $2,000 for this development. We are looking for other libraries that would like this function and are willing to co-sponsor with us. Any takers? Rhonda Kuiper Collection Development & Technical Services Manager | Round Rock Public Library (512) 218-3283 | fax: (512) 218-7061 | http://www.roundrocktexas.gov/library What I'm reading now: The Leadership Challence by James M. Kouzes and Barry Z. Posner The Great Alone by Kristin Hannah (listening on RBdigital)

1 0

Filtering inventory results by cn_sort vs. callnumber
by Nick Clemens 07 Dec '18

07 Dec '18

Hello All! I put together a bug a while back for switching the sorting on inventory results filter from using 'callnumber' to the hidden/constructed column 'cn_sort' i.e. When inventorying a section by callnumber you would enter the range GT90 to GT100, Koha would then interpret this to (roughly) GT090 and GT100 as we do when constructing the cn_sort column. 'cn_sort' is the column we use to pad callnumbers with '0' and spaces to ensure that a callnumber of GT90 is sorted before GT100 (if sorted as normal strings 1 comes before 9) During review if the bug there was concern that some callnumber schemes may not work under this change, or some libraries might not have the cn_sort columns correctly filled and that we should add a system preference to control which column was used. On bug 21629 ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21629) we made sorting lists by callnumber use cn_sort by default. I am just writing to see if any libraries out there have concerns about the change, or if we think that always using cn_sort to filter the results would work. We want to be consistent throughtout the code (ideally) Let me know what thoughts you have and if you think we can simply assume cn_sort is the definitive column for sorting and defining ranges. -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

4 5