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

[Bug 23010] New: If an item is checked out or in transit it should not be able to be marked withdrawn
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '26

14 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23010 Bug ID: 23010 Summary: If an item is checked out or in transit it should not be able to be marked withdrawn Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Currently an item can be marked withdrawn if it is checked out to a patron or in transit from one branch to another. This causes confusion for staff checking an item back in or receiving the transfer. If an item is checked out or in transit it should not be able to be marked withdrawn. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 107

[Bug 23260] New: Anonymize (remove) patron data from items_last_borrower
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '26

13 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23260 Bug ID: 23260 Summary: Anonymize (remove) patron data from items_last_borrower Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Increase level of patron privacy by removing patron information from the items_last_borrower table after a set period of time. Adjust the batch_anonymize cronjob to also remove data from the items_last_borrower table when the data is more than x days old (runtime option) but not if the item is lost, damaged, or withdrawn. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 332

[Bug 28528] New: bulkmarcimport delete option doesn't delete biblio_metadata
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '26

13 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28528 Bug ID: 28528 Summary: bulkmarcimport delete option doesn't delete biblio_metadata Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When using bulkmarcimport with the -d switch should not only delete biblio, biblioitems and items, but also biblio_metadata. I haven't checked if a FK takes care of the data, but if it does, we should still also reset the AUTO_INCREMENT: https://git.koha-community.org/Koha-community/Koha/src/branch/master/misc/m… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 16530] New: Add a circ sidebar navigation menu
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '26

13 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16530 Bug ID: 16530 Summary: Add a circ sidebar navigation menu 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: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com (Similar to the tools sidebar menu). This is just an idea that I thought would make navigation around the circ module a bit easier ... I realise that it changes the display of many of the pages so I appreciate any thoughts on the upcoming patch. :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 25918] New: Add budget/fund modification history to function added in BUG 25916
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '26

11 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25918 Bug ID: 25918 Summary: Add budget/fund modification history to function added in BUG 25916 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org Created attachment 106480 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106480&action=e… A mock-up of Modify Fund page with the history feature added. The acquisitions SIG discussed this enhancement and came up with this feature that multiple libraries said would help their workflow. The specific feature is to display a history of changes to the fund that is collapsible. I have attached a mock-up of the 'Modify Fund ...' screen that would incorporate the feature the libraries would like. This enhancement is a further enhancement of the function added in Bug 25916. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 25916] New: Create UI to modify budgets and funds.
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '26

11 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25916 Bug ID: 25916 Summary: Create UI to modify budgets and funds. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org Created attachment 106479 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106479&action=e… Mock-up of Modify Fund page with +/- and transfer function The Koha-US Acquisitions SIG discussed this enhancement and came up with some features that multiple libraries said would help their workflow. The specific features are a need a transfer between funds function as well as a add/subtract function for each account. I have attached a mock-up of the 'Modify Fund ...' screen that would incorporate the features the libraries would like. Page 1 is a suggestion to make the fund modification screen accessible from the 'all available funds... page. Page 2 shows what the current 'Modify Fund....' page looks like. Page 3 shows the mock-up of how we would like it to look. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 28491] New: field 003 not updated after import
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28491 Bug ID: 28491 Summary: field 003 not updated after import Change sponsored?: --- Product: Koha Version: master 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: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org I import some authority data from e.g. dnb.de, which contains: <controlfield tag="001">11915725X</controlfield> <controlfield tag="003">DE-101</controlfield> After the import, the local authority data looks like <controlfield tag="001">35</controlfield> <controlfield tag="003">DE-101</controlfield> So 001 now contains the internal Koha id (good), but 003 still points to DE-101 (i.e. dnb.de), which I think is bad, because if I look up the ID '35' in the linked DB DE-101, I will now get a bad result. I assume that 003 should be set to my MARCOrgCode Looking at the code, I find (in C4::AuthoritiesMarc, AddAuthority, 568ff) if (!$record->field('003')) { $record->insert_fields_ordered( MARC::Field->new('003', $marcorgcode), ); } So this behavior seems intentional? If so, I still find it very unlogical and buggy. I assume that both 001 and 003 should be overwritten with data pointing to the current Koha instance, and the original 001/003 "archived" in 035 and/or 040 I could easily provide a patch that changes this behavior, but I'm not sure if this would cause confusion / failing tests / etc. Maybe add an option to allow a force-overwrite of 003? Greeting, Thomas PS this seems slightly related to #25603 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 27357] New: Trigger printing of a routing list, when an issue is received
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27357 Bug ID: 27357 Summary: Trigger printing of a routing list, when an issue is received Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the printing of a routing list happens separately from receiving the issue and requires extra steps and attention to not be forgotten. It would be nice, if the printing of a routing list was triggered by receiving an issue to have a more streamlined process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28628] New: Elasticsearch - Heading search form does'nt match related indexed heading
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28628 Bug ID: 28628 Summary: Elasticsearch - Heading search form does'nt match related indexed heading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com When an authority is created using LinkBibHeadingsToAuthorities the heading created "700 $aVidard $bMathieu $f1971-..." (unimarc) is saved as "Vidard Mathieu 1971-..", indexed as "Vidard Mathieu 1971-.." and searched as "Vidard Mathieu 1971" => no match. So the link bib does'nt work. Test plan (UNIMARC exemple): - create a biblio with the following data in tag 700: - $a Vidard - $b Mathieu - $d 1971-... - save. => a new authority is created with the following heading "Vidard Mathieu 1971-.." - create an other biblio with the same value in tag 700. => again a new authority is created with the same heading. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 19852] New: Add message text box in circulation for patrons does not accept HTML tags
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19852 Bug ID: 19852 Summary: Add message text box in circulation for patrons does not accept HTML tags Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 69958 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=69958&action=ed… result after adding HTML tags for a patron message Hi When you add a patron message in circulation.pl, the modal that appears has a text box that does not accept HTML tags. Some libraries use HTML tags in these messages to link to information in Koha and to format the display of the message (see attached). Having this modal accept HTML would allow formatting and linking in messages. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13