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

[Bug 36352] New: Allow agreements to have multiple vendors
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36352 Bug ID: 36352 Summary: Allow agreements to have multiple vendors Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: billieanne.gebb(a)frontier.edu CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Some agreements may have multiple vendor relationships, for example, a title could be published by one entity but billed through another. It would be helpful to have both listed with the agreement. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 29649] New: [DOCS] What's new section
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29649 Bug ID: 29649 Summary: [DOCS] What's new section Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: david(a)davidnind.com Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Consider creating a "What's new" section that highlights in a "librarian friendly" way the new features, enhancements, and things fixed in a release - each item would eventually link to the updated section(s) in the documentation. This could make it easier for Koha Community members to identify what's new in a release, and save some of the work that support providers do each release highlighting the changes (or at least create a good starting point!). It could also be supported by a presentation (for use at events) and a video. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 24438] New: index can fail on timeout
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24438 Bug ID: 24438 Summary: index can fail on timeout 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 We have seen occasional timeouts when indexing elasticsearch, these cause the indexing to stop and fail. We should handle the response as the code indicates: 102 sub update_index { 103 my ($self, $biblionums, $records) = @_; 104 105 my $conf = $self->get_elasticsearch_params(); 106 my $elasticsearch = $self->get_elasticsearch(); 107 my $documents = $self->marc_records_to_documents($records); 108 my @body; 109 110 for (my $i=0; $i < scalar @$biblionums; $i++) { 111 my $id = $biblionums->[$i]; 112 my $document = $documents->[$i]; 113 push @body, { 114 index => { 115 _id => $id 116 } 117 }; 118 push @body, $document; 119 } 120 if (@body) { 121 my $response = $elasticsearch->bulk( 122 index => $conf->{index_name}, 123 type => 'data', # is just hard coded in Indexer.pm? 124 body => \@body 125 ); 126 } 127 # TODO: handle response 128 return 1; 129 } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 29814] New: Unwanted dashes added to authorities Zebra indexing
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29814 Bug ID: 29814 Summary: Unwanted dashes added to authorities Zebra indexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com In Zebra authorities configuration, when using index_heading the subdivisions are joined with two dashes. You can see this when looking at what is indexed : https://wiki.koha-community.org/wiki/Troubleshooting_Zebra#Which_indexes_ar… For example : field 250 $a Cinéma $x Films $y France $z 2010 Shows : <z:index name="Subject-topical-heading:w Subject-topical-heading:p Subject-topical-heading:s Heading:w Heading:p Heading:s">Cinéma--Films--France--2010</z:index> And a search "Cinéma Films France 2010" on main heading does not find this record. It comes from https://git.koha-community.org/Koha-community/Koha/src/commit/895fc88605f73… Anyone knows where this comes from and how it is supposed to work ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28318] New: accounlintes.credit_number missing on the API
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28318 Bug ID: 28318 Summary: accounlintes.credit_number missing on the API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com It was added to the DB structure, but bug 28272 skipped it so we could ponder if it is required on the API object and how should we name it. Feels like 'credit_sequence_number' could be a good name for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18407] New: REST API: Include renewability information on checkouts
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18407 Bug ID: 18407 Summary: REST API: Include renewability information on checkouts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org It would be useful to have renewability information directly in the /checkouts endpoint to avoid making additional requests. However, this could be optional. Create /api/v1/checkouts/expanded endpoint to include additional data on checkouts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 29643] New: [DOC] Review and update koha-manual git repository README and CONTRIBUTING files
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29643 Bug ID: 29643 Summary: [DOC] Review and update koha-manual git repository README and CONTRIBUTING files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Documentation Assignee: david(a)davidnind.com Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Review and update the koha-manual git repository README and CONTRIBUTING files to include: * A link to Documentation Team wiki pages * A link to CONTRIBUTING.md * Make the information about setup, producing output and useful commands more concise The main goal is to make it more useful and clearer for those that would like to contribute a change to the manual. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 35722] New: Item transfer operations should be available from the API
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35722 Bug ID: 35722 Summary: Item transfer operations should be available from the API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com We don't expose the item transfer queue in the API yet.. we should. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 35937] New: Add hourly support to Bookings
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35937 Bug ID: 35937 Summary: Add hourly support to Bookings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 29002 Bug 29002 adds the ability to book items ahead of time. It works at the daily loan level, but stores hours with the intention of expanding it to support hourly bookings. We should expose these hourly bookings as an option to end users. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29002 [Bug 29002] Add ability to book items ahead of time -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 40258] New: Option to only use item-level recalls and disable record-level recalls
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '26

03 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40258 Bug ID: 40258 Summary: Option to only use item-level recalls and disable record-level recalls Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com It would be good to essentially hide the "Recall next available item" options for libraries who do not want record-level recalls -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19