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

[Bug 15248] Make it possible to configure duplicate check on bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #26 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- QA tool is cranky about a lot of missing POD: [FAIL] C4/Matcher.pm FAIL pod_coverage sub _passes_required_checks has no pod coverage. sub _new_marc_matchers has no pod coverage. sub _del_matcher_components has no pod coverage. sub _store_matcher_components has no pod coverage. sub _get_match_keys has no pod coverage. sub _fetch_matchpoint has no pod coverage. sub _parse_match_component has no pod coverage. sub _store_matchpoint has no pod coverage. sub _update_marc_matchers has no pod coverage. [FAIL] C4/Search.pm FAIL pod_coverage sub _detect_truncation has no pod coverage. sub _build_stemmed_operand has no pod coverage. sub _build_weighted_query has no pod coverage. sub _get_facets_from_records has no pod coverage. [FAIL] Koha/BiblioFramework.pm FAIL pod_coverage sub _type has no pod coverage. [FAIL] Koha/BiblioFrameworkMarcMatcher.pm FAIL pod_coverage sub _type has no pod coverage. [FAIL] Koha/BiblioFrameworkMarcMatchers.pm FAIL pod_coverage sub _type has no pod coverage. [SKIP] Koha/Schema/Result/BiblioFrameworkMarcMatcher.pm SKIP pod_coverage No POD exists [SKIP] Koha/Schema/Result/MarcMatcher.pm SKIP pod_coverage No POD exists -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9750] Bring routing lists into notices & slips
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9750 --- Comment #18 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- > 2. No templates were created for ROUTING_LIST in any of the languages for > "Email" but does show for "Print" > I think Print and no Email is correct here as this is like a "slip". But maybe misundersanding the issue? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9150] Add id and relevance as sort options for authorities search
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9150 --- Comment #5 from cgresser <cgresser(a)jesuit.org.uk> --- I don't think one can sort any Authorities search results by Authority ID. It might, however, be really useful if there are a lot of newer or older entries duplicating or near-duplicating an authority heading. I had to browse through hundreds of authority entries for a 2-3 element authority, e.g. "Catholic Church -- Doctrines -- History". I might be doing this wrong, but it seems that I cannot search for such complex entries in one search string. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42192] New: Don't index 490$9 (MARC 21)
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42192 Bug ID: 42192 Summary: Don't index 490$9 (MARC 21) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org MARC 21 does not have a 490$9: https://www.loc.gov/marc/bibliographic/bd490.html The default framework does not have a 490$9: https://git.koha-community.org/Koha-community/Koha/src/branch/main/installe… But we index 490$9 in the koha-auth-number index, along with a number of other $9 subfields: https://git.koha-community.org/Koha-community/Koha/src/branch/main/admin/se… I discovered this in the wild because some migrated records had 490$9 subfields, had junk in them, that was causing weird search results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 42205] New: Field 001 in Authorities cannot be set freely
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42205 Bug ID: 42205 Summary: Field 001 in Authorities cannot be set freely Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: mark(a)hofstetter.at QA Contact: testopia(a)bugs.koha-community.org In Authorities you cannot set the value of Marc Field 001, it is filled with the database id (authid) from the table. This is wrong from a technical point of view (db ids shouldn't have a meaning in the real world) But more important it make it hard to import linked bibliographic and authority, because you know the authid only after the import. So I propose to add the abilty to chose the 001/controlnumber freely and have it accessable in the auth table -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42158] New: Overdue notice trigger setup offers too many letter options
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42158 Bug ID: 42158 Summary: Overdue notice trigger setup offers too many letter options Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: chloe.zermatten(a)openfifth.co.uk, lisette(a)bywatersolutions.com, martin.renvoize(a)openfifth.co.uk, nick(a)bywatersolutions.com When setting up overdue notices, the letter dropdown includes all notices with module Circulation. That gives a very long list of options that includes several templates that are hardcoded for other processes (like DUE and PREDUE). It would be helpful to shorten that list. Maybe we could define a new letters module value of Overdues? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 9150] Add id and relevance as sort options for authorities search
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9150 --- Comment #4 from Fridolin Somers <fridolin.somers(a)biblibre.com> --- (In reply to cgresser from comment #3) > I would second this, as searching authorities can be hard for more complex > authorities (i.e. with more than 2 or 3 elements). Please consider as a > much-wanted enhancement. > Clemens You mean sorting by authority type ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36393] New: Renewal with a specific date does not take the new date due that we pick
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36393 Bug ID: 36393 Summary: Renewal with a specific date does not take the new date due that we pick 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: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce 1- Log in to the staff interface 1-1. Make sure you have a ciculation rule that allows you to renew 1-2. set the AllowRenewalLimitOverride system preference to Allow and SpecifyDueDate to Allow 2. Check out the item to a Borrower 5. Access the borrower's account and renew it until the limit is reached and note the due date. 6. Go to Circulation, click Renew 7. Enter the item barcode and choose a due date further than the due date from step 5 and submit 8. Click on Override limit and renew button ---> Note that the new date due is not the date that we picked in step 7 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 37189] New: Renewals: Koha prioritizes hard due date from circulation rules over manual due date, although the manual due date is earlier
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37189 Bug ID: 37189 Summary: Renewals: Koha prioritizes hard due date from circulation rules over manual due date, although the manual due date is earlier Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: isabel.pineda(a)ds.edu.sv QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I wrote this comment last week in Bug 36393, but I am not sure if this bug is still being attended, so I decided to file a new bug. Please delete it if it is duplicated: After updating from version 23.11 to 24.05, the renewal for a specific date is not working anymore. Although I give a specific date for a specific renewal, the system takes automatically the hard due date from the circulation rules. e.g. In "Administration > Circulation rules" I save "15.08.2024" as hard due date for a specific item type and patron category. Then I go to one patron of the above category to renew his borrowed items, and manually select "30.07.2024" as due date. -> The system renews the items until 15.08.24. It ought to prioritize the manual due date for this specific patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 40560] New: Incorrect breadcrumb on recall history
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40560 Bug ID: 40560 Summary: Incorrect breadcrumb on recall history Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It is still using the "old way" and is not looking good: https://snipboard.io/uo10iU.jpg -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18