May 2022 - Koha-bugs - lists.koha-community.org

[Bug 29336] New: Some authorised_value FK fields are too short
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '22

15 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29336 Bug ID: 29336 Summary: Some authorised_value FK fields are too short Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org To mention a few: authorised_value | varchar(10) in authority framework additional fields `authorised_value_category` varchar(16) auth_tag_structure `authorised_value` varchar(10) COLLATE utf8mb4_unicode_ci DEFAULT NULL, borrower_attribute_types `authorised_value_category` varchar(32) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 21466] New: Data inconsistencies - items.location values must have a corresponding authorised value
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '22

15 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21466 Bug ID: 21466 Summary: Data inconsistencies - items.location values must have a corresponding authorised value Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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 See bug 18355. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 29105] New: items responses do not respect effective_itemtype
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '22

15 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29105 Bug ID: 29105 Summary: items responses do not respect effective_itemtype Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com The item objects we return from various items API routes do not respect the effective itype offerings. Example, itype is mapped directly from the item itype field to item_type.. it should check for effective itemtype and return the result of that. Similarly notforloan is mapped directly, but can depend on the effective itemtype. There are possibly others. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 30641] New: Authority detail page shows wrong number of records using the authority
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '22

14 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30641 Bug ID: 30641 Summary: Authority detail page shows wrong number of records using the authority Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl You can see the wrong behaviour in a clean sample database with http://localhost:8081/cgi-bin/koha/authorities/detail.pl?authid=133 To test: * Test plan assumes you are using the ktd sample data * Staff interface > authorities * Search for agile * Verfiy the result list shows used by 2 records and this is correct (authority is linked to both of them) * Switch to authority detail page * Verify it shows 3 records use this authority * Verify this is incorrect (the second record is not linked to the authority) I suspect that the detail page doesn't do an exact/phrase search opposed to the other pages, finding also records with similar authority numbers? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 30658] New: (Bug 29496 follow-up) CheckMandatorySubfields don't work properly with select field in serials-edit.tt for Supplemental issue
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '22

14 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30658 Bug ID: 30658 Summary: (Bug 29496 follow-up) CheckMandatorySubfields don't work properly with select field in serials-edit.tt for Supplemental issue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CheckMandatorySubfields use the class "input_marceditor" but in file serials-edit.tt this class is not set for select input in Supplemental issue form. In consequence if a select field is set as mandatory, it is detected as missing even if it is filed and so you can't submit the form and receive the new supplemantal issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 30268] New: When creating an order from a staged file, mandatory item subfields that are empty do not block form submission
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '22

14 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30268 Bug ID: 30268 Summary: When creating an order from a staged file, mandatory item subfields that are empty do not block form submission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Acquisitions Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Steps to reproduce: 1. Make sure you have mandatory item subfields in the MARC bibliographic framework used in acquisitions ("ACQ" if it exists, the default framework otherwise). 2. Use the "Stage MARC records for import" tool to upload a file. Do not import the bibliographic records. 3. Create a new acquisition basket ("Create items when:" must be set to "placing an order") and add a new order from a staged file 4. Select the file you just uploaded 5. In the "Items information" tab, make sure at least one mandatory subfield is empty 6. Try to submit the form. If there are errors about other mandatory fields (like the fund for instance), fix those errors and resubmit. You will be able to submit the form without filling the mandatory item subfields, but that should not be possible. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 20439] New: SMS provider sorting
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '22

14 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20439 Bug ID: 20439 Summary: SMS provider sorting Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On intranet memberentry.pl and on OPAC opac-messaging.pl the SMS provider drop-down is sorted in the order the provider was added rather than alphabetically by provider name - making it difficult for library staff and for borrowers to find providers not added in alphabetical order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 30393] New: datatables wrapper should handle searching for % and _
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '22

14 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30393 Bug ID: 30393 Summary: datatables wrapper should handle searching for % and _ Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org This characters have special meanings in LIKE queries in MariaDB/MySQL and should be escaped correctly. [1] [1] https://dev.mysql.com/doc/refman/8.0/en/string-literals.html -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 20726] New: Display acquisition details on the subscription detail page
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '22

13 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20726 Bug ID: 20726 Summary: Display acquisition details on the subscription detail page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Serials Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Bug 20365 will add the ability to create several pending orders on the same subscription. To make it clear we should add a history of the acquisition on the subscription detail page. -- You are receiving this mail because: You are watching all bug changes.

1 60

[Bug 28730] New: Add option to format AH field (due date) in SIP checkout response
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '22

12 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28730 Bug ID: 28730 Summary: Add option to format AH field (due date) in SIP checkout response 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org According to SIP2 spec on due date/AH: This date field is not necessarily formatted with the ANSI standard X3.30 for date and X3.43 for time. Since it is a variable-length field the ACS can send this date field in any format it wishes. Some machines pass this directly to the checkout receipt, we should be able to format as a due date -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12