- Koha - lists.katipo.co.nz

Re: [Koha] Koha as Doc Man System
by dcook＠prosentient.com.au 22 Apr '20

22 Apr '20

You would need to clarify what you mean by "docs management system". If you're referring to a system as described by https://en.wikipedia.org/wiki/Document_management_system, then I would say no. Koha isn't a records management system nor is it a digital library. Koha is an integrated library system / library management system, which works by storing and indexing metadata about resources (e.g. books, DVDs, journal articles, et cetera). It doesn't store the resources themselves. There is some basic capacity to store arbitrary files in Koha, but not as sophisticated as you'd find in a document/record management system or digital asset management system. Of course, Koha is open source, so a person could always build document management functionality into Koha. But I would say it's not viable at present without work. 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: Tue, 21 Apr 2020 14:51:23 +0000 (UTC) From: Esmael Wan <opensistem(a)yahoo.com> To: koha(a)lists.katipo.co.nz Subject: [Koha] Koha as Doc Man System Message-ID: <1058923143.197341.1587480683421(a)mail.yahoo.com> Content-Type: text/plain; charset=UTF-8 Is it viable to consider Koha as a docs management system ? Regards Akla Esmael

2 1

Koha as Doc Man System
by Esmael Wan 21 Apr '20

21 Apr '20

Is it viable to consider Koha as a docs management system ? Regards Akla Esmael

2 1

Re: [Koha] Easy way to temporarily disable hold notice
by BRANNON, CHRISTOPHER 21 Apr '20

21 Apr '20

Can you simply not fill holds? Notices are generated if you fill holds. ___________________________ 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 Message: 2 Date: Mon, 20 Apr 2020 15:57:58 +0000 From: Holger Meissner <Holger.Meissner(a)hs-gesundheit.de> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Easy way to temporarily disable hold notice Message-ID: <2846715e750c490aa3e97bdd452e73e3(a)nExchange1.hsg.intra> Content-Type: text/plain; charset="us-ascii" Hi koha community, is there an easy way to temporarily disable the hold notice for all patrons? Letter code HOLD. We want to skip hold notices for a few weeks, then turn them back on. Is there a syspref? Do we have to manipulate the message preferences of every patron? Koha version 17.11. Thanks in advance, Holger ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz https://linkprotect.cudasvc.com/url?a=https://lists.katipo.co.nz/mailman/li… ------------------------------ End of Koha Digest, Vol 174, Issue 17 *************************************

4 3

Easy way to temporarily disable hold notice
by Holger Meissner 20 Apr '20

20 Apr '20

Hi koha community, is there an easy way to temporarily disable the hold notice for all patrons? Letter code HOLD. We want to skip hold notices for a few weeks, then turn them back on. Is there a syspref? Do we have to manipulate the message preferences of every patron? Koha version 17.11. Thanks in advance, Holger

1 0

20.05 Release Dates
by Renvoize, Martin 20 Apr '20

20 Apr '20

Hi Everyone, Time is marching on and I felt it pertinent to set the structure for end of the 20.05 cycle. I've now added my intended date to the community calendar, 1st May - Feature Freeze 8th May - String Freeze 22nd May - Release Thanks to everyone for their diligent efforts this release, it's shaping up to be a real bumper edition with some great new features and lots of bugfixes and enhancements. So, what now? We need all the help we can get to bring the manual up to date, improve the release notes and spot and fix any last bugs. Looking ahead, it's a great time to add you names to the release team list for the next cycle. Stay safe, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager Community Release Manager (19.11, 20.05) *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

1 0

New Koha Libraries for April 2020 Koha Newsletter
by B2H2 SOLUTIONS 17 Apr '20

17 Apr '20

