- Koha - lists.katipo.co.nz

CHAT: a new Adventure of Fred and the Avenging Chicken!
by King, Fred 15 Apr '20

15 Apr '20

Esteemed Colleagues everywhere, I hope everybody is staying well and safe. In my neck of the woods, most meetings, conferences...well, just about everything has been cancelled or postponed. So, since I can't chronicle exciting journeys to places unknown, here's the latest Adventure of Fred and the Avenging Chicken: COVID 19: Fred and the Avenging Chicken Don't go Much of Anywhere. I hope it brings you a needed chuckle. http://avengingchicken.online/spring2020/ Fred King, AHIP Medical Librarian, MedStar Washington Hospital Center fred.king(a)medstar.net<mailto:fred.king@medstar.net> 202-877-6670 ORCID 0000-0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org We've all got royal blood in our veins, you know. It's the best place for it in my view. --E.L. Wisty (Peter Cook) ---------------------------------------------------------------------- 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.

5 5

Re: [Koha] Taking patron images out of db into a directory
by dcook＠prosentient.com.au 14 Apr '20

14 Apr '20

Recently, I've been re-thinking the scalability of Koha, so it's interesting to hear about this from you, Mengu, as the person who I think runs the biggest Koha installation in the world. Originally, I thought putting images in the database was a bad idea, but it is an easy way to provide that image data over a network to multiple nodes and is part of an established community-supported application backup strategy. But fetching arbitrary blobs from a database could be slow and it could inflate Koha's metadata/transaction database. Storing image data in the database seems convenient - especially for small implementations - but is more problematic for large implementations. The probable solution to me for a large implementation is a network file share or object storage (e.g. AWS S3, Ceph, Minio, OpenStack Swift, etc). But that puts more of a burden on system administrators to make sure things are backed up. Not a problem for large implementations but it would be for small implementations. The ultimate solution to me would be a standard API (Koha::UploadedFiles I presume) in Koha with different storage backends. This is a common approach used by other FOSS systems. You can have drivers for database storage, file system storage, object storage - and you can choose the driver best suited to your situation with the default option being the most convenient for small implementations (ie probably database storage). Recently, we've locally provided an object storage integration to provide people with a robust low-cost method for storing documents in Koha, which seems to be working well. Using a caching layer would be nice too, so loading the same page 2 times doesn't equal 2 high cost trips to the data storage. I've been using the IIIF Image Server Loris backed by Fedora Commons backed by AWS S3 and caching makes a world of difference for end users. Anyway, that's my 2 cents. Ideally, the work done on this would be generalized, so that it could be used for things like biblio images, documents, etc. (I suppose storing URIs might be a useful way to do it. That way you could use file:///local/disk, file:///network/disk, s3://mybucket... maybe mysql://..) (I'd be interested too to hear about optimizations people have for serving image data. Starman won't perform this task as well as Nginx or Apache, but I think we need to have this data behind an authorization layer, which currently means Perl. But that's really a completely different discussion.) We might also want to move this from koha to koha-devel listserv? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- Date: Thu, 9 Apr 2020 17:40:17 +0300 From: Mengu Yazicioglu <mengu(a)devinim.com.tr> To: Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] Taking patron images out of db into a directory Message-ID: <e332b7e3-6a35-c7ab-3ff4-0b603b44af9c(a)devinim.com.tr> Content-Type: text/plain; charset=utf-8; format=flowed Hi all, We'd like to write a patch to move patron images out of db into a directory in the server. By this change, we'd like to satisfy following. 1. The size of database backup will be decreased, by this way one may store db backups more. 2. Database performance will increase 3. It will be possible to put patron images in different disk in the server 4. Easily put images gathered from other systems like (university system, personnel system, etc) What is your idea? -- Mengü Yazıcıoğlu Devinim Yazılım Eğitim Danışmanlık Reşit Galip Cad. No: 29/6 Çankaya/ANKARA Tel: (312) 446 86 68 Cep: (532) 701 90 27

1 0

Call for news: April 2020 Koha Newsletter
by Koha Newsletter 14 Apr '20

14 Apr '20

I'm collecting news for the April newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * Images are welcome. * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Bad 008 fields - how to find them
by Elaine Bradtke 14 Apr '20

14 Apr '20

An unknown number of biblios in our catalogue have bad 008 fields. I'd like to be able to fix them, but how do I find them? Two things I've noticed about the bad 008s, some lack a date, some have invalid codes in various positions. I'd like to produce a list of biblionumbers of records that are missing dates, or have invalid codes. Or possibly two lists one for dates, one for invalid codes. Is it possible to do this with a report? It's beyond my minimal skills in that area. 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

2 1

Education: Education meeting TODAY!
by Caroline Cyr-La-Rose 14 Apr '20

14 Apr '20

