- Koha - lists.katipo.co.nz

Fwd: FW: Signoff request for bug 21190 [GDPR logging]
by Marcel de Rooy 30 Jan '20

30 Jan '20

See my request below. Unfortunately, it was not accepted by the mailing list due to added company signatures (with attachment). So here is another try. Marcel ---------- Forwarded message --------- Van: Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl> Date: do 30 jan. 2020 om 09:04 Subject: FW: Signoff request for bug 21190 [GDPR logging] To: rooy.de.m(a)gmail.com <rooy.de.m(a)gmail.com> *Van:* Marcel de Rooy *Verzonden:* woensdag 29 januari 2020 14:23 *Aan:* koha ml <koha(a)lists.katipo.co.nz> *Onderwerp:* Signoff request for bug 21190 [GDPR logging] Hi, See bug 21190. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21190 GDPR: Log successful/unsuccessful login attempts [part 1] Some people asked for it. I wrote something. I do not really need it myself. I waited three months, but to no avail. This is my last resort ;) If you are interested in such changes, please test and signoff. If no one is, I will not keep waiting but just happily close the report. Thanks, Marcel

2 1

upgrade tp 19.00.02-1 memcached error
by Alvaro Cornejo 30 Jan '20

30 Jan '20

Hi I´ve just upgrade to 19.11.02-1 and the upgrade showed the following errors regarding memcached. Setting up koha-common (19.11.02-1) ... Upgrading database schema for biblioteca Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Updated the es-ES translations. Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Updated the fr-FR translations. Setting up libsasl2-modules:amd64 (2.1.27~101-g0780600+dfsg-3ubuntu2.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... W: APT had planned for dpkg to do more than it reported back (15 vs 19). Affected packages: koha-common:amd64 After this, I restart memcached and it seems working: acornejo@CelacpVPS-2:/etc/sysctl.d$ sudo service memcached restart acornejo@CelacpVPS-2:/etc/sysctl.d$ sudo service memcached status ● memcached.service - memcached daemon Loaded: loaded (/lib/systemd/system/memcached.service; enabled; vendor preset Active: active (running) since Thu 2020-01-30 00:51:09 -05; 7s ago Docs: man:memcached(1) Main PID: 9050 (memcached) Tasks: 10 (limit: 4676) CGroup: /system.slice/memcached.service └─9050 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127.0.0.1 -P Jan 30 00:51:09 CelacpVPS-2 systemd[1]: Started memcached daemon. acornejo@CelacpVPS-2:/etc/sysctl.d$ And koha about shows memcached running: Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_library | Status: running. | Config read from: koha-conf.xml Is there something I should check? Regards Alvaro |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com

1 0

External Independent Security Audit of Koha
by dcook＠prosentient.com.au 30 Jan '20

30 Jan '20

Hi all, Fred King's email about using Koha in a Protected Health network reminded me of a question I wanted to pose around the world. Has anyone commissioned an external independent security audit of Koha? That is to say, a security audit from someone other than a Koha support vendor? If so, would they be willing to share the results with other Koha libraries? For instance, in Fred's case, he could refer his IT department to those results, so they could use it in their risk management analysis. (Of course, I think it would be important to note that security depends a lot on the implementation itself, the version of the Koha software, and so on. So one security audit report would not cover all implementations world-wide, but it could be a useful starting point.) I know that I've had IT departments interested in these third-party external independent security audits, so I imagine this is actually a common request that a lot of Koha users around the world are probably facing. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

relevance problem
by paweln 29 Jan '20

29 Jan '20

Hello everyone, I have problem with relevance. When I search and set relevance as ‘Publication/Copyright date: newest to oldest’, Koha returns records without any order? What may cause a problem? Best regards, Paweł Niedźwiadek -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

2 3

Fines till date
by paweln 29 Jan '20

29 Jan '20

Hello. I would like to charge fines till specified date, e.g. 20.01.2020. Before that day will be no fines, despite of checkout history. I could not find any description, how to do that. Probably I overlook something. I kindly ask for tips. Paweł -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

2 1

list of biblio without items and empty marc 773
by Alvaro Cornejo 29 Jan '20

29 Jan '20

Hi I´m trying to get a report of all biblios that does not have an item and marc 773 / * are empty/NULL or just 773 / 0. The issue is that when linking analytical monographic reccord to a specific biblio, field/subfields of 773 are populated with "parent" record information. Analitical Monographic record remains with no item so further queries still return those items. I tried several variations of the following query unsuccessfully SELECT CONCAT('<a href=\"/cgi-bin/koha/catalogue/detail.pl?biblionumber=',b.biblionumber,'\">',b.biblionumber,'</a>') AS RecEdit, b.title AS TITLE FROM systempreferences, biblio AS b LEFT JOIN items AS i ON b.biblionumber = i.biblionumber LEFT JOIN biblio_metadata AS m ON i.biblionumber = m.biblionumber WHERE i.itemnumber IS NULL AND systempreferences.variable='OPACBaseURL' AND (SELECT ExtractValue(metadata,'//datafield[@tag="773"]/subfield[@code="0"]') FROM biblio_metadata AS m WHERE m.biblionumber) IS NULL Any ideas as how to fix this query? Regards, Alvaro |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com

1 0

Cover image not shown in opac search result but biblio detail
by Alvaro Cornejo 29 Jan '20

29 Jan '20

Hi I´m running koha 19.11.002 and noticed that the opac search result does not show biblio some cover images; however biblio detail show it. On the intranet, image is shown in both, the search page and the biblio detail. I´ve checked all cover system preferences but found nothing that can help. In usercss I only add a line to remove ¨no cover image¨ /* Hide the no image found image */ .no-image { display: none !important; } If I remove that line, the no image icon appears for a couple of seconds and then disappears A side question, where are the local images stored? is there a marc record for that? Any ideas? Regards Alvaro |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com

1 0

Where has "OpacNavRight" gone?
by Michael Kuhn 29 Jan '20

29 Jan '20

Hi Today I was astonished when I was trying to edit Koha system preference "OpacNavRight" - there is no such preference anymore! Also the Koha 19.05 and 19.11 manuals don't mention this preference anymore. But the release https://koha-community.org/koha-19-11-release/ list the following bug as solved: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23253 (OpacNavRight does not display correctly for opacuserlogin disabled or self registration) However, we would like to fill the empty space of the right column under the main login form - at the moment it is completely white... Is this a bug or did I miss something? 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

4 5

Upgrade: Ubuntu 16.04.6 LTS / Koha 17.11.18.000
by Alex Shepherd 28 Jan '20

28 Jan '20

Hi Guys, I’m needing to update my Koha server that hosts 8 separate instances of Koha and just looking for any advice or guidance to reduce disappointment… Its on a Digital Ocean Droplet, which I’ve taken a SnapShot of and will test the upgrade on a cloned test instance from the snapshot before doing it on production, so its low risk but I want to avoid unforeseen issues that may not show-up for a while. I’m aware of the notes here: https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Upgrade_Inst… but they are quite brief and I kinda expect more issues than “it just works”… Maybe it does - I don’t know yet. It is currently running: Ubuntu 16.04.6 LTS Koha 17.11.18.000 MariaDB 10.0.38-MariaDB-0ubuntu0.16.04.1 The only “special” things I’ve done to this server are: A) install the IndexData repos: http://ftp.indexdata.dk/ubuntu xenial InRelease http://ftp.indexdata.dk/ubuntu xenial Release to upgrade Yaz and Zebra as there were issue with my Koha instances handling some Asian languages (Thai I believe) that were improved with the later versions. B) Add the Startup scripts to each MySQL DB to reset the sequence numbers etc on boot. Questions in my mind: 1) Do I just alter the APT Koha repo to say 19.11 and run update/upgrade in one step or is there a need to step through each major version to get there? 1) Should I also upgrade Ubuntu to 18.04 LTS or just leave it on 16.04 LTS? This might affect the Yaz and Zebra versions as well. Any comments or advice? Regards Alex Shepherd p: +64-7-829 4441 m: +64-21-777764 e: kiwi64ajs(a)gmail.com

2 1

FW: Koha on Digital Ocean (Was: Re: Installation on so-called virtual server at external internet service provider IONOS)
by King, Fred 28 Jan '20

28 Jan '20

(Reposted after it got stuck in moderation--too many recipients.) -----Original Message----- From: King, Fred Sent: Monday, January 27, 2020 12:48 PM To: 'Chris Brown' <chris(a)stayawake.co.uk>; Heinz-Jürgen Oertel <hj.oertel(a)t-online.de> Cc: koha <koha(a)lists.katipo.co.nz>; koha-us(a)koha-us.org Subject: Koha on Digital Ocean (Was: Re: [Koha] Installation on so-called virtual server at external internet service provider IONOS) Hello Chris, Heinz-Jürgen, and everybody, I'm glad to hear that someone else is using Digital Ocean! We're currently running the MedStar Authors Catalog Koha instance at Digital Ocean, and since I bought our in-house Koha instance server refurbished seven years ago and I'm getting kind of nervous, I'm trying to move that to Digital Ocean as well. I'm planning to start on the $5 USD per month configuration ($6 USD with weekly backup), though we may splurge for the $10/$12 configuration if we need to. Yes, we're a very small library--circulation is maybe in the high two figures per month and is mostly the Advanced Cardiac Life Support exam review book. Getting another in-house server isn't an option. My next step is a Technical Review Meeting with our IT department where I need to convince the Demand Management Team that Koha/Digital Ocean will not present a security threat to the rest of our network and the Protected Health Information contained therein. Our systems were attacked a couple of years ago and we were shut down for a couple of weeks (my desk has never been so tidy), so their concerns are understandable. The form they asked me to fill out was the same one that any software vendor chosen by the hospital needs to use, though in my case a lot of the answers were "not applicable." Which brings me to a few questions, some general and some Koha or maybe Digital Ocean specific: One of the things I think they'll ask me about is data encryption. The form I filled out asked the highest level--TLS 1.3, 1.2, 1.1, SSL 3.0 or less. Any ideas? Yes, it's a basic question that I should know, but there are large gaps in my knowledge as I'm mostly self-taught. They're also going to ask about antivirus protection. I have never heard of a Koha instance running on Debian/Ubuntu being affected by a virus or anything similar, and if it had happened I think I would have heard of it since I've been involved with Koha since version 2.something-or-other. Does anybody know something different? I'd also like to hear from other users of Digital Ocean, or from people whose Koha systems have had to undergo a review of this type. Any advice? I know enough about Koha, Ubuntu, and Digital Ocean to be able to set up, migrate, and run our small Koha system, enough to install it on a Raspberry Pi (http://avengingchicken.online/misc/installing_koha_on_raspberry-pi-4.pdf) take part in a panel discussion (http://koha-us.org/learn/conferences/kohacon2019/, see "Unsupported? You're not on your own!"), but this part is something new to me. Thank you, Fred King, AHIP Medical Librarian, MedStar Washington Hospital Center fred.king(a)medstar.net 202-877-6670 ORCID 0000-0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org Mars is the only known planet in the universe inhabited solely by robots. --Brandon Spektor, LiveScience -----Original Message----- From: Koha <koha-bounces(a)lists.katipo.co.nz> On Behalf Of Chris Brown Sent: Sunday, January 26, 2020 9:55 AM To: Heinz-Jürgen Oertel <hj.oertel(a)t-online.de> Cc: koha <koha(a)lists.katipo.co.nz> Subject: [EXTERNAL] Re: [Koha] Installation on so-called virtual server at external internet service provider IONOS ** ATTENTION: This email originated from outside the MedStar network. ** DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe. Hi Heinz-Jürgen, I don't have any experience of IONOS but I successfully host Koha on a virtual private server from Digital Ocean. For a long time we were running on a small configuration costing 20 USD per month though we have now upgraded as we're supporting 5 libraries (and a web site). I have had a smooth ride (though I do have prior experience of administering Linux servers). Digital Ocean will give you a VPS with Debian pre-installed which makes it easy to get started. If you're hosting in-house, some things to think about: 1. Does your ISP offer a static IP address? 2. You will need to set up a tunnel (or do I mean a bridge?) through your broadband router to your Koha server 3. You will need a way to do backups -- preferably off-site Good luck! Best Regards Chris Brown On Sun, Jan 26, 2020 at 12:53 PM Heinz-Jürgen Oertel <hj.oertel(a)t-online.de> wrote: > Hello, > just a short introduction, joined the list today. > I'm on the way to replace the currently used Allegro-B for our small, > about > 3000 books, library. The main reason is to have an OPAC to tell the > world what we have collected so far in our specialized library. > > We have two options > - installing koha on a separate pc (debian) on our premises, but so > far I don't know how can open the OPAC to the customers > > - installing koha on an external virtual server with root access My > question, is there someone here having it done at IONOS, the former > German company 1&1. > > Or to you have better recommendations. > By the way, money is a very small resource in our association, German > Verein e.V. > > Greetings > Heinz > > > > _______________________________________________ > Koha mailing list > https://urldefense.proofpoint.com/v2/url?u=http-3A__koha-2Dcommunity.o > rg&d=DwIGaQ&c=RvBXVp2Kc-itN3g6r3sN0QK_zL4whPpndVxj8-bJ04M&r=vKh6XwOmjy > C51IkP1OfsdjQZoWT2vpi6VZl8El8EPRI&m=d1e9HNijxpF-CFm6aDGu2L4sA9uNUSWxNY > OhmVfKlfY&s=PFaZDDXbAVaeRYYYQEEUYB394Eoew_4m7DdURTjQriU&e= > Koha(a)lists.katipo.co.nz > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.katipo.co.n > z_mailman_listinfo_koha&d=DwIGaQ&c=RvBXVp2Kc-itN3g6r3sN0QK_zL4whPpndVx > j8-bJ04M&r=vKh6XwOmjyC51IkP1OfsdjQZoWT2vpi6VZl8El8EPRI&m=d1e9HNijxpF-C > Fm6aDGu2L4sA9uNUSWxNYOhmVfKlfY&s=2YTTiymU3KGcGMBjQQzVdlLnADG5enBMFZZdo > gdgCtQ&e= > _______________________________________________ Koha mailing list https://urldefense.proofpoint.com/v2/url?u=http-3A__koha-2Dcommunity.org&d=… Koha(a)lists.katipo.co.nz https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.katipo.co.nz_mai… ---------------------------------------------------------------------- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopaedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you. Help conserve valuable resources - only print this email if necessary.

2 1