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

[Bug 38159] New: Add count to Today's checkouts/Previous checkouts
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38159 Bug ID: 38159 Summary: Add count to Today's checkouts/Previous checkouts 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the issues table checkouts are separated by today's checkouts and previous checkouts. Some libraris would find it handy if this included a count of the number of checks in each. ie: Today's checkouts (2) Previous checkouts (1) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 39595] New: Allow membership_expiry.pl to limit based on patron attribute
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39595 Bug ID: 39595 Summary: Allow membership_expiry.pl to limit based on patron attribute 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 The membership_expiry cron can take a "WHERE" value to check against the borrowers table in order to limit who gets renewed/notified (like "where categorycode != 'STAFF'"). It'd be helpful to have a way to check a patron attribute here, too. Maybe we could add options to the cron for "-attribute_code" and "-attribute_value" to limit only to patrons who have an attribute that matches the code and value? This is technically possible with the current WHERE implementation: -where 'me.borrowernumber in (select borrowernumber from borrower_attributes where code="show_bcode" and attribute=1)' But making is an explicit option would be more clear. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 36064] New: Add Holds with cancellation requests info to intranet-main page
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36064 Bug ID: 36064 Summary: Add Holds with cancellation requests info to intranet-main page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some librarians would like to see notice/warning on the staff interface main page if there are holds with cancellation requests. Like Bug 36063 but for holds with cancellation requests. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 39594] New: fix_invalid_dates.pl missing a --help switch
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39594 Bug ID: 39594 Summary: fix_invalid_dates.pl missing a --help switch Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11361] Add a Z39.50 search page in the OPAC to let members search for records on remote Koha instances
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11361 --- Comment #35 from Sarah Cornell <sbcornell(a)cityofportsmouth.com> --- Created attachment 180745 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=180745&action=e… results screen with "more results in..." -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11361] Add a Z39.50 search page in the OPAC to let members search for records on remote Koha instances
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11361 --- Comment #34 from Sarah Cornell <sbcornell(a)cityofportsmouth.com> --- Sure, that's pretty close to what I'm thinking. We are in an area where libraries are independent of each other (enthusiastically so) but are geographically nearby and all use Koha. We have an existing state program for ILL handled through a different interface, but we may lose that due to funding cuts. Our libraries aren't interested in merging, and probably won't even be able to form a consortium or a true shared catalog. I hope this bug would make it possible for patrons to search a neighboring library's catalog without going to a special search screen. There are two ways I see this working: an additional entry in the "more searches" menu (to the right on opac-detail.pl, controlled by syspref OPACSearchForTitleIn) or something in that same right-hand column that says "look for this item nearby" and it searches for that ISBN in a set list of z39.50 targets. (See "details..." screenshot) The second way would be similar to the way that the Overdrive API works, where it takes the terms from a search and submits it to a set list of z39.50 targets. (see "results..." screenshot) If I remember correctly the ILL module can allow patrons to place a request that searches z39.50 targets, but I want patrons to just get the results before they place an ILL request. Let me know if that's not helpful! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11361] Add a Z39.50 search page in the OPAC to let members search for records on remote Koha instances
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11361 --- Comment #33 from Sarah Cornell <sbcornell(a)cityofportsmouth.com> --- Created attachment 180744 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=180744&action=e… details screen with "more searches" -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39552] New: Add a hook/plugin to Elasticsearch indexing to modify record
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39552 Bug ID: 39552 Summary: Add a hook/plugin to Elasticsearch indexing to modify record 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 As discussed at the Koha Hackfest 2025: Sometimes we need conditional indexing of fields (008 based on leader, 264 based on indicator). Instead of complicating the yml file and the DB, we can add a hook after the ES record has been created but before it is sent to ES. This hook should get the ES record and the MARC record (and maybe even the biblio/auth object) and return the modified ES record. So you can implement whatever weird conditionals etc you need, or even any other modifications (eg getting number of items, advanced geo stuff, ..) without us having to make core very complex. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 38759] New: koha-mysql doesn't work with timezone set in koha-conf.xml
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38759 Bug ID: 38759 Summary: koha-mysql doesn't work with timezone set in koha-conf.xml Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor 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 a timezone is set in the koha-conf.xml file, the koha-mysql command doesn't work. This seems to be due to missing quotes around the timezone value. For the timezone configuration see: https://wiki.koha-community.org/wiki/Time_Zone_Configuration If you dump the created connection command, you will see something like: mysql --host=<host> --user=XXX --password=XXX --init-command=SET time_zone='America/Sao_Paulo' koha_XXX This will result in an error. Quoting the value for the init-command parameter appears to fix the issue: mysql --host=<host> --user=XXX --password=XXX --init-command="SET time_zone='America/Sao_Paulo'" koha_XXX -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 37702] New: Fast Cataloging does not work with fast_cataloging permission when duplicate suspected
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '25

09 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37702 Bug ID: 37702 Summary: Fast Cataloging does not work with fast_cataloging permission when duplicate suspected 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: holly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Fast cataloging should work seamlessly with the patron permission fast_cataloging, and has in the past. This is no longer working in 23.05, 23.11 and 24.05. To replicate: -Set a user with no cataloging permissions except fast_cataloging. -Log in as that user. -Attempt a checkout with some nonsense barcode. -Follow prompt to add record via fast cataloging. -Fill out fast add MARC with a title that already exists in catalog and save. -Koha will ask if this is a duplicate *Select yes, edit existing items: you are taken to the normal view of the record and cannot add items. *Select no, save as new record: Instead of this directing into item creation, you are directed to the normal view of the record you just created. You can add an item from New or Edit. -If no duplicate suspected, saving the record does direct to the item creation screen as expected, and then you run into bug 37407, which has been fixed for upcoming versions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7