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

[Bug 20860] New: List last e-mail address/SMS number/carrier sent to
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20860 Bug ID: 20860 Summary: List last e-mail address/SMS number/carrier sent to Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be helpful if the notifications listed the last e-mail address or SMS number and carrier that each notice was sent to. That way we know if the information was changed before/after the last failure. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 29292] New: Notices does not record what address or number was used
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29292 Bug ID: 29292 Summary: Notices does not record what address or number was used 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be great if we could see what e-mail address or phone number or sms number, or mailing address was used to send a notice on the last attempt. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30286] New: Notices.pl does not show what number or e-mail it used
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30286 Bug ID: 30286 Summary: Notices.pl does not show what number or e-mail it used Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be helpful to see what number or address was used when a notice was last sent (or failed) in notices.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20868] New: Making billing date mandatory when closing invoice
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20868 Bug ID: 20868 Summary: Making billing date mandatory when closing invoice Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: information(a)newcastle.gov.uk QA Contact: testopia(a)bugs.koha-community.org Would it be possible to make the billing date a mandatory field before you close an invoice for payment? Thanks -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20901] New: Koha/Patrons/Import.t fails on fresh database
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20901 Bug ID: 20901 Summary: Koha/Patrons/Import.t fails on fresh database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org t/db_dependent/Koha/Patrons/Import.t # Looks like you failed 58 tests of 124. Fresh install, no optional stuff -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 20908] New: Print receipts need clean up
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20908 Bug ID: 20908 Summary: Print receipts need clean up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org During work on bug 20903, I realize the need of clean up of print receipts scripts and templates... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20932] New: Add multiple items should have a maximum number to be able to add at a time
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20932 Bug ID: 20932 Summary: Add multiple items should have a maximum number to be able to add at a time Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: nick(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Currently, when adding items to an existing record- the option is to add item, duplicate or add multiple items. When the option is chosen for adding multiple items, there is a box displayed that a quantity can be entered. If the number is large (above 100) there is a pop-up message confirming this many. In addition to the pop-up, it would be helpful for a system preference to set a maximum number for this feature -as it is with Batch Item Modification / Batch Item Deletion. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 34146] New: How to limit number of copies?
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34146 Bug ID: 34146 Summary: How to limit number of copies? Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: vbovictor(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In Koha it is possible to Add an instance or choose to "Add Multiple Copies" simultaneously to a record. So far so good. More..... I had a situation where an employee mistakenly typed 800,000 copies for a record. As a result, when Koha started its automatic Indexing routine, it consumed all of the server's memory and crashed system access. When I tried to delete the 800,000 copies in batch, the system crashed. It took slow deletion from 5,000 to 5,000 to reach 800,000. Considering the aforementioned case, would any colleague know if we can limit the quantity in the option "Add Multiple Copies"? If there is no option, I believe that a configuration option to limit the entry of copies is important. Thanks, Victor -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 20938] New: Resetting patrons password would resend patron patron detail email
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20938 Bug ID: 20938 Summary: Resetting patrons password would resend patron patron detail email Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, staff can reset a patron's password in Koha. However, it would be nice to have Koha send an email with this password/patron details (as it does when registering a new patron) to the patron instead of having the staff write down and/or tell the patron the password. Due to security it would be nice if this was done without staff interaction with the actual password. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20961] New: cn_sort for DDC callnumbers should between 1 and 99 should be formatted as 001.* - 099.*
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20961 Bug ID: 20961 Summary: cn_sort for DDC callnumbers should between 1 and 99 should be formatted as 001.* - 099.* Change sponsored?: --- Product: Koha Version: master 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The documentation for C4::ClassSortRoutine::GetClassSortKey says * Concatenates class and item part. * Converts to uppercase. * Removes leading and trailing whitespace and '/' * Separates alphabetic prefix from the rest of the call number * Splits into tokens on whitespaces and periods. * Leaves first digit group as is. ... 9.1 => 9_100000000000000 80.1 => 80_100000000000000 700.1 => 700_100000000000000 when sorted ascending by cn_sort are 700.1 => 700_100000000000000 80.1 => 80_100000000000000 9.1 => 9_100000000000000 however, DDC classes are formatted 000 – Computer science, information & general works 100 – Philosophy and psychology 200 – Religion 300 – Social sciences 400 – Language 500 – Pure Science 600 – Technology 700 – Arts & recreation 800 – Literature 900 – History & geography 000 is sub-divided into the hundreds group 000 Computer science, knowledge & systems 010 Bibliographies 020 Library & information sciences ... and sub-sub-divided into the thousands groups... 000 Computer science, information & general works 001 Knowledge 002 The book 003 Systems ... As such, '* Leaves first digit group as is.', should read * the first digit group should be 3 characters wide, 0-padded I.e. the value of cn_sort for callnumber 1.1 should be 001_100000000000000, so that the examples above sort 009_100000000000000 080_100000000000000 700_100000000000000 See discussion here: http://lists.koha-community.org/pipermail/koha-devel/2018-June/044623.html And the summary of DDC 23 here: https://www.oclc.org/content/dam/oclc/dewey/DDC%2023_Summaries.pdf -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3