*1. Central Library, Assam Science and Technology University, Guwahati: Assam * OPAC Link: http://astu-opac.koha.co.in/ Implemented and Maintained by B2H2 Solutions India (Pvt) Ltd. *About the Company:* B2H2 Solutions tends to be the first conveyor of Customized Open ILMS Koha in North East India. We are catering to different regions across India. Our rich expertise in managing clients across different domains, we are in the continuous process of innovating our offerings and Koha Integrated Library Management Software support for every library. *2. Central Library, Nandalal Borgohain City College, Dibrugarh: Assam* OPAC Link: http://nlbcitycollege-opac.b2h2.co.in/ Implemented and Maintained by B2H2 Solutions India (Pvt) Ltd. *About the Company:* B2H2 Solutions tends to be the first conveyor of Customized Open ILMS Koha in North East India. We are catering to different regions across India. Our rich expertise in managing clients across different domains, we are in the continuous process of innovating our offerings and Koha Integrated Library Management Software support for every library. -- *With Regards * *B2H2 Solutions India Pvt. Ltd.* *ISO 9001:2015 Certified * *Company* *Office: Morigaon(Assam), Pin-782105* *E-mail: info(a)b2h2.co.in <info(a)b2h2.co.in> * * support(a)b2h2.co.in <support(a)b2h2.co.in> * *Phone No: +91-7002708080 * * +91-9365122854 * *Website: http://b2h2.in <http://b2h2.co.in>* [image: http://jbcollege-opac.kohacloud.in] <http://jbcollege-opac.kohacloud.in/> [image: Image result for dspace] *Disclaimer : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.*

1 0

Re: [Koha] Is Koha plugin system safe?
by dcook＠prosentient.com.au 17 Apr '20

17 Apr '20

Hi Michal, I would say that the plugin system (like many plugin systems) is risky. As Jonathan indicates, plugins are not reviewed by the Koha Community, so we can make no guarantees regarding safety/security of individual plugins. Since the plugins are third-party code, they could contain anything. That said, I doubt that you'd find any/many malicious Koha plugins in the wild. You're more likely to find Koha plugins that just have accidental security vulnerabilities. For instance, I have found some that have SQL injection vulnerabilities, which I wouldn't recommend using (although I say that personally and not as a member of the Koha Community - I'm not reviewing any plugins at a community level). In terms of safety, you're *probably* more likely to find accidental problems rather than malicious ones, although practically speaking you could encounter either. There is a fledgling conversation about adding signature (ie author verification) for plugins (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24632) With this verification, you could set up Koha to only use plugins from a trusted provider (like Prosentient Systems, PTFS Europe, ByWater Solutions, BibLibre, EBSCO, etc.) . That wouldn't keep you safe from accidental security vulnerabilities, but it would keep you safe from malicious plugins. The trade-off with plugins is that you get new functionality quicker but it's not as rigorously reviewed as the Koha codebase. 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, 16 Apr 2020 03:28:34 -0700 (MST) From: Michał Dudzik <dudzikmichal(a)wp.pl> To: koha(a)lists.katipo.co.nz Subject: [Koha] Is Koha plugin system safe? Message-ID: <1587032914820-0.post(a)n5.nabble.com> Content-Type: text/plain; charset=us-ascii The koha plug-in system enables easy system expansion with an additional non-standard function. I have received several queries from librarians about the security of the plug-in system. Personally, I have not observed any problems, so I would like to ask if using the plug-in system is safe? Regards, Michal -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html ------------------------------ Message: 2 Date: Thu, 16 Apr 2020 12:54:23 +0200 From: Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> To: Michał Dudzik <dudzikmichal(a)wp.pl> Cc: koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Is Koha plugin system safe? Message-ID: <CAJzKNY6-UxzgUsRHuizsNS5ir9HoqE7couyWh50P+gKUKfNuMA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi Michal, It depends on the plugin :) A plugin can do almost everything it wants, so you should only install plugins you really trust. And you should give the permissions to manage them to librarians you really trust as well. I should add that plugins are almost never reviewed (by the QA team for instance), so they could potentially contain security issues. Regards, Jonathan Le jeu. 16 avr. 2020 à 12:28, Michał Dudzik <dudzikmichal(a)wp.pl> a écrit : > > The koha plug-in system enables easy system expansion with an > additional non-standard function. > I have received several queries from librarians about the security of > the plug-in system. > Personally, I have not observed any problems, so I would like to ask > if using the plug-in system is safe? > > Regards, > Michal >

