February 2024 - Koha-bugs - lists.koha-community.org

[Bug 34893] ILS-DI can return the wrong patron for AuthenticatePatron
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34893 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |36161 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36161 [Bug 36161] ISLDI AuthenticatePatron broken when LDAP enabled and auth falls back to internal connection -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23532] New: AutoCreateAuthorities create authority only headings
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23532 Bug ID: 23532 Summary: AutoCreateAuthorities create authority only headings Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: gveranis(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The problem: We have enable AutoCreateAuthorities and also enable BiblioAddsAuthorities and when we insert values for tag 650 , we get authorities only with 150$a filled and not other subfields. I found that on C4/Biblio.pm lines 549 - 555 map { $authfield->add_subfields( $_->[0] => $_->[1] ) if ( $_->[0] =~ /[A-z]/ && $_->[0] ne "a" && C4::Heading::valid_bib_heading_subfield( $authority_type->auth_tag_to_report, $_->[0] ) ); } $field->subfields(); Koha try to copy subfields to the new authority record. BUT the condition C4::Heading::valid_bib_heading_subfield( $authority_type->auth_tag_to_report, $_->[0]) return false. Because the $authority_type->auth_tag_to_report has value of 150 and not 650 as file C4/Heading/MARC21.pm declared. if we set on file C4/Heading/MARC21.pm also the value '150' => { auth_type => 'TOPIC_TERM', subfields => 'abvxyz', subject => 1 }, (valid based on https://github.com/Koha-Community/Koha/blob/master/installer/data/mysql/en/…) then it works , but I am not sure if it is valid to set there new fields. or better solution could be $authority_type->auth_tag_to_report take right value in condition. Could anyone propose the best solution ? Thanks, George Veranis -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24421] New: Generated authorities are missing subfields
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24421 Bug ID: 24421 Summary: Generated authorities are missing subfields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In bug 21826 the intent was to only add allowed subfields to generated authorities, however, the code uses the authority tag instead of the biblio tag - there is no mapping for these, so correct subfields are ignored To recreate: 1 - Enable the sysprefs AutoCreateAuthorities BiblioAddsAuthorities CatalogModuleRelink 2 - Open a record with a subject heading with a subdivision and add a new subfield, or add a new unauthroized heading to a record and save it e.g. 650$aChess$xOpenings$vFiction. 3 - Save the record, note the created authority and that field is linked 4 - Save the record again and note the authority number changes 5 - Find and view the authority linked to the record 6 - The record is for 'Chess', not Chess openings' 7 - Search authorities for 'Chess' - note duplicated records -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 25261] New: Multiple parts handling - confirmation alert
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25261 Bug ID: 25261 Summary: Multiple parts handling - confirmation alert Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.field(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha already has a field in the item record to identify multi-part material. Materials specified (bound volume or other part) or 952$3. When there is a value in this field (e.g. 2) Koha will prompt you at checkout and checkin with a message dialog which says: Note about the accompanying materials: 2 This is helpful but can be missed by library staff. This enhancement takes this one step further to introduce a confirmation box to acknowledge that the parts have been checked on issue and return. This prevents staff from proceeding before checking the item in their hands. The reason for this is to prevent arguments with library patrons that they did not originally take all the parts or that they did not return all the parts. For example, a CD with an accompanying booklet or a string quartet with 4 parts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 239

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 --- Comment #105 from Thibaud Guillot <thibaud.guillot(a)biblibre.com> --- (In reply to Lisette Scheer from comment #103) > Template process failed: undef error - The method > Koha::CirculationRule->has_priority is not covered by tests! > > Trace begun at /kohadevbox/koha/Koha/Object.pm line 964 > > Once I try selecting the priority box and saving, my smart-rules.pl > completely breaks. Hi Lisette, Thanks for testing and feedback :) So did you forget to update your schema ? I apply another time and its work great for me. I rebased on master and I took the opportunity to indent some lines. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #159712|0 |1 is obsolete| | --- Comment #104 from Thibaud Guillot <thibaud.guillot(a)biblibre.com> --- Created attachment 162367 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=162367&action=e… Bug 8137: Add 'global' has_priority rules for checkouts I tried to review the desired behavior through this bug. The goal would be to be able to have a general 'override' rule. Currently, if you set a max_checkouts_allowed of 5 (regardless of itemtype) in one library, for example, and do the same in another, it adds up to 10. By giving checkout rules priority, you "overwrite" other local rules per branchcode. Test plan: 1) Set for library "A" a max_checkouts_allowed to 3 for any type of user and item type. 2) On main rules set the same rule to 2 3) Do a few checkouts with a user belonging to library A, normally you'll be able to do 3. 4) Apply this patch and run updatedatabase.pl and also rebuild your schema by updating dbix class files 5) See now the Has priority checkboxes on "Default checkout, hold and return policy" and "Default checkout, hold policy by patron category" 6) You can set here you new rule for "Total current checkouts allowed" to 2 7) Repeat step 3 and normally you won't be able to make the third Sponsored-by: BibLibre -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33664] New: Should we allow cancelling orders while the basket is closed?
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33664 Bug ID: 33664 Summary: Should we allow cancelling orders while the basket is closed? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com, michaela.sieber(a)kit.edu This is a workflow question: At the moment cancelling an order line from the basket summary page is only possible, while the basket is open. For standing orders this means it's always possible, while it's not for other types of orders. There is now 2 ways to cancel the order: Option A: * Reopen the basket * Cancel the order * Close the basket + Less clicks than option B - All unreceived order lines will switch status unnecessarily (ordered - new - ordered) - The basket close date will reset to today's date Option B: * Create a new shipment * 'Fake' an invoice, for example it could be named: Cancellations * Use the cancelling options from the list of pending orders + Close date remains the same + Only the cancelled order line will change status - More clicks and not really convenient Now the question: Is there a strict reason why we should not permit cancelling from a closed order? The closed order lines will still show in the second table below. We could also add a hint on the cancellation date. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 30232] New: Acquisition logged in user performance
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30232 Bug ID: 30232 Summary: Acquisition logged in user performance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Some acquisition methods can take borrowernumber or a Koha::Patron->unblessed. When called with logged in user, sometimes in a loop, performance will be better if fetching Koha::Patron of logged in user only once. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 7923] Performance omnibus
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7923 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |35921 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35921 [Bug 35921] Improve perfs of acqui-home.pl when there are many budgets -- You are receiving this mail because: You are watching all bug changes.

1 0