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

[Bug 22042] New: BlockReturnofWithdrawn Items does not block refund generation when item is withdrawn and lost
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22042 Bug ID: 22042 Summary: BlockReturnofWithdrawn Items does not block refund generation when item is withdrawn and lost Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- If BlockReturnofWithdrawnItems is set to block and an item that is both withdrawn and lost is checked in, Koha will not mark the item as returned but will mark it as found and generate a refund if circ rules allow refunds. To test: - Set BlockReturnofWithdrawnItems to Block - Set BlockReturnofLostItems to Don't Block - Set Default lost item fee refund on return policy to Yes - Check out an item with a replacement cost to a patron - Mark the item as lost - Mark the item as withdrawn - Note that the patron now has a charge for the replacement fee - Check the item in - Note that the patron now has a credit for the replacement fee -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 33899] New: Release team 23.11
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33899 Bug ID: 33899 Summary: Release team 23.11 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 33877 Add the next release team :) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33877 [Bug 33877] Fix teams.yaml -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 34549] New: The cataloguing editor allows you to input invalid data
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34549 Bug ID: 34549 Summary: The cataloguing editor allows you to input invalid data Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I had a library using UTF-8 encoding instead of MARC-8 encoding, and they were able to import records into the cataloguing editor and save them into Koha. Then when they tried to view, edit, or delete the records, Koha would throw fatal errors. You can duplicate this by copying and pasting the following character into your cataloguing editor in say the 245$a field: -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 34645] New: Add missing fields to MarcItemFieldsToOrder system preference
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34645 Bug ID: 34645 Summary: Add missing fields to MarcItemFieldsToOrder system preference 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org See bug 34644 - MarcItemFieldsToOrder supersedes MarcFieldsToOrder, so the fields discount, sort1, and sort2 won't be populated if using the latter - We should add these fields in to allow the orders to be created correctly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 26611] New: Required match checks don't work for authority records
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26611 Bug ID: 26611 Summary: Required match checks don't work for authority records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The code specifically ignores these for authorities, I am not sure why? While we could easily disable the feature for authority matching to follow current behaviour, I believe we need this functionality to be able to match correctly. Match points check only the first 20 records (see bug 21972) so can only target unique or unique-ish values Match checks allow you to compare specific fields and can verify that matches above are correct. For example: Importing records and checking the 010a - which matches the LC-card-number index can have false matches because the index also contains the 010z - the match check would allow us to compare the specific fields in the records as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 34270] New: Upgrade and prune jQueryUI assets in the staff interface
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '24

14 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34270 Bug ID: 34270 Summary: Upgrade and prune jQueryUI assets in the staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 34114 With the elimination of our dependency on jQueryUI Sortable by Bug 34114 we will be left with only autocomplete as a jQueryUI dependency. We can trim down our jQueryUI assets to reflect this and upgrade at the same time. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34114 [Bug 34114] Replace the use of jQueryUI sortable -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 26586] New: Koha should return a SIP2 64 response to a 63 request for fee items
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '24

13 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26586 Bug ID: 26586 Summary: Koha should return a SIP2 64 response to a 63 request for fee items 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com At the moment, we're supporting SIP 2.0 for the 63 Patron Information Request, but the 3M SIP2 Protocol Extensions outlines a 7th position "fee items". If a SIP2 client sents a Y in that position, Koha will close the connection. At the very least, it should just return a 64 response and just not send any fee item info back. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 17318] New: Make 'Normalization rule' configurable on matchpoint definition
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '24

12 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17318 Bug ID: 17318 Summary: Make 'Normalization rule' configurable on matchpoint definition Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently, there's a free text field on matchpoint definition, that is of no use, as the code does some default normalization no matter what you put there (se screenshot). As pointed out on 17304 and other bugs, this normalization routine is counter productive. The purpose of this bug is to introduce a way for defining the normalization rules we'd like to apply. IT will make use of bug 17302 to have a small (but useful) list of normalization routines. This could be expanded if needed, or we could even make plugins do it (that'd certaintly belong to another bug report). I don't think removing the 'feature' is a good move now, but we could consider it with broader discussion. Someone should rise it in koha-devel, meetings, etc. This will provide a way out, until we end that fine-grained discussion. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 20558] New: typo mts_authorized_value vs mts_authorised_value in admin/marctagstructure.pl
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '24

12 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20558 Bug ID: 20558 Summary: typo mts_authorized_value vs mts_authorised_value in admin/marctagstructure.pl Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org What are the consequences of this? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 22258] New: Elasticsearch - full record is not indexed in plain text
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '24

11 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22258 Bug ID: 22258 Summary: Elasticsearch - full record is not indexed in plain text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Target Milestone: --- This is to start a discussion - at some point we dropped the inclusion of the full record in plain text in the ES index A consequence is that data in a field that is not specifically indexed is no longer searchable. This is a change from zebra I believe where the entire record can be searched. I am not sure of the affect on relevancy, but I think we need t o find a way to support full record searching. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32