- Koha-devel - lists.koha-community.org

Thank you for all the help
by RAGHAV ARORA 17 Jul '19

17 Jul '19

Hello everyone, I was working on a project based on koha ILS for which I got a lot of help from the mailing lists and that allowed me to finish the project properly. I am really obliged and want to thank all the members of the mailing lists for helping me out. It is really great that koha has such an active community that is willing to help beginners like me. Once again, Thank you. Regards *Raghav Arora* Sophomore, M.Sc (Hons) Chemistry BE Electrical and Electronics Engineering Contact : (+91) 9897597761 Personal Email <raghavarora999(a)yahoo.in> | University Email <f20171016(a)pilani.bits-pilani.ac.in> LinkedIn <https://www.linkedin.com/in/raghav-arora-9820a648/> | GitHub <https://github.com/RAraghavarora/> ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ *Birla Institute of Technology and Science, Pilani* Pilani campus, Rajasthan-333031

1 0

Call for News: July 2019 Newsletter
by kohanews 16 Jul '19

16 Jul '19

I'm collecting news for the July 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 ****. * News items can be of any length. * Images are fine * 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

Koha Community Project Day
by Katrin Fischer 15 Jul '19

15 Jul '19

Hi all, Do you have a Koha clean-up / dev / fun project in mind, that you never find time to work on? Koha Community Project Day is your chance to finally get around to it! We are organising a global Koha event everyone can participate in. We are looking for all kinds of small projects people want to commit to. This could be anything Koha related - working on bugs, the manual, a plugin, website content... When: Friday, 26 July 2019, whatever timezone you are in We will be collecting project ideas and commitments on the wiki: https://wiki.koha-community.org/wiki/Koha_Community_Project_Day_26_July_2019 If you are not comfortable editing the wiki, please email me your changes and I will take care of it! Looking forward to all the ideas you come up with! Katrin

1 0

String Freeze (Maintenance Branches)
by Fridolin SOMERS 15 Jul '19

15 Jul '19

Hi All, Today we start string freeze for the maintenance branches. With the series of maintenance releases starting on tuesday the 23rd. Go forth and update your translations : https://translate.koha-community.org/projects/19.05/ https://translate.koha-community.org/projects/18.11/ https://translate.koha-community.org/projects/18.05/ Best regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0

Account details email after verification
by akafortes 13 Jul '19

13 Jul '19

Hello everyone! Is it possible to send the Account Details Notice to a new Patron, after he has used the email verification? In hopes to make the use case clear: 1. New member registers using "Self Registration" 2. The verification email is sent 3. Patron follows the activation link and verifies his new account 4. *This is what I want to do now* *Email is sent with the account details of the Patron* Is there a way to make this happen? Thank you. -- Sent from: http://koha.1045719.n5.nabble.com/Koha-devel-f3063671.html

2 1

Virtualbox 6.0 compatible with Hyper-V
by dcook＠prosentient.com.au 12 Jul '19

12 Jul '19

Hi all Windows users, Just mentioning that Virtualbox 6.0 apparently can use Hyper-V as a backend, so if you're frustrated because Docker Desktop uses Hyper-V, which prevents you from using VMware or Virtualbox, your prayers have now seemingly been answered. I haven't tried it out, but that's what I'm told: https://www.virtualbox.org/wiki/Changelog-6.0 I really like using Docker Desktop for all my development now, but sometimes it might be necessary to use Virtualbox, so nice to have this as an option. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 1

Re: [Koha-devel] Library limits
by BOUIS Sonia 11 Jul '19

11 Jul '19

