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

[Bug 33997] New: Borrowers.updated_on should not be updated by track_login
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33997 Bug ID: 33997 Summary: Borrowers.updated_on should not be updated by track_login Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently borrowers.updated_on is updated by track_login even though a login is not an update to the patron record. This update needs to be blocked so that the updated_on field accurately reflects updates to the patron. Logins are supposed to be tracked by borrowers.lastseen which track_login already does. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 38902] New: Allow holds fine limit (maxoutstanding) to be determined by patron category
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38902 Bug ID: 38902 Summary: Allow holds fine limit (maxoutstanding) to be determined by patron category Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: raina(a)flo.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The system preference “maxoutstanding” is used to determine when patrons are blocked from making holds in the OPAC. For example, maxoutstanding: Prevent patrons from making holds on the OPAC if they owe more than 5 USD in fines. This is separate from the checkout fine limit (noissuescharge). Currently the maxoutstanding preference is applied to all patrons, and there's no way of changing the value for individual patron categories. Bug 28924 enables checkout fine limit to be set by patron category, but there's no way of changing the value for "maxoutstanding" by patron category, which means that all patron groups will still be blocked from placing holds in the OPAC at the same amount. It would be helpful to be able to determine when patrons should be blocked from making holds in the OPAC by patron category, like bug 28924 does for the checkout fine limit. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 38755] New: search_for_data_inconsistencies.pl: Fix list of inconsistencies
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38755 Bug ID: 38755 Summary: search_for_data_inconsistencies.pl: Fix list of inconsistencies Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The relevant POD looks like this: ----------------------------------------------------- =head1 DESCRIPTION Catch data inconsistencies in Koha database * Items with undefined homebranch and/or holdingbranch * Authorities with undefined authtypecodes/authority types * Item types: * if item types are defined at item level (item-level_itypes=specific item), then items.itype must be set else biblioitems.itemtype must be set * Item types defined in items or biblioitems must be defined in the itemtypes table * Invalid MARCXML in bibliographic records * Patrons with invalid category types due to lower and upper age limits * Any date fields in the database (timestamp, datetime, date) set to 0000-00-00 =cut ----------------------------------------------------- perldoc renders the list as running text, which is kind of hard to read. The list should either be formatted with "=item" or indented to be treated as "pre formatted" chunk of text. I would vote for the first option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 31791] New: Add the ability to lock records to prevent modification through the Koha staff interface(s).
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31791 Bug ID: 31791 Summary: Add the ability to lock records to prevent modification through the Koha staff interface(s). Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl - Add a read-only field - The read-only field will only be editable by superlibrarian - Koha can update these internally for related routines -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 124

[Bug 20418] New: Remove UpdateTotalIssuesOnCirc and make it cron everywhere
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20418 Bug ID: 20418 Summary: Remove UpdateTotalIssuesOnCirc and make it cron everywhere Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I guess the reason this system preference exists it that if you do a lot of circulation, updating this live could have an impact on your server load. But we could make it cron for everyone, it would always work and wouldn't require choices to be made and setup to be done. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 24534] New: Selection Options for Importing Staged MARC Records
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24534 Bug ID: 24534 Summary: Selection Options for Importing Staged MARC Records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be great to have a selection option in the Staged MARD Management tool that allowed you to choose which bibliographic records get imported into the system. Right now the only option is to import all records. Sometimes librarians get records from vendors where the record may have errors or not be complete. It would be great to have an option to select the records you want to import on /koha/tools/manage-marc-import.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 18064] New: Long overdue cronjob does not follow the library' s calendar and skip closed days
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18064 Bug ID: 18064 Summary: Long overdue cronjob does not follow the library's calendar and skip closed days Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The cronjob that sets the Long overdue does not follow the library's calendar and skip closed days. However, the cronjob that sends the email (overdue notices) does follow the library's calendar. So as an example on a weekend where Monday is a holiday, the long over due may get set and chanrge the patrons account, but the email may be sent a day or 2 later. It would be good to allow the long overdue cron to follow the library calendar and skip closed days. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 82

[Bug 38605] New: t/db_dependent/Koha/OAIHarvester.t fails with wrong date format
by bugzilla-daemon＠bugs.koha-community.org 14 May '26

14 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38605 Bug ID: 38605 Summary: t/db_dependent/Koha/OAIHarvester.t fails with wrong date format Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 35659 It looks like the test started failing, because we now are in the "one digit" days of a month. I assume this could be a one character change? prove -v t/db_dependent/Koha/OAIHarvester.t t/db_dependent/Koha/OAIHarvester.t .. 1..28 The given date (2024-12-2) does not match the date format (iso) at /kohadevbox/koha/Koha/DateUtils.pm line 188. # Looks like your test exited with 11 before it could output anything. Dubious, test returned 11 (wstat 2816, 0xb00) Failed 28/28 subtests Test Summary Report ------------------- t/db_dependent/Koha/OAIHarvester.t (Wstat: 2816 (exited 11) Tests: 0 Failed: 0) Non-zero exit status: 11 Parse errors: Bad plan. You planned 28 tests but ran 0. Files=1, Tests=0, 2 wallclock secs ( 0.02 usr 0.00 sys + 1.34 cusr 0.12 csys = 1.48 CPU) Result: FAIL Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35659 [Bug 35659] OAI harvester -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 17015] New: New Koha Calendar
by bugzilla-daemon＠bugs.koha-community.org 14 May '26

14 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17015 Bug ID: 17015 Summary: New Koha Calendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: mehdi.hamidi(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org We are trying to create a new Koha calendar system. The one available right now is way too slow. This is the first patch of the calendar, it doesn't affect the functioning of the current calendar, but it works in parallel with it. Instead of having multiple tables for the holidays, we created one table, called discrete_calendar. This table contains the dates,branchcode, opening/closing hours, a note about the holiday and whether the library is open or not. The script misc/generate_discrete_calendar.pl fills the table discrete_calendar based on tables : repeatable_holidays, special_holidays, openinghours and branches. The script, by default, will add 2 years from the past and 1 year in the future in the table discrete_calendar. It also has an option to added more than 1 year in the future. The script misc/cronjobs/add_days_discrete_calendar.pl will add days in the future in the table discrete calendar. A day's opening and closing hours will be based on the same weekday from the week before. It will also check if the same day from last year was a holiday, if so, this will be counted as a holiday. The script makes sur there's at least 1 year in the future. So if it hasn't ran for 8 days, 8 days will be added in he future the next time the script is executed. There's also an atomic update to create the table. The current options are not final and they can be changed for convenience. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 508

[Bug 35466] New: bulkmarcimport needs a parameter to skip indexing
by bugzilla-daemon＠bugs.koha-community.org 14 May '26

14 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35466 Bug ID: 35466 Summary: bulkmarcimport needs a parameter to skip indexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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: jonathan.druart+koha(a)gmail.com, michaela.sieber(a)kit.edu, robin(a)catalyst.net.nz When using bulkmarcimport for migrations it does make sense to do a full reindex after finishing the import. At the moment the import will always create entries in background_jobs for Elasticsearch and in zebra_queue for Zebra. We should have a switch to turn this off if indexing is not required to increase performance and avoid unnecessary load. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32