1 0

Re: [Koha] RES: To batch change the returns / check-in
by Alex Buckley 16 Apr '20

16 Apr '20

Great thank you for letting me know Jose! Glad it was helpful. Best wishes, Alex On 17/04/20 6:26 am, Jose Ricardo Quaglio wrote: > > Hi Alex, > > > > thank you for your return, > > > > The proposal is, to determine a date for each day, after 03/17/2020. > > > > As the commands are sent to the Informatica Department, I need to > describe which of the bases will be modified, in this case, koha_biblio. > > > > To avoid unnecessary reports, I deactivated on 3/16, all instances of > Koha. > > > > Thanks again for all the information, > > > > Thank you, > > > > > > Jose Ricardo Quaglio > > > > Informatização de Bibliotecas - SC.211.3 > > > > Secretaria de Cultura > > > > Município de São Bernardo do Campo > > > > Tel.: +55 11 2630.9394 > > > > > > *De:*Alex Buckley [mailto:alexbuckley@catalyst.net.nz] > *Enviada em:* quarta-feira, 15 de abril de 2020 19:39 > *Para:* koha(a)lists.katipo.co.nz; jose.quaglio(a)saobernardo.sp.gov.br > *Assunto:* Re: To batch change the returns / check-in > > > > Hi Jose, > > Yes you're right at present in all versions of Koha 18.11 currently > available the only way to bulk extend due dates of existing issues is > in the database. > > A couple of suggestions I have for your query are: > > * Currently your query only changes the date_due of issues due on > one day 17 March 2020. If you're goal is to extend all issues that > have been due on 17 March till today's date (i.e. issues due on 17 > March, 18 March, 19 March and so on) then what you could do > instead is: > > UPDATE issues SET date_due="2020-04-29 23:59:00", > lastreneweddate="2020-04-15 15:01:00" WHERE date_due > '2020-03-17'; > > This will extend the due date to 29 April 2020 for any item that has > been due between 17 March and today. > > * Also you will not need to specify the database name koha_biblio > because to get into the Koha database shell you'll be specifying > the database name, like so: > > /sudo koha-mysql koha_biblio/ > > > > *How this would affect anything else:* > > Any overdue issues due before 17 March will *not* be extended with the > above amended query. Therefore you should consider doing the following: > > * * Stop overdue notices being generated* > > You can do this one of two ways: > > - If you want all notices (overdue, advance, hold and password reset > notices) to stop being sent during the lockdown you can run: > > sudo koha-email-disable <instancename> > > This stops notices being sent but they are still generated. Therefore > when the lockdown is over you will need to: > > - Delete notices in the message_queue database table which have a > time_queued value of during the lockdown, otherwise all overdue > notices generated during the lockdown will be sent > > - Re-enable email > > sudo koha-email-enable <instancename> > > > > OR > > - Comment out overdue_notices.pl in the /etc/cron.daily/koha-common file > > This will stop overdue notices being generated at all during the > lockdown. > > > > * *Stop overdue fines accruing during the lockdown for those > overdues due before 17 March 2020* > > - Set finesMode system preference to /'Calculate (but only for > mailing to the administrator)'/ > > > > * *Stop patrons being charged the replacement cost of items//(only > applies if you are using the > DefaultLongOverdueChargeValue system preference)* > > Remove the value from the DefaultLongOverdueChargeValue system preference. > > > > Just to let you know soon (probably around 24th April ) Koha 18.11.16 > will be available to upgrade to and that has the wonderful feature of > allowing you to bulk extend due dates in the Koha staff client as this > excellent blog post by my colleague Aleisha Amohia outlines: > https://www.catalyst.net.nz/blog/koha-let-people-read-longer > > Please let me know if you have any questions at all! > > Many thanks, > > Alex > > -- > Alex Buckley > Koha Developer > > Catalyst IT - Expert Open Source Solutions > DDI: +64 4 803 2378 | Mob: +64 22 429 6157 | www.catalyst.net.nz <http://www.catalyst.net.nz> > > > CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267. > > -- Alex Buckley Koha Developer Catalyst IT - Expert Open Source Solutions DDI: +64 4 803 2378 | Mob: +64 22 429 6157 | www.catalyst.net.nz CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

