November 2022 - Koha-bugs - lists.koha-community.org

[Bug 31937] New: cleanup_database locked a large number of patrons
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31937 Bug ID: 31937 Summary: cleanup_database locked a large number of patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The first run of cleanupdatabase after the upgrade to 21.11 did indeed cleanup a lot ;) It seems that this statement my $expired_patrons = Koha::Patrons->filter_by_expiration_date({ days => $lock_days })->search({ login_attempts => { '!=' => -1 } }); works different than before. It must have selected patrons that had an empty dateexpiry in 20.11 ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 32089] New: build_holds_queue should optimize transfers to the hold pickup location rather than the patron home library
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32089 Bug ID: 32089 Summary: build_holds_queue should optimize transfers to the hold pickup location rather than the patron home library Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 31557 The logic used in build_holds_queue is all based on the item location and the patron's home branch, on the assumption that the patron will be picking the hold up at their home branch. That's going to be correct often, but not always. We should instead look at the hold pickup location, reserves.branchcode. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31557 [Bug 31557] Add ability for holds queue builder to prioritize either matching a patron's home library to the item's home or holding library -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27035] New: Shows the number of results in a facet
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27035 Bug ID: 27035 Summary: Shows the number of results in a facet Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: ivan.dziuba(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org After searching, the number of results for facets is not displayed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 30243] New: When OPACSuggestionMandatoryFields includes branchcode the dropdown should default to an empty value
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30243 Bug ID: 30243 Summary: When OPACSuggestionMandatoryFields includes branchcode the dropdown should default to an empty value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When OPACSuggestionMandatoryFields includes branchcode the dropdown should default to an empty value which will force the user to make a choice regarding branchcode. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 32249] New: When OPACSuggestionMandatoryFields includes branchcode the dropdown defaults to patron home branch
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32249 Bug ID: 32249 Summary: When OPACSuggestionMandatoryFields includes branchcode the dropdown defaults to patron home branch Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 144003 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144003&action=e… OPACSuggestionMandatoryFields defaults to patron home branch When testing for documentation of Bug 30243 in 22.05, the branchcode dropdown defaults to patron home branch instead of an empty value. OPACSuggestionMandatoryFields includes branchcode OPACSuggestionUnwantedFields does NOT include branchcode Save all OPAC preferences On the OPAC, select "New Purchase Suggestion" In the form, Library defaults to patron's home branch instead of an empty value. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30812] New: subfield 9 deleted if no other data is available
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30812 Bug ID: 30812 Summary: subfield 9 deleted if no other data is available Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl DNB exports the ISBN with dashes in 020$9, which we import via SRU while cataloguing. Therefore we added a subfield 9 to field 020. But when 020 contains no data except the dashed ISBN in $9, the value of $9 is deleted. I assume this is caused by some special cases needed to delete the koha_id of an authority (which is often stored in $9). To reproduce: * Go to a framwork, field 020, add a subfield 9, visible in tab 0, OPAC, Intranet and edito * Go to a book, edit it, enter something in 020$a and 020$9, save * The values are stored * Edit again, remove the value from 020$a, save * the value from 020$9 is gone, too I can maybe take a look tomorrow to try to figure out what's happening.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31235] New: UseDaysMode is used for calculating the expiration date for waiting holds
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31235 Bug ID: 31235 Summary: UseDaysMode is used for calculating the expiration date for waiting holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is also a confusing one: The UseDaysMode system preference, that can also be set in the circulation rules is described as: ... when calculating the date due. BUT: In set_waiting it's also used to calculate the expiration date for holds: my $max_pickup_delay = C4::Context->preference("ReservesMaxPickUpDelay"); my $cancel_on_holidays = C4::Context->preference('ExpireReservesOnHolidays'); my $expirationdate = $today->clone; $expirationdate->add(days => $max_pickup_delay); if ( C4::Context->preference("ExcludeHolidaysFromMaxPickUpDelay") ) { my $itemtype = $self->item ? $self->item->effective_itemtype : $self->biblio->itemtype; my $daysmode = Koha::CirculationRules->get_effective_daysmode( { categorycode => $self->borrower->categorycode, itemtype => $itemtype, branchcode => $self->branchcode, } ); my $calendar = Koha::Calendar->new( branchcode => $self->branchcode, days_mode => $daysmode ); $expirationdate = $calendar->days_forward( dt_from_string(), $max_pickup_delay ); } I feel like this is quite odd as you can set ExcludeHolidaysFromMaxPickUpDelay to ignore the calendar (and then it will be ignored). But if you set it to use the calendar, it can still be ignored when the UseDaysMode setting is set to ignore calendar. So it should probably be: Ignore the calendar | Use UseDaysMode setting ... If asked previously, I'd have said don't make this rely on UseDaysMode and just use calendar or not. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 30381] New: On order items still available for item level holds with TrapHoldsOnOrder
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30381 Bug ID: 30381 Summary: On order items still available for item level holds with TrapHoldsOnOrder Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When TrapHoldsOnOrder is set to not trap holds with negative not for loan status, it's still possible to place an item level hold on these items in the OPAC. To test: - Create an item with not for loan -1 = on order - Set OPAC item level holds to 'Force' for its itemtype in circulation conditions - Try to place a hold on it from the OPAC - Notice that a checkbox to select the item displays and you can place a hold -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32246] New: Standardize start page layout between different modules
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32246 Bug ID: 32246 Summary: Standardize start page layout between different modules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The reports, cataloguing and Koha start page all leave room to the left, but the circulation page does not. It would be nice to adapt it for more consistency :) Also makes me wonder how to use that space - we have the news on the start page, maybe we could make this the dedicated area for IntranetReportsHomeHTML etc.? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 24550] New: Books renewals triggers item loan policies to revert to branch renewing item
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24550 Bug ID: 24550 Summary: Books renewals triggers item loan policies to revert to branch renewing item Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rrussell(a)pacificoaks.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 98192 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=98192&action=ed… Renewal changes item policies Since the new update, we've noticed issues with our items not following policies from their home branch, triggering overdue notices, causing issues with holds, not charging fines, and reverting to the default branch. Not certain if self renewal is triggering this as well. These were never issues before. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6