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

[Bug 39541] New: Do we need to store the whole MARC record in Elasticsearch?
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39541 Bug ID: 39541 Summary: Do we need to store the whole MARC record in Elasticsearch? Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org Currently the whole MARC Record is stored in the ElasticSearch Record. At the Koha Hackfest 2025 I learned that one reason for this is to be able to search the whole record (Bug 22258). Another reason might be to avoid hitting the DB when displaying search results. But: * We sometime encounter problems with very large records (due to limits with UNIMARC) * The code to store the whole record is rather convoluted (involes encoding/decoding the record, checking for errors, falling back to other encoding methods..) * It bloats the ES index (if it's not needed) So I will investigate: * would displaying search results work without the whole MARC record? * aren't we hitting the DB anyway during displaying search results * in OPAC * in Staff * in API If it seems easy to optionally not add the whole record to the index, I would suggest * Adding a new Option "Don't store" to syspref ElasticsearchMARCFormat * If it is set, skip adding the whole MARC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 32581] New: Update dateexpiry on categorycode change
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32581 Bug ID: 32581 Summary: Update dateexpiry on categorycode change 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: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you change a patron's category code, nothing checks whether their existing dateexpiry is valid for their category. An immediate renewal will correct this, but without that step, you could have someone move from a category with longer enrollment into a shorter enrollment period without anything prompting a check if that dateexpiry is still valid. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 Sara Brown <sbrown(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=42168 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25384] New: Label maker font list is not configurable
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384 Bug ID: 25384 Summary: Label maker font list is not configurable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The label maker font list is hard-coded to 12 arbitrary choices. It would be better if we could configure the font choices in the user interface (since we can already configure the truetype font files in koha-conf.xml). -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 42167] New: Show first name if different from preferred in 'Add guarantor' search
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42167 Bug ID: 42167 Summary: Show first name if different from preferred in 'Add guarantor' search Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If ShowPatronFirstnameIfDifferentThanPreferredname is set to [Show], a patron's first name shows in brackets next to their preferred name (if they differ) when searching for patrons in quick and full patron search, while placing a hold, and when searching for patrons from the 'Check out' tab. However, the first name doesn't show in search results using the 'Add guarantor' feature. For consistency across types of patron search, it would be helpful if it could show there as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 36741] New: AUTO_RENEWALS_DGST should skip auto_too_soon
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36741 Bug ID: 36741 Summary: AUTO_RENEWALS_DGST should skip auto_too_soon Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I think it's debateable that auto_too_soon items should show up in the AUTO_RENEWALS_DGST at all, but I can think of reasons why they would be useful to show (you might want to show which items weren't renewed because it was too soon). But at the moment, the AUTO_RENEWALS_DGST doesn't account for them. It just prints out the title and barcode, which looks ridiculous. We need a default. Either to skip auto_too_soon in that loop, or to say that it's too soon for it to be renewed. I'm in favour of the former. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 21779] New: Holds history doesn't show where hold placed
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21779 Bug ID: 21779 Summary: Holds history doesn't show where hold placed Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: siobhancottam(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The Holds history tab doesn't show the same information as the modification log e.g. if the reservation was placed in the OPAC or staff client. It is possible to find this information from the log viewer, but not from a patron record modification log as this doesn't show holds at all. This is time-consuming to find the relevant hold if you don't already know the approximate date when the hold was placed. The system log uses the reserve ID as the Object, which is presumably why it doesn't show in the Patron log where their borrowernumber is the Object no. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 41981] New: Searching patrons by partial name not working
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41981 Bug ID: 41981 Summary: Searching patrons by partial name not working Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andres.castro(a)ues.edu.sv QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com For version 24.11.12, when searching for a patron by partial name in the intranet admin site, an alert error pops up saying: "Something went wrong when loading the table. 502: error." I have looked the following log files but I have not found any clues on what's wrong: - intranet-error - plack-intranet-error - api-error - plack When the search box is empty and I press enter, no errors appear but of course all patrons are shown. Searching by card number works without any issues. I upgraded to 24.11.13 since it's the latest version as of March 3rd 2026 but the error is still showing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 42162] New: Allow patron attribute to show based on value in another attribute
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42162 Bug ID: 42162 Summary: Allow patron attribute to show based on value in another attribute Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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(a)bywatersolutions.com It would be helpful to allow a patron attribute to be shown or hidden based on the value in another attribute. One use case: - an attribute is tied to an authorized value list that includes "Other" - when "Other" is selected, a second attribute appears to allow a free-text entry I suppose this could be coded as specifically the ability to use an "Other" value with a free-text field, but I think other use cases may exist for a more flexible implementation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 42160] New: automatic_renewals.pl reindexes by itemnumber, should reindex by biblionumber
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42160 Bug ID: 42160 Summary: automatic_renewals.pl reindexes by itemnumber, should reindex by biblionumber Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz automatic_renewals.pl does this: push @item_renewal_ids, $auto_renew->itemnumber; ... my $indexer = Koha::SearchEngine::Indexer->new( { index => $Koha::SearchEngine::BIBLIOS_INDEX } ); $indexer->index_records( \@item_renewal_ids, "specialUpdate", "biblioserver" ); So, it is calling index_records with the itemnumbers to be indexed. Everywhere else similar calls to index_records use biblionumbers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0