1 0

Re: [Koha] To batch change the returns / check-in
by Alex Buckley 16 Apr '20

16 Apr '20

Hi Jose, Yes you're right at present in all versions of Koha 18.11 currently available the only way to bulk extend due dates of existing issues is in the database. A couple of suggestions I have for your query are: * Currently your query only changes the date_due of issues due on one day 17 March 2020. If you're goal is to extend all issues that have been due on 17 March till today's date (i.e. issues due on 17 March, 18 March, 19 March and so on) then what you could do instead is: UPDATE issues SET date_due="2020-04-29 23:59:00", lastreneweddate="2020-04-15 15:01:00" WHERE date_due > '2020-03-17'; This will extend the due date to 29 April 2020 for any item that has been due between 17 March and today. * Also you will not need to specify the database name koha_biblio because to get into the Koha database shell you'll be specifying the database name, like so: /sudo koha-mysql koha_biblio/ *How this would affect anything else:* Any overdue issues due before 17 March will *not* be extended with the above amended query. Therefore you should consider doing the following: * * Stop overdue notices being generated* You can do this one of two ways: - If you want all notices (overdue, advance, hold and password reset notices) to stop being sent during the lockdown you can run: sudo koha-email-disable <instancename> This stops notices being sent but they are still generated. Therefore when the lockdown is over you will need to: - Delete notices in the message_queue database table which have a time_queued value of during the lockdown, otherwise all overdue notices generated during the lockdown will be sent - Re-enable email sudo koha-email-enable <instancename> OR - Comment out overdue_notices.pl in the /etc/cron.daily/koha-common file This will stop overdue notices being generated at all during the lockdown. * *Stop overdue fines accruing during the lockdown for those overdues due before 17 March 2020* - Set finesMode system preference to /'Calculate (but only for mailing to the administrator)'/ / / * *Stop patrons being charged the replacement cost of items*/**/*(only applies if you are using the ** **DefaultLongOverdueChargeValue system preference)*/ / Remove the value from the DefaultLongOverdueChargeValue system preference. Just to let you know soon (probably around 24th April ) Koha 18.11.16 will be available to upgrade to and that has the wonderful feature of allowing you to bulk extend due dates in the Koha staff client as this excellent blog post by my colleague Aleisha Amohia outlines: https://www.catalyst.net.nz/blog/koha-let-people-read-longer Please let me know if you have any questions at all! Many thanks, Alex -- Alex Buckley Koha Developer Catalyst IT - Expert Open Source Solutions DDI: +64 4 803 2378 | Mob: +64 22 429 6157 | www.catalyst.net.nz CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

3 4

Re: [Koha] To batch change the returns / check-in
by Michael Kuhn 16 Apr '20

16 Apr '20

Hi > Due to COVID-19 our Libraries are closed. > > I am studying a way to batch change the returns / check-in in this period. Maybe the new tool to bulk edit due dates will fit your needs. See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24846 This tool is already part of Koha 19.11.04 and 19.05.09. It also has been backported for Koha 18.11.16 which will probably be released at the end of April 2020. The following video shows how to use the tool: https://www.youtube.com/watch?v=uiS1oS2uHmE 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