- Koha - lists.katipo.co.nz

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

Log access from intranet
by Alvaro Cornejo 07 Apr '20

07 Apr '20

Hi, I´m trying to access /tools/AccessFiles but I get the error message: Error: Files could not be found because the "access_dir" option was not set in "koha-conf.xml". Contact your system administrator to add this option. I looked to koha-conf file in /etc/koha/blibioteca/ but file does not have any information about where to place that info. Any idea of how to configure it? 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

Request to be added as Koha Support Provider
by ZINET Software Solutions 07 Apr '20

07 Apr '20

Dear Sir /Ma'am, Greetings of the day. ZINET Software Solutions was established in 2015 and have been providing IT and IT Enabled services to various categories. We would like to introduce ourselves as one of the Koha support providers in India, based having our registered office at Kerala. We are providing support to various parts of India such as Kerala, Tamil Nadu, Maharashtra, Nagaland, Karnataka etc. Currently we have been providing support to more than 55 clients. We request you to kindly add our company details as a paid support provider of Koha ILS. Our details are as follows: Company Name: ZINET SOFTWARE SOLUTIONS Contact Person: JOVIN DEGLUS Contact email: info(a)zinet.in Website: http://www.zinet.in Telephone: +91 7736 980 930 Koha Link: http://www.zinet.in/Solutions/Koha Looking forward to hear from you soon. Thanks n Regards ZINET SOFTWARE SOLUTIONS Address :2nd Floor, MAMS Commercial Complex ESI Jn, Kottiyam Kollam, Kerala, INDIA - 691571 Ph : +91 474 253 4911 +91 7736 980 930 Web : http://www.zinet.in/ Email : mailto:info@zinet.in

2 1

'Basic SQL for Koha Users' recording, slides, chat logs
by Jason Robb 06 Apr '20

06 Apr '20

Thanks to everyone who attended today's Basic SQL training presented by the koha-US education committee! Materials from the session are linked below. - Recording: https://youtu.be/qpPoAWZHzwY - Slides: https://drive.google.com/open?id=1SDpTD9DuL4sgxA8lMDJ3BzUGl2TTjtENq3acMUby8… - Chat logs:: https://drive.google.com/open?id=1Ux_NeHun80rX5VzTNfmo4NRUeiPJ4qA4 Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

koha-US general meeting reminder: Wednesday, April 8th, 2020
by Jason Robb 06 Apr '20

06 Apr '20

Our next koha-US general meeting is this Wednesday, April 8th. When: 8:30 AM PT / 9:30 MT / 10:30 CT / 11:30 ET (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+general+m…> ) Where: https://zoom.us/j/648572897 Agenda: https://docs.google.com/document/d/15ygCI7NnrVpY-cAFMPNISmYTJOI6M6It43_JuNo… This month we will review some of the resources recently made available, give some updates on upcoming koha-US events, and hear from various committees. As always, we'll have plenty of time for open discussion of bugs and issues, including strategies for handling current events. If you have specific topics for the agenda, please send them to secretary(a)koha-us.org Meetings are held via Zoom video conferencing. A microphone and webcam are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops, and Android and iOS on mobile devices. For help getting started, visit: https://support.zoom.us/hc/en-us/categories/200101697 These meetings are always free and open to any and all. Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

Elasticsearch: More questions
by Tom Hanstra 06 Apr '20

06 Apr '20

Elasticsearch users: A few additional questions: 1) The Koha install/configuration looks for: Search/Elasticsearch/Client/5_0/Direct.pm But CPAN installed: ./local/share/perl5/Search/Elasticsearch/Client/6_0/Direct.pm on my install. Consequently, when I try to index, I get the error message: Can't locate Search/Elasticsearch/Client/5_0/Direct.pm Should I update the module which is complaining (Koha/SearchEngine/Elasticsearch.pm) or is there some other change that should be made to address this? 2) Assuming my change from 5_0 -> 6_0 is ok, I'm still getting the error: Software error: Can't locate object method "index_name" via package "Catmandu::Store::ElasticSearch" at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 414. Could it be that Koha cannot find the Catmandu::Store::ElasticSearch files? Is there someplace where the PERL5LIB path is needed that might be missing? The files are there, but it certainly does not seem to be able to use that to look up the information it needs. 3) After performing the indexing, assuming it is actually valid, the index still shows as "yellow": curl http://localhost:9200/_cat/indices yellow open koha_london_test_20_biblios VRgVHrtDQ0S1oBGFJRVjjA 5 1 12287 0 138.9mb 138.9mb yellow open koha_london_test_20_authorities AQOw74fbQYqnm63KuZQ0zQ 5 1 6163 0 8mb 8mb Should those be green after indexing is completed? Is there something that moved it on to green? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra(a)nd.edu

1 0

Update after importing MARCXML
by Heinz-Jürgen Oertel 05 Apr '20

05 Apr '20

Hi, after importing a news set of data using "Stage MARC records for import", "Manage staged MARC records" tells me 3251 new records. And after that, searching for an Author should I see immediately more results? Can I see somewhere, which records are new? -- Heinz

2 2

Elasticsearch again
by Tom Hanstra 02 Apr '20

02 Apr '20

