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

[Bug 28743] New: With IndependentBranches block changes to biblio records shared with other libraries
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '23

08 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28743 Bug ID: 28743 Summary: With IndependentBranches block changes to biblio records shared with other libraries 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: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 28323] New: Invalid record in sample data leading to error when displaying
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '23

08 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28323 Bug ID: 28323 Summary: Invalid record in sample data leading to error when displaying Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org Strk̆v̜elser illustreret af Jean Anderson dansk udgave ved Lis Engel [overst̆telse ved Jesper Langer] staff://cgi-bin/koha/catalogue/detail.pl?biblionumber=369 opac://cgi-bin/koha/opac-detail.pl?biblionumber=369 ========= error ============ Invalid data, cannot decode metadata object (biblio_metadata.id=368, biblionumber=369, format=marcxml, schema=MARC21, decoding_error=':8: parser error : PCDATA invalid Char value 31 <controlfield tag="001">00aD000015937</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :10: parser error : PCDATA invalid Char value 31 <controlfield tag="008">00ar19881981bdkldan</controlfield> ^ :10: parser error : PCDATA invalid Char value 31 <controlfield tag="008">00ar19881981bdkldan</controlfield> ^ :10: parser error : PCDATA invalid Char value 31 <controlfield tag="008">00ar19881981bdkldan</controlfield> ============ Here is some analysis by Caroline ============ I can't find the exact problem with record 369, but it's definitely problematic, even MarcEdit won't open it I can view it with a command line tool that I have Problem record : https://snipboard.io/paTtIK.jpg the error messages seem to point to the control fields 001, 004 (which doesn't exist in MARC21 afaik), and 008 Compared with a healthy record : https://snipboard.io/XFZ5VN.jpg In fact, there are a couple more fields in the problem record that dont exist in MARC21 : 021 (should probably be 020), 245$d (should probably be 245$c?), 245$f should be dates The fact that indicators are all 00 is also wierd... anywho, I think there is probably a character at the beginning of the record that is messing up everything else tuxayo: does this look like a legitimate record to have in sample data? Because real world data can be weird ^^ tuxayo: Or is this worthless and should be removed from sample data? caroline: I think it should be removed.... I mean it's just sample data and this one is clearly a problem Unless it was there for a specific purpose like you suggested it causes problem when searching for danish documents too :/ Advanced search > Language Danish > Search > Error ====== issue with search of Danish records ======= - OPAC - advanced search - Language dropdown => Dansk - search - error Actually it's just that it redirects to the record page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 34216] New: Error: Session timed out. Please log in again
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '23

08 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34216 Bug ID: 34216 Summary: Error: Session timed out. Please log in again Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: cnclibrarian(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 34236] New: Add an option to only display the items of some libraries in a list
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '23

08 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34236 Bug ID: 34236 Summary: Add an option to only display the items of some libraries in a list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depending of the organisation of a library network, it could be useful to display a list with all new books in some library, without displaying the items available in other liraries. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 29104] New: Add new columns to table_borrowers column configuration
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29104 Bug ID: 29104 Summary: Add new columns to table_borrowers column configuration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliwho(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The present options under columns_settings.pl for the table_borrowers table are name, cardnumber, date_of_birth, category, library, address, & phone. It would be helpful to have the dateexpiry column available for display as well. Others may have prefer additional columns as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 34231] New: Allow different input formats for monetary values
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34231 Bug ID: 34231 Summary: Allow different input formats for monetary values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, jonathan.druart+koha(a)gmail.com, michaela.sieber(a)kit.edu, tomascohen(a)gmail.com There are several bugs already about this, but after discussing with Joubu and Tomas today I think it deserves a fresh start. On bug 30718 Jonathan wrote: > "Show the user a readable date (as per altFormat), but return > something totally different to the server." > > It's actually an option we want to use for all our dates, that will > reduce a lot the overhead in our controllers. And we should use the same approach for dealing with monetary amounts in patrons/account and in the acquisition module. Using a client side solution we avoid having to touch the .pl scripts and it will also make it easier to work with the API. We'd have 2 input fields, one hidden, with the 'raw' data in the expected database format, and one visible input field for entering and displaying the 'formatted' data. When sending the data to the server, only the 'raw' data will be processed. To explain the need/use case: At the moment we don't have any validation on input fields in the acquisition module and that leads to input errors that can have dire consequences. 1,00 might be turned into 100 or 1000 or just end up as an empty field. We also only allow the 'US' format with decimal dot, but not the French/German format of decimal comma. This is also a usability issue as keyboard with German layout don't have a . in the number block, only a comma. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 --- Comment #40 from Sam Lau <samalau(a)gmail.com> --- I am still failing subtest 'safe_to_delete() tests'. The only thing that changed in that subtest was that you commented out this line: $patron->account->pay({ amount => 10, debits => [ $debit ] }); Uncommenting it made all tests successful for me -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8483] Borrower reading history should include deleted items
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8483 --- Comment #57 from Jonathan Druart <jonathan.druart+koha(a)gmail.com> --- If you were interested in this, can you help testing bug 33948 please? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 31997] New: Show club question answers in staff client
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31997 Bug ID: 31997 Summary: Show club question answers in staff client 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Similar to bug 25079. When creating a club template, one can set "club questions" to be asked as one creates a club. The answers to those questions are stored in the database and can be retrieved in a report, but are not otherwise shown in the staff interface. These values should be visible in the clubs list on plubs.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32505] New: Cannot search by dateofbirth in specified dateformat
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '23

07 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32505 Bug ID: 32505 Summary: Cannot search by dateofbirth in specified dateformat Change sponsored?: --- Product: Koha Version: master 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. Set DefaultPatronSearchFields to include dateofbirth 2. Set dateformat to something besides iso. I am using mm/dd/yyyy. 3. Set a patron to have a dateofbirth 4. Search for them in your specified dateformat. For me "04/24/1980". It doesn't return your patron. 5. Try ISO format, "1980-04-24". It works. We should be able to find patrons in a search based on the dateformat specified. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41