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

[Bug 39308] New: No space between preffered name and middle name in some places
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39308 Bug ID: 39308 Summary: No space between preffered name and middle name in some places Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons 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 To recreate: 1. Find a patron with a middle name. 2. ON the checkout page or details page notice it displays like this: 'EdnaMiddleName Acosta' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[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 39141] New: Page is blank when visiting Circulation Check In
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39141 Bug ID: 39141 Summary: Page is blank when visiting Circulation Check In Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com >From Koha home click 'Circulation' then 'Check out' You are on a page with a header search, but no content, this can be odd For contrast: 'Circulation' -> 'Check in' You have a form in the page to return items -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[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 39550] New: RestrictPatronsWithFailedNotices system preference should not be in Patron relationships section
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39550 Bug ID: 39550 Summary: RestrictPatronsWithFailedNotices system preference should not be in Patron relationships section Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I was going to document bug 23295, and noticed the new system preference is under the Patron relationships section. I feel like that's not the right place for it. But there doesn't seem to be a fitting section for it either. Here are some options I thought about 1. Create a "Patron restrictions" section - either with only this one, or we could move a couple of other ones too like useDischarge 2. Place the pref under "General" 2. Place under "Notices and notifications" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 39857] New: OAI expanded_avs option broken
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39857 Bug ID: 39857 Summary: OAI expanded_avs option broken Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 31224 moved OAI to use metadata_record - when doing so the param to expand fields was incorrectly added as: expand_coded_values => $expanded_avs, It should be: expand_coded_fields => $expanded_avs, -- You are receiving this mail because: You are watching all bug changes.

1 22

[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

[Bug 37273] New: Add ID column to Agreements table in the ERM
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37273 Bug ID: 37273 Summary: Add ID column to Agreements table in the ERM Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Created attachment 168606 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=168606&action=e… ERM ID number appended to agreement name When creating an Agreement or License in the ERM, an ID number is added to the agreement or license name. If it is necessary for the ID number to be visible, it should be in a separate column from the name. Having the ID number appended to the name is a little confusing (see example image). Another option is to hide the hide ID number if it is not needed. -- You are receiving this mail because: You are watching all bug changes.

1 34