June 2023 - Koha-bugs - lists.koha-community.org

[Bug 23059] New: reserves_stats.pl needs overhaul
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '23

26 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23059 Bug ID: 23059 Summary: reserves_stats.pl needs overhaul Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- This bug is sort of a catch-all for changes that need to be made to the holds statistic wizard, reserves_stats.pl Two big issues: - By default, the wizard sets a value for items.homebranch and items.holdingbranch. That means it unexpectedly cuts out all bib-level holds and gives no clear indication that it's done so. You *can* change home and holding branch to not limit, but it's not intuitive. - The wizard splits holds into 5 statuses (Placed, Processed, Pending, Satisfied, and Cancelled) that aren't used anywhere else in Koha. These statuses aren't explained without diving into the code and don't match how we otherwise divide and talk about holds. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 31832] New: Add reference for EnableItemGroups to EnableItemGroupHolds system preference
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '23

26 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31832 Bug ID: 31832 Summary: Add reference for EnableItemGroups to EnableItemGroupHolds system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: System Administration 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 Item group holds only make sense if the library allows item groups in the first place. We should add a note to the system preference linking them together. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 33947] New: Move GetAllIssues to Koha
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33947 Bug ID: 33947 Summary: Move GetAllIssues to Koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 33576] New: Records are not indexed when imported if using Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33576 Bug ID: 33576 Summary: Records are not indexed when imported if using Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The importing is done in a transaction. We call the indexer form inside the transaction. This means that when rabbit sends the task, it may not be found in the DB yet. We need to ensure we index after the transaction completes -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 33019] New: Records not indexed in Elasticsearch ES when first catalogued
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33019 Bug ID: 33019 Summary: Records not indexed in Elasticsearch ES when first catalogued Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz We have a Koha instance where records are not being indexed into Elasticsearch when they are first catalogued. They can be accessed if you go to the catalogue detail page directly, but cannot be searched. However if you edit the record and save, it is indexed successfully. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 28205] New: Less important hold trapped before or no hold trapped in some cases (race condition)
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28205 Bug ID: 28205 Summary: Less important hold trapped before or no hold trapped in some cases (race condition) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com So our libraries ran into a strange hold problem which turned out to be a race condition: if you change priority of holds and return an item and build_holds_queue.pl cron is not yet run again the priority is not updated and you fill hold with less importance! After build_holds_queue.pl the priorities are OK because hold_fill_targets gets updated according to the right hold priority. Similar race condition also happens when you have already some items for the biblio in hold_fill_targets and add a new item to the biblio and try to return it it doesn't attach to any waiting holds until the build_holds_queue.pl is ran. To better understand the issue I think it is easier to look the code in C4::Reserves::_Findgroupreserve(). Explaining with words is bit difficult... Basically in that function the SQL selects > my $title_level_target_query = qq{ > my $query = qq{ should be UNION'ed to fix the case when adding new item which could potentially fill the hold. This might cause unoptimal logistic route to be used but still would follow the hold priority. To fix the issue of changing hold priorities we need to update hold_fill_targets table by calling C4::HoldsQueue::CreateQueue() every time staff member updates hold priorities in a biblio. But even with these improvements wouldn't this be buggy when deleting items from the biblio record? Not sure how to solve that case. Added major bug priority for this but if you feel like it doesn't deserve it feel free to change to normal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 30926] New: Remove unnecessary use statements
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30926 Bug ID: 30926 Summary: Remove unnecessary use statements Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 17600 We have 'use' statements that are useless. We could remove them. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17600 [Bug 17600] Standardize the EXPORT -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 31072] New: Remove direct CSV export in itemsearch.pl
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31072 Bug ID: 31072 Summary: Remove direct CSV export in itemsearch.pl Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: simon.hohl(a)dainst.org QA Contact: testopia(a)bugs.koha-community.org I am not 100% sure if this is something you are considering in need of fixing, but anyway: We just had a colleague crashing our system by running multiple searches with cgi-bin/koha/catalogue/itemsearch.pl. The search scope was rather broad (a lot of entries) and the output option had been set to CSV (without going to the "screen" view). Because the interface did not give any feedback after starting the search (it just indicated "website loading"), the colleague refreshed the browser window and started another search. The result: We had 2 processes running on the server, using 8gb of RAM each, thus causing our server to grind to a halt. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 33620] New: Don't show patron-privacyguarantor/patron-privacy_guarantor_fines if borrowerRelationship is empty
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33620 Bug ID: 33620 Summary: Don't show patron-privacyguarantor/patron-privacy_guarantor_fines if borrowerRelationship is empty Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On the patron detail screen there are two list items: -Show checkouts to guarantor -Show charges to guarantor I end up hiding these with CSS often. It would be better if these simply did not show if borrowerRelationship is empty. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 27873] New: Make display of patron restrictions, charges, notes, etc. consistent for check out and patron details screens
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27873 Bug ID: 27873 Summary: Make display of patron restrictions, charges, notes, etc. consistent for check out and patron details screens Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On the check out screen (circulation.pl) info about the patron’s account displays in the following order: expiration, restrictions, charges, notes, messages. But on the patron details screen (moremember.pl) the info displays in a different order: charges, messages, notes, restrictions, expiration. For consistency it seems like the info should display in the same order on both screens. Additionally it would help when training new staff members and when working a busy information desk to be able to rely on finding the information in the same place on both screens. Our Library prefers the sort order that displays on the check out screen because it puts the expiration date, restrictions and then charges at the top of the screen so that staff can quickly see the status of the account and handle them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35