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

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 --- Comment #20 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Michael Hafen from comment #19) > I'm inclined to say, since BugZilla has been changed, it might be better to > revert/push. I don't see a way to un-obsolete patches here. un-obsoleting can be done from the GUI, just not with git bz - do you want me to do it so you can take a look? But both options are fine for me, we just need to resolve. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 --- Comment #19 from Michael Hafen <michael.hafen(a)washk12.org> --- I'm inclined to say, since BugZilla has been changed, it might be better to revert/push. I don't see a way to un-obsolete patches here. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 --- Comment #18 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- A note for Monday... I forgot to remove the patches from my branch before pushing and now we can either revert/push this or we could do a follow-up with the renaming. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 Michael Hafen <michael.hafen(a)washk12.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 Michael Hafen <michael.hafen(a)washk12.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #169405|0 |1 is obsolete| | Attachment #169406|0 |1 is obsolete| | Attachment #169407|0 |1 is obsolete| | --- Comment #17 from Michael Hafen <michael.hafen(a)washk12.org> --- Created attachment 170213 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=170213&action=e… Bug 9596: Add library and skip-library options to cronjobs/longoverdue.pl [rebase to 2024-08-05 and change cli option from --branch to --library for QA] [ I hope it's ok that I squashed it ] This script doesn't seem to be included in cron files by default. This change is to allow script parameters to effect only certain libraries. This allows the script to be added multiple times to a cron file with different settings for different libraries. Test plan: 1. apply patch 2. identify two books at different libraries the same number of days overdue. 3. run the longoverdue.pl script specifying one of the libraries in the --library command line parameter. i.e. koha-shell -c 'misc/cronjobs/longoverdue.pl --library branch_code --lost 60=2 --maxdays=61 --confirm' instance_name 4. observe that the book at the specified library has been or would be affected by the script while the other book is not. Bug 9596: (QA follow-up) Add some clarifying comments Bug 9596: (QA follow-up) Only find a given patron once -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9596] Allow longoverdue.pl to be configured per library on the command line
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Failed QA --- Comment #16 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Can we please switch from branch to library for the new options and in documentation, etc. please? We are trying to match the language in the GUI whenever possible to create more consistency. See: https://wiki.koha-community.org/wiki/Terminology I know it feels nit-picky, but if we don't do it now, it will cause much more trouble if we wanted to do it later once libraries are using these parameters. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37609] New: Item type code of 0 causes cascade of failure
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37609 Bug ID: 37609 Summary: Item type code of 0 causes cascade of failure Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The general rule of thumb when creating item type codes is all capital letters, no spaces, no special characters. This implies that alpha numeric characters will work, including the number 0. However if an item type is created with a code of 0, it will cause various failures. I am assuming Koha is reading the number 0 as null or blank. If the number 0 cannot be used, documentation should include both best practices but also what should not be used like the number 0. These are the failures I made note of: 1. An item can't be saved with the 0 item type in the 952$y or the 942$c, which also prevents circulation. 2. If a circulation rule is created with the 0 item type, the rule can't be deleted. Deleting the 0 item type is the only way to remove the circulation rule. I did some additional testing where I changed the Item Type code to '0A' and 'A0' and had similar results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 14697] Extend and enhance "Claims returned" lost status
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|24097 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24097 [Bug 24097] Don't show claims tab in patron account, when there are no claims -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37608] New: Add a default circulation rule that considers total checkouts and holds combined
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37608 Bug ID: 37608 Summary: Add a default circulation rule that considers total checkouts and holds combined 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: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A library is interested in a default circulation rule that considers total checkouts and holds combined. In other words a patron would only be allowed to have an X number of checkouts and holds combined. Right now these items are considered individually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 36974] New: Sort summary-print by ascending due date
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36974 Bug ID: 36974 Summary: Sort summary-print by ascending due date Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello, This is a small correction, but the summary-print.pl sort by descending due date... it would be preferable to sort it in ascending order to obtain the earliest due date on the first line. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11