April 2020 - Koha-bugs - lists.koha-community.org

[Bug 21551] New: Automatically update guarantee when updating guarantor
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '25

26 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21551 Bug ID: 21551 Summary: Automatically update guarantee when updating guarantor Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great if an update to a guarantor's contact information also updated all guarantees. It appears there used to be code for this, but it didn't work and was removed. See bug 15653. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15653 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 23046] New: Add tax handling to accounts
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23046 Bug ID: 23046 Summary: Add tax handling to accounts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We should have the ability to assign tax rates to the various charges a patron can incur. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 24599] New: Add endpoints for bulk processing of holds
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24599 Bug ID: 24599 Summary: Add endpoints for bulk processing of holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com As highlighted by bug 24410, we need a way to handle bulk submission of holds via the API. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 23669] New: Verify if checkouts or reserves requests from ILS-DI periods overlap with existing reserves
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23669 Bug ID: 23669 Summary: Verify if checkouts or reserves requests from ILS-DI periods overlap with existing reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: julian.maurice(a)biblibre.com Depends on: 15261, 23531 Same as BZ15261 but for WebServices Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 [Bug 15261] Verify if checkouts or reserves requests periods overlap with existing reserves https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23531 [Bug 23531] ILS-DI doesn't implement needed_before_date and pickup_expiry_date parameters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 16791] New: Explanation of callnumber.pl plugin
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16791 Bug ID: 16791 Summary: Explanation of callnumber.pl plugin Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: eb(a)efdss.org QA Contact: testopia(a)bugs.koha-community.org Perhaps a brief explanation of what callnumber.pl is meant to do would be a useful addition to the manual. I am not certain what its function is, though I discovered that it doesn’t do what I was hoping it would. See bug 13615 for a long winded query. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 21250] New: Auto-self-checkout not fully compatible with two-branch library setup
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21250 Bug ID: 21250 Summary: Auto-self-checkout not fully compatible with two-branch library setup Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org We use a two-branch library setup, both with auto-self-checkout enabled, so patrons log in with their cardnumber via the pre-defined staff user account (see below). The problem is that since the internal self-checkout user also has to be assigned to exactly one branch, that branch will be used as "current location" when a patron checks out a book. So, it's the self-service account's branch that's used instead of the patron's/borrower's branch. >From looking at the code it seems that C4::Circulation->AddIssue() is using "C4::Context->userenv->{branch}" where "$borrower->{'branch'}" should probably be used instead, since the current user's branch isn't relevant (even wrong) in the auto-self-checkout context. FYI, we use the following config (if relevant at all): - Koha 18.05.01-2 - AutoSelfCheckAllowed: Allow (AutoSelfCheckID/AutoSelfCheckPass) - CircControl: the library the item is from - HomeOrHoldingBranch: the library the item is from Thank you. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 25165] New: Explain all the cataloging plugins
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25165 Bug ID: 25165 Summary: Explain all the cataloging plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The only one that I could find in the manual is the cn_browser plugin, the upload plugin and a vague mention of unimarc 1XX plugins. https://koha-community.org/manual/19.11/en/html/administration.html#edit-ex… (towards the end of the section) As of writing this (19.12.00.071) this is the list of plugins: - barcode - barcode_manual - callnumber-KU - callnumber - cn_browser - dateaccessioned - macles - marc21_field_005 - marc21_field_006 - marc21_field_007 - marc21_field_008 - marc21_field_008_authorities - marc21_field_008_classifications - marc21_field_245h - marc21_leader - marc21_leader_authorities - marc21_linking_section - marc21_orgcode - normarc_field_007 - normarc_field_008 - normarc_leader - stocknumber - stocknumberAV - stocknumberam123 - unimarc_field_010 - unimarc_field_100 - unimarc_field_100_authorities - unimarc_field_105 - unimarc_field_106 - unimarc_field_110 - unimarc_field_115a - unimarc_field_115b - unimarc_field_116 - unimarc_field_117 - unimarc_field_120 - unimarc_field_121a - unimarc_field_121b - unimarc_field_122 - unimarc_field_123a - unimarc_field_123d - unimarc_field_123e - unimarc_field_123f - unimarc_field_123g - unimarc_field_123i - unimarc_field_123j - unimarc_field_124 - unimarc_field_124a - unimarc_field_124b - unimarc_field_124c - unimarc_field_124d - unimarc_field_124e - unimarc_field_124f - unimarc_field_124g - unimarc_field_125 - unimarc_field_125a - unimarc_field_125b - unimarc_field_126 - unimarc_field_126a - unimarc_field_126b - unimarc_field_127 - unimarc_field_128a - unimarc_field_128b - unimarc_field_128c - unimarc_field_130 - unimarc_field_135a - unimarc_field_141 - unimarc_field_210c - unimarc_field_210c_bis - unimarc_field_225a - unimarc_field_225a_bis - unimarc_field_4XX - unimarc_field_686a - unimarc_field_700-4 - unimarc_leader - upload -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 18365] New: Appendix D. Notice & Slips Guides is out of date
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18365 Bug ID: 18365 Summary: Appendix D. Notice & Slips Guides is out of date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I've just brought https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips#Notice_S… up to date with master. The 'Can be branch specific' column is no longer needed; as far as I know, any notice may be branch specific at this point. The only gap on the wiki are the letter codes for notices generated via SendAlerts -- If someone can help me out there, that would be great. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 18962] New: Including valid system requirements in Koha manual
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18962 Bug ID: 18962 Summary: Including valid system requirements in Koha manual Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mik(a)adminkuhn.ch QA Contact: testopia(a)bugs.koha-community.org According to https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Introduction Ubuntu 14.04 is no longer supported - but the information given on the page https://koha-community.org/download-koha/ still says that Koha is "Actively supported for packages: Debian 7 (Wheezy), Debian 8 (Jessie), Ubuntu 14.04 (Trusty Tahr)". It would probably be a good idea to have correct and complete information about the system requirements of Koha at the very beginning of the manual for every Koha version as it is good practice for almost every other software. * the manual of every Koha version * the release notes of every Koha version (or a link to the respective manual) * https://koha-community.org/download-koha/ (or a link to the respective manual) The systems requirements can be changing with every new version, of course, thus it is not enough to say in the manual: "Full system recommendations can be found on the official Koha wiki along with the developer documentation: http://wiki.koha-community.org". I suggest the manual of every Koha version should include a section with the exact requirements for the respective Koha version, e. g. * supported Linux distributions * supported version of Apache HTTP Server * supported version of MySQL * supported version of Perl This would probably also be helpful for all the guys that are trying to install Koha on unsupported Linux distributions like CentOS, Redhat etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 24439] New: Bulkmarcimport.pl Update documentation for -match option
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24439 Bug ID: 24439 Summary: Bulkmarcimport.pl Update documentation for -match option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org The -match option for bulkmarcimport says: -match=<FIELD> FIELD matchindex,fieldtomatch matchpoint to use to deduplicate fieldtomatch can be either 001 to 999 or field and list of subfields as such 100abcde This seems to indicate that you put a number in the FIELD parameter, but really you are putting the "Koha Search Index" text a comma and then the MARC field: -match=<KohaIndex,FIELD> or -match=Control-number,001 I was only able to figure this out because someone else was confused: http://koha.1045719.n5.nabble.com/bulkmarcimport-pl-AND-match-fails-when-tr… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2