November 2024 - Koha-bugs - lists.koha-community.org

[Bug 36603] New: UNIMARC: automatically copy the ISNI number over when linking authorities with authorities
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36603 Bug ID: 36603 Summary: UNIMARC: automatically copy the ISNI number over when linking authorities with authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org The 2023 edition of the IFLA UNIMARC Authorities Format Manual [1] has the following to say about subfield $o of authority fields 500, 510 and 520 [2,3,4]: "$o International Standard Name Identifier (ISNI) The subfield $o (International Standard Name Identifier) is used in field 510 to record the ISNI of the related identity. When the preferred access point of an authority record that contains field 010 is transferred to the 500/510/520 access point of another record (while establishing a link between both authority records), the number contained in the 010 field of the first record will also be transferred in a devoted subfield $o. Repeatable." So, when linking authorities with other authorities in UNIMARC instances I think it would be a good idea if Koha automatically copied the contents of subfield 010$a [5] into the corresponding 5xx$o subfield (if such an ISNI number exists in the source record, of course). [1] https://repository.ifla.org/handle/123456789/3011 [2] 500 RELATED ACCESS POINT – PERSONAL NAME [3] 510 RELATED ACCESS POINT – CORPORATE BODY NAME [4] 520 RELATED ACCESS POINT – FAMILY NAME [5] 010 INTERNATIONAL STANDARD NAME IDENTIFIER (ISNI) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 37944] New: Object deletion should be logged with a JSON diff of changes, implement for items
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37944 Bug ID: 37944 Summary: Object deletion should be logged with a JSON diff of changes, implement for items Change sponsored?: --- Product: Koha Version: unspecified 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should store deleted objects as diffs just as we do for modification and item created. This enhancement will store modification diffs if the action is set to DELETE, and an "original" object is passed in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 32413] New: JSON reports shows inaccurate results with repeated parameters
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32413 Bug ID: 32413 Summary: JSON reports shows inaccurate results with repeated parameters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org If I create a report that uses a repeating parameter, for example <<library>>, more than once in a report, and then run a JSON call on that report, I get inaccurate results (Like every other result). Currently, the only workaround is to make each parameter unique, and then repeat the parameter over as many times as it is needed in the report. For example, https://mydomain.com/cgi-bin/koha/svc/report?id=938&sql_params=blah would only return half the results if the report because I use the same parameters 7 times int he sql. However, if I rename each parameter something different, like <<library1>>, <<library2>>,etc, and call https://mydomain.com/cgi-bin/koha/svc/report?id=938&sql_params=blah&sql_par…, it works. The JSON call needs to be updated to accept repeated parameters. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 37639] New: items.stack ( shelving control number ) not included in items API endpoint
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37639 Bug ID: 37639 Summary: items.stack ( shelving control number ) not included in items API endpoint Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com items.stack is not included at /api/v1/items/ I think it should be -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52

[Bug 7508] Collapsable items on items tab
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7508 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #10 from Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> --- Koha does allow me to create items without barcodes, I don't know how common that is but I can do it. Without a barcode the heading just reads 'Barcode' that is a bit confusing. Can we use itemnumber, or fall back to itemnumber? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7508] Collapsable items on items tab
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7508 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lucas(a)bywatersolutions.com --- Comment #9 from Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> --- This is wonderful and gives me pure joy. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37644] New: Let developers configure flatpickr defaultHour and defaultMinute via its config object
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37644 Bug ID: 37644 Summary: Let developers configure flatpickr defaultHour and defaultMinute via its config object Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org Let's keep default hour and minute but allow developers to use flatpickr's config object as well for setting defaults (and that config taking precedence). -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 38520] New: Should not be able to place a Recall on a next available item if items are available
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38520 Bug ID: 38520 Summary: Should not be able to place a Recall on a next available item if items are available 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a record has available items I should not be able to place a "Recall next available item". To recreate: 1. Have a record with multiple available items. 2. Have at least 1 item checked out. 3. From OPAC attempt a recall. 4. You have the option to select "Recall next available item". There are available items, why would we need to recall anything in this situation? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38519 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38519 [Bug 38519] Improve contrast of Bootstrap alerts and text background classes -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21602] New: Self registration doesn't take into account the ages for the selected patron category
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '24

22 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21602 Bug ID: 21602 Summary: Self registration doesn't take into account the ages for the selected patron category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org When a patron category is used on the PatronSelfRegistrationDefaultCategory syspref, the "Age required" and "Upperage limit" are not taken into account during the self registration. For example, if I set age required to 15 years old, I can register with a birth date = today. -- You are receiving this mail because: You are watching all bug changes.

1 6