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

[Bug 23875] New: Elasticsearch - ES - When sorting by score we should provide a tiebreaker
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23875 Bug ID: 23875 Summary: Elasticsearch - ES - When sorting by score we should provide a tiebreaker Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com In ES if we sort by 'relevance' we actually don't pass anything to ES and results are ordered by score. When doing a search limiting only by collection or type, the scores are all the same. This is fine, except that editing any record will then cause a reordering of the results, even though it won't affect the score. We should provide a tie-breaker in the case of equal sort scores -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 30719] New: ILL should provide the ability to create batch requests
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '25

07 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30719 Bug ID: 30719 Summary: ILL should provide the ability to create batch requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Some interlibrary loan providers, for example Reprints Desk, allow for ILL requests to be submitted in batches. In the Reprints Desk case, a batch is created with the supplier, then requests are then submitted including the batch ID. Obviously, this workflow may differ according to supplier and these differences should be abstracted away into the supplier backend. For core Koha, we should provide the ability for it to recognise if a given backend can process batch requests. If so, we should provide an interface for creating and manipulating batches within Koha, then submitting a batch to the supplier. It should also be possible to view all batches and the contents of a given batch. The funding institution has defined the following workflow for creating and populating batches: - A encapsulating "batch" is created with a name and a requesting borrower - Requests are added to a batch via two methods: - In bulk: - A form which allows the user to paste in a collection of identifiers, such as DOI / PMID etc. - For each of these identifiers: - The request metadata should be populated via API queries to metadata suppliers, for example, PubMed API or LibKey/Browzine. This behaviour is governed by the presence of appropriate plugins. - (Optional) Once the metadata is populated for an item, we check for item availability via any installed ILL availability plugins - Individually: - A regular ILL request form, requests are added to the batch -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 194

[Bug 22815] New: Save item's homebranch in patron's fines list
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '25

06 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22815 Bug ID: 22815 Summary: Save item's homebranch in patron's fines list 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: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- bug 15136 added a column to the fines screen (boraccount.pl) that shows the item's home branch. If the item is deleted the branch information goes away. It would be helpful if that column was filled and the data saved so if the item is deleted the information is not lost. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 29074] New: DefaultHoldExpirationdatePeriod blank value interpreted as zero
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '25

03 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29074 Bug ID: 29074 Summary: DefaultHoldExpirationdatePeriod blank value interpreted as zero 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 26498 If DefaultHoldExpirationdate is on and DefaultHoldExpirationdatePeriod is blank, the blank is treated as a zero and all holds are created with an expiration date of today. I'm not sure what the best answer is. We could: - add some text to the syspref to make clear that a blank is treated as zero - make it always save and display a zero when you try to save a blank or - make it treat a blank as disabled (and then add some text to the syspref to tell people that) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26498 [Bug 26498] Add option to set a default expire date for holds at reservation time -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 25787] New: Club holds can't be placed without modify_holds_priority permission
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '25

03 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25787 Bug ID: 25787 Summary: Club holds can't be placed without modify_holds_priority permission Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Staff cannot place a request for a patron club if the staff member does not have modify_holds_priority set. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 26476] New: Make hold request notes editable
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '25

02 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26476 Bug ID: 26476 Summary: Make hold request notes editable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are times that staff may alter a hold, or move it. Some libraries need to have an explanation of the change, especially if a staff member changes the priority. Currently, you cannot edit a hold after it is placed. It would be helpful if staff could modify the note field at any time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 30274] New: Non-reservable items should only fill item-level reserves
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '25

02 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30274 Bug ID: 30274 Summary: Non-reservable items should only fill item-level reserves 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com For item types where 'holds allowed(total)' equals 0, you can still place reserves on these non-reservable items via the staff client by overriding the circulation rule. The bug is that, when you check in an item that is non-reservable (holds allowed is 0), it will trigger the holds pop-up and can fill a biblio-level hold ("next available"). The holds pop-up should only be triggered by non-reservable items if there is an item-level reserve on it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 23581] New: Do not fill hold when patron account has overdues/fines
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '25

02 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23581 Bug ID: 23581 Summary: Do not fill hold when patron account has overdues/fines Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Would like to see a preference that would keep a patron from advancing and/or having holds filled in the queue if they have overdue items and/or fines. This could be used as an incentive to return items on time and not play the system in some ways, especially in libraries that don't charge fines. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28500] New: Display before and after values when a biblio has been edited
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28500 Bug ID: 28500 Summary: Display before and after values when a biblio has been edited Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Trying to determine what information was changed in a biblio is rather difficult. While there is some functionality in the logs, not all staff have access to the logs, nor is the info easy to interpret. It would be really helpful to have another method of tracking changes to bib records, such as a simple BEFORE value: xxxx AFTER value: xxxxx that only records the changes made, which user made the change, and when. Ideally this would be viewable outside of logs, perhaps through reports, and kept for the entire time the biblio is in the catalog. This is very important for libraries that have multiple locations and multiple staff editing biblios - there is a need to see who made what changes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 30653] New: "Check out" search with one result does not redirect to checkout
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30653 Bug ID: 30653 Summary: "Check out" search with one result does not redirect to checkout Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I am seeing this on 21.11.04. I go to the front page of the intranet. The "Check out" tab of the header search is active as default. I type my name into the search box and press enter. This takes me to this page: /cgi-bin/koha/members/member.pl?quicksearch=1&circsearch=1&searchmember=magnus%20enger This page shows one result, and the "Card" column links to: /cgi-bin/koha/circ/circulation.pl?borrowernumber=1 while the "Name" column links to: /cgi-bin/koha/members/moremember.pl?borrowernumber=1 If I choose my name in the typeahead/dropdown that appears below the search box, I am taken to this page: /cgi-bin/koha/circ/circulation.pl?borrowernumber=1 Then I do the same thing in 21.05.05: Type my name in the "Check out" box and press Enter. There I am taken directly to: /cgi-bin/koha/circ/circulation.pl (This is a POST, so borrowernumber=1 is not visible in the URL). Looking more closely at the source of /cgi-bin/koha/members/member.pl?quicksearch=1&circsearch=1&searchmember=magnus%20enger in 21.11.04 I do see this: $.ajax({ 'dataType': 'json', 'type': 'POST', 'url': sSource, 'data': aoData, 'success': function(json){ // redirect if there is only 1 result. if ( json.aaData.length == 1 && aoData.iDisplayStart == 0 ) { var borrowernumber = json.aaData[0].borrowernumber; /* Overwrite history state of firstletter search since only one result was returned; This prevents a loop upon clicking back */ history.replaceState( {}, null, window.location.href.split("?" )[0]); document.location.href="/cgi-bin/koha/circ/circulation.pl?borrowernumber="+borrowernumber; return false; } fnCallback(json); } }); This seems to incorporate the fix from bug 29411, but it does not seem to be working. There is nothing in the console. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4