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

[Bug 35191] New: Make entries per page configurable for items table on staff detail page
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35191 Bug ID: 35191 Summary: Make entries per page configurable for items table on staff detail page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 33568 The new API driven items view defaults to 20 per page. This is a bit low, it would be great if it could be configurable to a higher value per the table configuration. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33568 [Bug 33568] Use the REST API to display items on the biblio detail view -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 32802] New: Bundle handling JS should be moved to an asset
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32802 Bug ID: 32802 Summary: Bundle handling JS should be moved to an asset Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 29560, 31080, 31615, 32121 The item bundling Javascript has come quiet extensive.. it should be tidied up somewhat and moved into it's own asset file. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29560 [Bug 29560] Add option to create MARC links when adding items to bundles https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31080 [Bug 31080] Block adding the bundle item to its own bundle https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31615 [Bug 31615] Allow checkin of items bundles without verifying their contents https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32121 [Bug 32121] Show an alert when adding a checked out item to an item bundle -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 16122] New: Item record needs to keep Local Use count
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16122 Bug ID: 16122 Summary: Item record needs to keep Local Use count Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Like the "issues" field in the items table, there should be a field for "local_use" to keep the count of local uses. While this information is kept in the statistics table, it is a task to acquire, and if a library wants to keep bloat down on their tables, the statistics are pruned on a regular schedule, which means loss of valuable data. This counter would keep that valuable information in one field in each item record, rather than having a separate field for each instance in the statistics table. Unless it is vital to someone to know the exact moment a local use occurred, I am suggesting that this piece of information not be recorded in the statistics table any longer. This would significantly reduce the growth of the statistics table in general. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 163