Hello Tomas, I don't have an opinion (I don't really understand the question in fact...) but, I'm wondering if there's any link with the question I have sent few month ago : http://koha.1045719.n5.nabble.com/Branches-limitations-for-locations-td6006… Cheers, Sonia Message: 1 Date: Fri, 5 Jul 2019 16:46:29 -0300 From: Tomas Cohen Arazi <tomascohen(a)gmail.com> To: koha-devel <koha-devel(a)lists.koha-community.org> Subject: [Koha-devel] Library limits Message-ID: <CABZfb=WHGQoOh=xaxmJfE04UNZ_G3DpV=425EoLu9ROvv2pLqA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I have filed this the following bugs now: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23272 <- this one has patches https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23271 The idea is that we have Koha::Object::Limit::Library, currently only used in Koha::Patron::Attribute::Type, and we should use it as a reference. But I have a question: I noticed in Koha::AuthorisedValues we overload ->search by allowing it to have a (surprise?) parameter: branchcode. I ->use the word 'surprise' because we've been leaning to the 'least surprise' principle and allowing to pass an attribute name that isn't in the model, seems like a surprise we would like to avoid. I would like to propose we create an analogous Koha::Objects::Limit::Library class (notice the plural), implementing a specialized search method, with a name that clearly states the goal as discussed previously in the context of a bug I now don't remember :-D In the lines of sub search_with_branch_limits { my ( $self, $params, $attributes, $library_id ) = @_; my $or = $library_id ? { '-or' => [ 'authorised_values_branches.branchcode' => undef, 'authorised_values_branches.branchcode' => $library_id, ] } : {}; my $join = $library_id ? { join => 'authorised_values_branches' } : {}; $attributes //= {}; $attributes = { %$attributes, %$join }; return $self->SUPER::search( { %$params, %$or, }, $attributes ); } Note: I'd replace the table and column names for the configured ones. Opinions? -- Tom?s Cohen Arazi Theke Solutions (http://theke.io) ? +54 9351 3513384 GPG: B2F3C15F

1 0

Problems searching callnumbers with Koha and ICU
by Mason James 10 Jul '19

10 Jul '19

Hi Folks Has anyone hit a problem searching callnumbers with Koha and ICU - specifically callnumbers with SPACE ' ' characters? An example problematic callnumber is 'PZ 7 .W663 1984' Or, has anyone had *success* searching callnumbers with ICU? :) Either way, I'd be curious to hear from you I tested on Koha 18.05.12 and Debian 9.8 Cheers, Mason

2 2

Debian Buster problems
by Mark Tompsett 09 Jul '19

09 Jul '19

The following error occurred while importing the database structure: [Mon Jul 8 19:17:21 2019] install.pl: DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails at /usr/share/perl5/DBIx/RunSQL.pm line 278, <$args{...}> line 1. Please contact your system administrator -- After fighting past the Mojolicious::Plugins::OpenAPI issue and the JSON::Validator sub-issue, I thought I had gotten to the install part, and this came up. GPML, Mark Tompsett

1 0

Library limits
by Tomas Cohen Arazi 05 Jul '19

05 Jul '19

Hi, I have filed this the following bugs now: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23272 <- this one has patches https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23271 The idea is that we have Koha::Object::Limit::Library, currently only used in Koha::Patron::Attribute::Type, and we should use it as a reference. But I have a question: I noticed in Koha::AuthorisedValues we overload ->search by allowing it to have a (surprise?) parameter: branchcode. I use the word 'surprise' because we've been leaning to the 'least surprise' principle and allowing to pass an attribute name that isn't in the model, seems like a surprise we would like to avoid. I would like to propose we create an analogous Koha::Objects::Limit::Library class (notice the plural), implementing a specialized search method, with a name that clearly states the goal as discussed previously in the context of a bug I now don't remember :-D In the lines of sub search_with_branch_limits { my ( $self, $params, $attributes, $library_id ) = @_; my $or = $library_id ? { '-or' => [ 'authorised_values_branches.branchcode' => undef, 'authorised_values_branches.branchcode' => $library_id, ] } : {}; my $join = $library_id ? { join => 'authorised_values_branches' } : {}; $attributes //= {}; $attributes = { %$attributes, %$join }; return $self->SUPER::search( { %$params, %$or, }, $attributes ); } Note: I'd replace the table and column names for the configured ones. Opinions? -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0