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

[Bug 21976] New: koha-reset-passwd must call Koha::AuthUtils::generate_password to deal with password restrictions
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21976 Bug ID: 21976 Summary: koha-reset-passwd must call Koha::AuthUtils::generate_password to deal with password restrictions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 18298 Like minPasswordLength and RequireStrongPassword Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18298 [Bug 18298] Allow enforcing password complexity -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 32306] New: Hold modifications don't log correctly
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32306 Bug ID: 32306 Summary: Hold modifications don't log correctly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org When one modifies holds from records holds page, these changes don't log into action_logs table correctly. Instead holds data before modifications is stored to action_logs. To test: 1. Find hold to modify. 2. If possible, locate this hold from action_logs table: SELECT * FROM action_logs WHERE module = "HOLDS" AND object = <reserve_id>; 3. Modify hold, change its pickup library from A to B. 4. Save changes. 5. Take a look at action_logs table. => Modification is saved, but holds pickup library is still A. 6. Modify hold again, e.g add expiration date. 7. Save. => Expiration date is empty, but pickup library is now B. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 31610] New: When creating a guarantee, patron messaging preferences should be copied to this account from the category
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '25

07 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31610 Bug ID: 31610 Summary: When creating a guarantee, patron messaging preferences should be copied to this account from the category Change sponsored?: --- Product: Koha Version: unspecified 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 When creating a guarantee, patron messaging preferences should be copied to this account from the category. Steps: Have a guarantor. Create a guarantee. Koha will use the CHILD patron category to assign this guarantee, but will not copy over the message preferences from this CHILD patron category. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 25936] New: Notify users if their password has changed
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25936 Bug ID: 25936 Summary: Notify users if their password has changed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We should email/SMS users if their password has changed. We shouldn't include any information about the old or new password, but just alert them that it has been changed. This is useful in the event that someone has compromised an account and changed the password. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 36990] New: Move MarcEdit tutorials out of the manual, into the wiki
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36990 Bug ID: 36990 Summary: Move MarcEdit tutorials out of the manual, into the wiki Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In one of the docs meeting (april 2024?), we decided that the Koha manual should be used to describe how to use Koha, and not how to use other software. Integration examples should be in the Koha wiki. As the MarcEdit section at the end of the cataloging chapter (https://koha-community.org/manual/latest/en/html/cataloging.html#handling-o…) not only describes how to use another software, it is also possible wildly out of date >This tutorial was written with MARCEdit version 5.2.3769.41641 on Windows XP, instructions may be different if your version or operating system is different. MarcEdit is now at version 7 and Windows is... 11? (sorry, I don't use windows or follow its development) This should be moved to the wiki as an example of MarcEdit use with Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 38979] New: Standardize word spacing for Cardnumber and Borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38979 Bug ID: 38979 Summary: Standardize word spacing for Cardnumber and Borrowernumber Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org A discerning librarian of mine pointed out that the moremember.pl page shows "Card number" and "Borrowernumber". They asked for a space to be added to make the latter "Borrower number", which honestly makes a lot of sense. While I think that's a good starting point, I figured I'd raise this issue to cover all the different instances for both. $ grep -R "Card number" koha-tmpl/* | wc -l 36 $ grep -R "Cardnumber" koha-tmpl/* | wc -l 7 $ grep -R "Borrowernumber" koha-tmpl/* | wc -l 11 $ grep -R "Borrower number" koha-tmpl/* | wc -l 1 Chances are that there are more instances with lower cased initial letters, but cardnumber and borrowernumber are valid in links... It would probably be wise to add a coding guideline for this as well. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 26869] New: Create items across batch of bibs
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26869 Bug ID: 26869 Summary: Create items across batch of bibs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Say I have a couple thousand records for eBooks. I imported them without adding items, but decided later that I'd like to have items to ease searching. I'd love to be able to add those to my bibs in a batch without exporting and re-importing them. I'm imagining an interface like additem.pl except items I define would be created across all the bibs I've indicated. Ideally, there'd be some mechanism for values like itype and call number to choose whether you want Koha to apply a static value for all the items or derive specific values from the bibs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 87

[Bug 38356] New: CheckPrevCheckout should also check current loans
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38356 Bug ID: 38356 Summary: CheckPrevCheckout should also check current loans 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: tuomas.kunttu(a)kouvola.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At this moment, with the system preference CheckPrevCheckout, Koha will look at the patron’s circulation history to see if they have checked this item out before. It would be helpful if Koha could also check the customer’s current loans and provide a notification if attempting to lend a book that the customer already has on loan. Of course, this need wouldn’t exist if the AllowMultipleIssuesOnABiblio setting were set to 'don’t allow,' but there are other requirements that necessitate keeping it as 'allow'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 38891] New: MARC21 Addition to relator terms in technical notice 2024-10-17
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38891 Bug ID: 38891 Summary: MARC21 Addition to relator terms in technical notice 2024-10-17 Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org https://loc.gov/marc/relators/tn241017rel.html MARC Code List for Relators The following relator has been added to the MARC Code List for Relators list for usage in appropriate fields and elements. Addition: tad [technical advisor] - A person with expertise in a particular field who advises on the convincing portrayal of a subject to add authenticity to a work. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 36431] New: SIP2: Checkin does not show difference between WasTransfered and NeedsTransfer
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36431 Bug ID: 36431 Summary: SIP2: Checkin does not show difference between WasTransfered and NeedsTransfer Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org If you enable AutomaticItemReturn, SIP will trigger an eventual transfer to home branch when checking in. If disabled, it will not but the station receives an alert to notify the user. But the SIP response for both cases is actually the same. The code shows this: if ($messages->{NeedsTransfer}) { $self->{item}->destination_loc($messages->{NeedsTransfer}); $self->alert_type('04'); # send to other branch } if ($messages->{WasTransfered}) { # set into transit so tell unit $self->{item}->destination_loc($item->homebranch); $self->alert_type('04'); # send to other branch } The destination location will be the same in both cases. And the alert number is the same too. How could the SIP station 'know' that the transfer is done already or still needs to? Both SIP responses contains AO holding branch, AQ destination, CT destination and CV 04. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28