[Bug 27769] New: Advanced editor shouldn't break copying selected text with Ctrl+C
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27769 Bug ID: 27769 Summary: Advanced editor shouldn't break copying selected text with Ctrl+C Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, nick(a)bywatersolutions.com Depends on: 17179 Bug 17179 added a shortcut for Ctrl+C to copy the line where the cursor is into the advanced editor's clipboard div. That only works if you don't have text selected. If you have text selected, the shortcut silently does nothing, but Ctrl+C, which I've used for decades to copy selected text, doesn't copy the text. Dozens of times a day, I copy the OCLC control number from a record, or the contents of an 024, do an advanced search for that number (where I can no longer actually see what record I'm replacing), and replace the record. Despite having now spent months trying to train myself that Ctrl+C has been broken (difficult training since I catalog both on a Mac, where Cmd+C has not been broken, and on Windows where it has), every couple of weeks I catch myself having just replaced a record with some record I had previously successfully right-click copied data from. How often do I *not* catch myself, and replace a record with a record for a completely different bib? Dunno, I'd really rather not think about that. The keyhandler looks like it'a a CodeMirror command, and the very scanty documentation says that a CodeMirror key handling command can return CodeMirror.Pass to let other handlers or the default behavior handle the key. Currently the handler does "return true" when it sees selected text and decides not to handle Ctrl+C. If instead returning cm.Pass would make the system clipboard work when text is selected, and the advanced editor clipboard work when no text is selected, that would be the best outcome. Second best would be deciding that silently causing the system clipboard to fail was a bad idea, and switching the default shortcut to something else. Yes, there is a system-wide option to change keys. For me, that means getting 14 people to agree on a different key, then starting the process of persuading an admin to make the change. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17179 [Bug 17179] Advanced editor: Add keyboard shortcuts to repeat (duplicate) a field, and cut text -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 31092] New: Upon importing batch records, if a full MARC record is found, only append the items; do not overlay a full MARC record
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31092 Bug ID: 31092 Summary: Upon importing batch records, if a full MARC record is found, only append the items; do not overlay a full MARC record Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: balestrieri(a)monterey.org QA Contact: testopia(a)bugs.koha-community.org When receiving items from our vendors, the full MARC records are sent in batches for import. We would like the ability to have koha only overlay our brief "on order" records that already exist in the system, not our full records already in our system. Currently, the only choice is to overlay ALL or NO records (choices are "Replace, Add, or Ignore") and to append the items, depending on the matching rule used (most users currently match on ISBN when importing books, audiobooks). Apparently, other ils systems have the ability to determine which existing records are brief and which existing records are full, and you can choose to only overlay the brief MARC records, leaving the full MARC records in tact, appending only the items. I understand the definitive markers are in the leader of the marc record. The leader will show the level of marc record it is. Most loaders will have a function to put this as one of the criteria. An example of an incoming Leader: =LDR 01429pam a2200385 i 4500 Position 17 is the encoding level. The above encoding level is blank, so it is a full level record. Encoding levels: Blank - full level record 1 - full level record 2 – less-than-full level record 3 – less than full level record 4 - less than full level record 5 – less than full level record 6 - less than full level record 7 – less than full level record 8 – less than full level (this is a prepublication record) It would be most convenient if koha would have an internal matching rule that allows for the user to overlay only existing records where levels 2-8 are in position 17 on the MARCs, ignoring any records with a "blank" or "1" in position 17 on existing MARCS, with the ability to still append all items. Right now, many of us in aquisitions need to create separate vendor accounts to order "added/existing" items only to avoid the constant overlaying of full MARC records in koha. We know any items arriving from these accounts already have full records in our system, so the vendor does not send full MARCs for any items ordered from these accounts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 35115] New: ERM - Potential MARC data loss when importing titles from list
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35115 Bug ID: 35115 Summary: ERM - Potential MARC data loss when importing titles from list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: pedro.amorim(a)ptfs-europe.com CC: caroline.cyr-la-rose(a)inlibro.com, jonathan.druart+koha(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 To reproduce: 1) Enable ERMModule sys pref 2) Create a new public list, visit: /cgi-bin/koha/virtualshelves/shelves.pl 3) Click "New list" enter name, set public -> public 4) Click "Add items", enter 112\n113\n114 (new line for each), in "Biblio numbers" 5) Notice that all added biblios have quite a few MARC fields 6) Go to packages, visit: /cgi-bin/koha/erm/eholdings/local/packages 7) Create a new package, add a name and hit 'Submit' 8) Go to titles, visit: /cgi-bin/koha/erm/eholdings/local/titles 9) Click "import from list" 10) Pick the package created in 7) 11) On the row of the list created in 2), click "Import" 12) Go back to the list, visit: /cgi-bin/koha/virtualshelves/shelves.pl?op=view&shelfnumber=1 13) Notice all the biblios have been stripped of their MARC data, and only title remains. Setting this as 'major' for now as I don't think this is intended or desired behavour. -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 39010] New: Allow RestrictPatronsWithFailedNotices to take a days variable, set in intranet
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39010 Bug ID: 39010 Summary: Allow RestrictPatronsWithFailedNotices to take a days variable, set in intranet Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 23295 restrict_patrons_with_failed_notices.pl is hardcoded to look back 7 days. It would be great for that interval to be customizable in the system preference. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23295 [Bug 23295] Automatically debar patrons if SMS or email notice fail -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 23295] New: Automatically debar patrons if SMS or email notice fail
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23295 Bug ID: 23295 Summary: Automatically debar patrons if SMS or email notice fail Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org When the sending of an SMS (or email) notice fails at the Koha level (i.e. before it is passed to the SMS API) then librarians should have the ability to enable automatic restriction (debarment) of patrons prompting them to update their smsalertnumber (or email address) in their library accounts. Adding this ability will tie in nicely with the functionality implemented in bug 13552 and bug 23291. As the enhancement for this bug report would let us restrict when notices failed at the Koha level, whereas 13552 and 23291 would let librarians restrict when notices failed at the SMS API level in batch restriction jobs retrieving patrons by SMS numbers in the SMS gateway report libraries get telling them which notices failed at the SMS API level. So all three enhancements together will mean there will be end-to-end functionality to restrict patrons when SMS notices fail, thereby prompting them to update their smsalertnumber. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 71

[Bug 31744] New: Inventory tool can take a long time and never complete
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31744 Bug ID: 31744 Summary: Inventory tool can take a long time and never complete Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There seems to be a problem with scaling for the inventory tool. More and more often now with bigger libraries we are running into libraries putting too many barcodes into the tool, and timing out the tool, or not getting feedback on the job progress and clicking back and trying again (and again. And again.), eventually causing a denial of service as they tie up all of their plack workers with inventory jobs. Potentially we could put the processing part into the background jobs or work on the performance here some other way so that larger batches could be accommodated? The servers weren't underpowered for this - the libraries were putting in collection-size-appropriate numbers of barcodes. Open to any kind of solution here that would help make this tool more usable for libraries. Cheers, Liz -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 26907] New: Fix POD for C4::Auth::checkauth
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26907 Bug ID: 26907 Summary: Fix POD for C4::Auth::checkauth Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Multiple problems here: - There are several "private" subroutines (starting with underscore) between the POD and the actual checkauth subroutine, so if you search for "sub checkauth" you might miss that the POD is actually there (I did). - The example of how to use the sub is: ($userid, $cookie, $sessionID) = &checkauth($query, $noauth, $flagsrequired, $type); but the sub is actually looking for more possible arguments: 793 my $authnotrequired = shift; 794 my $flagsrequired = shift; 795 my $type = shift; 796 my $emailaddress = shift; 797 my $template_name = shift; - The POD says "The login page is provided using a HTML::Template". As far as I know that would now be TT, HTML::Template. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1