Earlier testing of Koha 19.11.03 with Elasticsearch 7 and 6 both gave errors. There was some suspicion that perhaps Elasticsearch had to be rolled back to V5. So, I did that today, as well as upgrading Koha to 19.11.04. And I am getting a new error. Basically, now, it looks like there might be a configuration error somewhere? Here is my current error when trying to index: PERL5LIB=/usr/share/koha/lib:/usr/local/lib:/usr/local/share/perl5 ./bin/search_tools/rebuild_elasticsearch.pl -d -v -p 4 [7019] Checking state of biblios index [7019] Dropping and recreating biblios index [Request] ** [http://localhost:9200]-[400] [illegal_argument_exception] Custom Analyzer [analyzer_phrase] failed to find filter under name [icu_folding], called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Indexer.pm line 349. With vars: {'body' => {'status' => 400,'error' => {'root_cause' => [{'reason' => 'Custom Analyzer [analyzer_phrase] failed to find filter under name [icu_folding]','type' => 'illegal_argument_exception'}],'reason' => 'Custom Analyzer [analyzer_phrase] failed to find filter under name [icu_folding]','type' => 'illegal_argument_exception'}},'request' => {'serialize' => 'std','path' => '/koha_london_test_20_biblios','ignore' => [],'mime_type' => 'application/json','body' => {'settings' => {'index' => {'analysis' => {'normalizer' => {'nfkc_cf_normalizer' => {'type' => 'custom','char_filter' => 'icu_normalizer'},'icu_folding_normalizer' => {'filter' => ['icu_folding'],'type' => 'custom'}},'char_filter' => {'punctuation' => {'pattern' => '([\\x00-\\x1F,\\x21-\\x2F,\\x3A-\\x40,\\x5B-\\x60,\\x7B-\\x89,\\x8B,\\x8D,\\x8F,\\x90-\\x99,\\x9B,\\x9D,\\xA0-\\xBF,\\xD7,\\xF7])','type' => 'pattern_replace','replacement' => ''}},'analyzer' => {'analyzer_stdno' => {'filter' => ['icu_folding'],'char_filter' => ['punctuation'],'tokenizer' => 'whitespace'},'analyzer_phrase' => {'filter' => ['icu_folding'],'char_filter' => ['punctuation'],'tokenizer' => 'keyword'},'analyzer_standard' => {'filter' => ['icu_folding'],'tokenizer' => 'icu_tokenizer'}}}},'index.mapping.total_fields.limit' => '10000'}},'qs' => {},'method' => 'PUT'},'status_code' => 400} FWIW, Koha knows what the indices should be but also seems to know that they do not yet exist: Nodes: localhost:9200 | Status: running | Indices: koha_london_test_20_biblios (count: -1), koha_london_test_20_authorities (count: -1) Anyone seen this type of error or have ideas on what might be going on with this particular issue? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra(a)nd.edu

2 2

Re: [Koha] [Koha-devel] On-site checkouts and circulation types proposal
by Lari Taskula 01 Apr '20

01 Apr '20

I have sent this to the general mailing list. tldr for general list readers; * we need to be able to define separate circulation rules between normal and on-site checkouts. * my proposal in this mail is to add a new circulation rule scope "circulationtype". A rule scope in Koha is currently a combination of a library, patron category and item type. * circulationtype would be either "All" (default), "Normal" or "On-site" The case is explained by our client library here https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101#c0 > Which rules are suitable for such separation? I think this would make sense to all circulation rules except hold-related rules. It would allow very flexible parametrization between normal and on-site checkouts. In order to make adaptation straight-forward, this could be blocked by Bug 15522 (the circulation rules user interface change). Once 15522 is pushed and libraries update their Koha instances, they could find this together with the new GUI. Also at this point it doesn't make much sense to develop anything new on top of the old interface. Lari Taskula CEO, Hypernova Oy +358449857337 Kauppakatu 25 C 409 80100 Joensuu, Finland On 1.4.2020 10.46, Jonathan Druart wrote: > Hi Lari, > > I think it would be interesting to get opinions from the general > mailing list. What are the different use cases? Which rules are > suitable for such separation? > Theoretically, all. But in practice? > > Your idea is good I think, and certainly a great way to answer the need. > > Few things: > You will not double the size of the table horizontally, but maybe > vertically. Instead of 1 row you will end up with 2. > To prevent it to be doubled, the "type" will need to be "normal", > "onsite", or "both" if current maxissueqty == maxonsiteissueqty > > Keep in mind the syspref ConsiderOnSiteCheckoutsAsNormalCheckouts. > > Cheers, > Jonathan > > Le mer. 1 avr. 2020 à 08:24, Lari Taskula <lari.taskula(a)hypernova.fi> a écrit : >> Hi fellow Koha devs, >> >> I'm working on Bug 24101 >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 in which >> our client wants the ability to separately define circulation rules for >> normal and on-site checkouts. They need the ability to renew on-site >> checkouts, define due date calculation parameters and additionally >> specify separate fine rules (not mentioned in bz ticket yet). >> >> I wanted to ask for your thoughts on this. >> >> Initially I was thinking of duplicating the rules of normal circulation >> the way maxissueqty and maxonsiteissueqty is currently done, but in the >> end this would lead to duplicating almost all of the circulation rules. >> That would not be very convenient and it seems like a short-sighted way >> of solving this problem because it leaves no room for possible new types >> of checkouts in the future. Who wants to see the circulation rule table >> doubling in width? Not me. >> >> Another, more elegant approach would be to define a new circulation rule >> scope "circulationtype" that defines whether a rule applies to normal or >> on-site checkout (or any other type of checkout someone may come up with >> in the future). Now that we are able to explicitly define a scope that a >> specific circulation rule follows, this would make sense. No need for >> ugly duplication and we can get rid of maxonsiteissueqty too. >> >> Anyways, before I start implementing such a change I wanted to ask for >> support from the community, or better yet even cooler ideas. Perhaps >> there is something about Koha that I have missed that could already >> solve their problem. >> >> Thanks for your time. >> >> -- >> Lari Taskula >> CEO, Hypernova Oy >> +358449857337 >> Kauppakatu 25 C 409 >> 80100 Joensuu, Finland >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/

1 0