Hello everyone! A quick reminder that there is an education meeting today at 19UTC (3pm EDT). This meeting is open to everyone who is interested in training or education for Koha. Here is the summary of the last meeting we had in November: https://lists.katipo.co.nz/public/koha/2019-November/053887.html The meeting will take place in Zoom, graciously provided by ByWater Solutions https://zoom.us/j/95356522383 See you then! -- Caroline Cyr La Rose, M.L.I.S. Librarian | Product Manager Phone: 1-833-465-4276, ext. 221 Caroline.Cyr-La-Rose(a)inLibro.com <mailto:caroline.cyr-la-rose@inLibro.com> INLiBRO | Document Technologies Specialists | www.inLibro.com <http://www.inLibro.com>

1 0

Re: [Koha] Taking patron images out of db into a directory
by BRANNON, CHRISTOPHER 13 Apr '20

13 Apr '20

I would also like to suggest while you are doing this, please add a way to manage this directory from Koha. I would see it as a huge asset if an administrator could browse and manage these images, along with images for other things, such as cover images, or even an online repository an archive. ___________________________ Christopher Brannon IT Coordinator 702 E Front Ave Coeur d'Alene, ID 83814 (208)769-2315 Ext. 456 cbrannon(a)cdalibrary.org www.cdalibrary.org

1 0

Taking patron images out of db into a directory
by Mengu Yazicioglu 13 Apr '20

13 Apr '20

Hi all, We'd like to write a patch to move patron images out of db into a directory in the server. By this change, we'd like to satisfy following. 1. The size of database backup will be decreased, by this way one may store db backups more. 2. Database performance will increase 3. It will be possible to put patron images in different disk in the server 4. Easily put images gathered from other systems like (university system, personnel system, etc) What is your idea? -- Mengü Yazıcıoğlu Devinim Yazılım Eğitim Danışmanlık Reşit Galip Cad. No: 29/6 Çankaya/ANKARA Tel: (312) 446 86 68 Cep: (532) 701 90 27

6 13

Koha Community Newsletter: March 2020
by Koha Newsletter 10 Apr '20

10 Apr '20

The Koha Community Newsletter for March 2020 is here: https://koha-community.org/koha-community-newsletter-march-2020/ <https://koha-community.org/koha-community-newsletter-march-2020/> 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. -- Chad Roseburg Editor, Koha Community Newsletter

2 1

Roles for 20.11 now open
by Renvoize, Martin 07 Apr '20

07 Apr '20

Hi everyone, The role proposals page for the upcoming 20.11 development cycle is now available at https://wiki.koha-community.org/wiki/Roles_for_20.11 <https://wiki.koha-community.org/wiki/Roles_for_19.11> and we'd love to see some new names on the volunteers' list. The vote on roles will be held at the may irc general meeting and descriptions of what the roles entail can be found here: https://wiki.koha-community.org/wiki/Project_roles. Roles to draw your attention to: * Bug Wranglers - We can always do with more bug wranglers! These people love to keep things tidy and Bugzilla is always in need of your help. We need people to help manage 'the list', identifying the duplicates, promoting bugs to specialists and finding people to do signoffs and testing. Everyone is invited to this party, we need you! * Documentation Team - The documentation team is a growing team that's made great inroads into bringing Koha's documentation up to date and ensuring we have a really well-documented piece of software. There's plenty more to do and they're always on the lookout for new contributors. * Wiki Curators - Koha's wiki is bursting at the seams with good information, but we need your help to bring order to the chaos and keep improving the content. If you've got an interest in maintaining an area of the Wiki, helping identify out of date information or categorizing data then this is a job for you. * Quality Assurance Team - This vitally important team is always looking for new recruits! If you've got an eye for detail, or you're a tester who likes rolling up their sleeves a little bit and looking at how a piece of code works, then we'd love to hear from you. Again, there's always support available from 'the usual suspects' so don't shy away, why not make this your first cycle on the QA team and see how much fun it can be working with this important team. * Quality Assurance Topic Expert - Do you know one particular area of koha better than the rest? Are you the 'go to' guy (or gal) for SIP2, EDI, Acquisitions or another area of Koha? We'd like to hear from you too. You don't have to know the whole codebase to be a great QA Specialist, you're an expert in what you know and we always need more experts. Those are just a few highlights, please see the wiki page above for the full list. *Martin Renvoize* <https://www.ptfs-europe.com/> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

2 1

Connection to memcached servers failed after update to 19.11.04
by Alvaro Cornejo 07 Apr '20

07 Apr '20

Hi I have just updated koha from 19.11.02 to 19.11.04 and got the following erors during update. Upgrade to 19.11.04.000 done (19.11.04 release) 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. An process check shows: ps -ef |grep memcach memcache 676 1 0 Apr02 ? 00:03:10 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127.0.0.1 -P /var/run/memcached/memcached.pid Koha about page shows Memcached is working. Can I safely ignore those erors? Koha version: 19.11.04.000 PSGI: Plack (deployment) Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_library | Status: running. | Config read from: koha-conf.xml Regards, Alvaro |----------------------------------------------------------------------------------------| *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire

2 1