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

[Bug 31424] New: Prompt to change patron messaging if email/SMS absent or changed
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31424 Bug ID: 31424 Summary: Prompt to change patron messaging if email/SMS absent or changed 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: arm(a)hanover.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Suggesting a prompt to staff or patron to update the messaging preferences if a new member is registered with no email/SMS number and the messaging prefs default to 'on', or if an existing user account is edited and the SMS or email contact info is changed. The lack of this reminder leaves many accounts with failed/unsent messages or pending 'print' messages. Also when an email address is added, notices are not sent because staff/patron may not turn on messaging preferences. There are a couple of old bugs about SMS / failed email. This might help with those. Related: 14964 23497 14590 14872 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19098] New: Additional logic for 260/RDA 264 fields
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19098 Bug ID: 19098 Summary: Additional logic for 260/RDA 264 fields 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If we have implemented 10306 and 19096, we can add some additional logic for multiple RDA 264 fields. Making e.g. the place and year picked more accurate than just glueing together or picking the first one. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 23124] New: trailing spaces in DefaultPatronSearchFields can break patron searching
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23124 Bug ID: 23124 Summary: trailing spaces in DefaultPatronSearchFields can break patron searching Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration 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 Target Milestone: --- We should probably just trim this string on save? To recreate: 1 - Add a trailing space to DefaultPatronSearchFields 2 - Attempt to search for patrons 3 - Error! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 21106] New: oai.pl XML output doesn't validate against OAI-PMH XML schema
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21106 Bug ID: 21106 Summary: oai.pl XML output doesn't validate against OAI-PMH XML schema Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 21102 When using some verbs Koha return a well formed but in invalid XML. CLI test: wget -q "https://www.openarchives.org/OAI/2.0/OAI-PMH.xsd" wget -q "https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=ListSets" -O test.xml xmllint --noout --schema OAI-PMH.xsd test.xml Web test: An online way to test this is with http://validator.oaipmh.com/ 1. verb=ListSets: When no set is defined Koha incorrectly output <ListSets/>. A set (child element of ListSets) should always be there, minOccurs default value is 1. Otherwhise should be: <error code="noSetHierarchy">No sets defined</error>, AFAIK even if tehere is no error. 2. verb=Identify: setDescription is not a string, is descriptionType ##other, "defined by a community" (?) See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17785#c13 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21102 [Bug 21102] OAI-PMH specification conformance [UMBRELLA] -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24407] New: AuthDisplayHierarchies ignores new nodes and needs protection against cyclic relations
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24407 Bug ID: 24407 Summary: AuthDisplayHierarchies ignores new nodes and needs protection against cyclic relations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Suppose I have term A with children B and C where the children have a 550 tag with broader indication to A. If I go to record A, the tree is built showing B and C. If I add a child D to A, the tree for A is not rebuilt but still showing the old situation. A related problem: If I change term A setting it to a be child of B with a 550 (which it obviously not is), this cyclic relation will trigger deep recursion. Resulting in a gateway timeout and a process eating up resources.. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 31794] New: REST API: GET endpoint for Authorities
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '23

15 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31794 Bug ID: 31794 Summary: REST API: GET endpoint for Authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 34413] New: Flat picker birth date field does not display properly on initial load on iOS
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34413 Bug ID: 34413 Summary: Flat picker birth date field does not display properly on initial load on iOS 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you are using iOS (iPhone for my test), and create a new patron, the birth date field does not show. there is a squishy blob in it's place. Click on that, and the flatpicker comes up and you can enter the date. Everything from that point forward looks fine. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 24480] New: Fields added with Marc modifications templates are not added in an ordered way
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24480 Bug ID: 24480 Summary: Fields added with Marc modifications templates are not added in an ordered way Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org they are instead appended to the end of the record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 33164] New: Return claim message shows intermittently when BlockReturnOfLostItems enabled
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33164 Bug ID: 33164 Summary: Return claim message shows intermittently when BlockReturnOfLostItems enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1. Set BlockReturnOfLostItems system preference to Block 2. Check out an item to a patron 3. Go to the patrons page and claim a return on the item 4. Check in the item and keep checking in the item. Notice the message "Item is lost, cannot be checked in." shows every time, but the return claim message only shows sometimes. This is because BlockReturnOfLostItems interrupts the return process and may prevent the return claim message from coming through. This is a problem since this message is the only way to resolve a return claim, and the message may not show when the item is returned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 34375] New: Shipping fund in an invoice defaults to the first fund from the list rather than 'no fund' after receiving.
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34375 Bug ID: 34375 Summary: Shipping fund in an invoice defaults to the first fund from the list rather than 'no fund' after receiving. Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org To recreate: Go to a vendor record in Acquisitions and then Receive Shipment Enter an invoice number Leave the Shipping cost empty and Shipping Fund as 'No fund' Receive some orders or go straight to Finish receiving Notice the Shipping fund has defaulted to the first fund in the alphabetical list of funds. It is not possible to select 'No fund' and the selected fund is recorded in shipmentcost_budgetid incorrectly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23