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

[Bug 32273] New: Unable to set author subfields in Elastic search configuration
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '22

09 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32273 Bug ID: 32273 Summary: Unable to set author subfields in Elastic search configuration Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com In a situation in which you have 2 authors that are both named Barnaby Conrad but one has the authorized name of dates 1922-2013 and the other has III, 1952-. If you click on one of their names for a search from a record where they are the author, results for both show up as the search just does au:"Conrad, Barnaby,". Configuring subfields in the Elastic search do not resolve the problem. Current work around is to enable 'UseAuthoritiesForTracing.' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 32074] New: Edit vendor has a floating toolbar, but still an additional save button at the bottom
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '22

09 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32074 Bug ID: 32074 Summary: Edit vendor has a floating toolbar, but still an additional save button at the bottom Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org That's a small inconsistency with other forms having the floating toolbar. On the edit vendor form, there is also another save button at the bottom. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 27244] New: items with a negative not for loan values are considered available in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '22

08 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27244 Bug ID: 27244 Summary: items with a negative not for loan values are considered available in the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the OPAC search results if you use the 'Limit to currently available items' filter or add '&limit=available' to your search URL items with negative not for loan values (on order) are not filtered out. To recreate: 1. add some negative nfl values to items 2. do an OPAC search where those items would up in the results 3. click the 'Limit to currently available items' filter 4. items with negative not for loan values still show -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 31984] New: TaxRate system preference - incorrect default value used and warning message on order form
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '22

08 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31984 Bug ID: 31984 Summary: TaxRate system preference - incorrect default value used and warning message on order form 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org For the TaxRate system preference: 1. The description [1] says that the first value entered will be used by default. 2. When entering an order for a basket, the last value in the list is selected as the default (19.65%). 3. If the values for the TaxRate system preference are changed, for example having the values: 0.15|0.20: - 19.65% is shown as the default value, even though it is not a value entered in the TaxRate system preference - There is a warning for the 'Tax rate' input field for the order: "Tax rate not defined in system preference TaxRates!" - The tax inclusive values for budgets/funds are calculated correctly if you choose another option, despite the warning message. To replicate: 1. Check that there are values entered for the TaxRates system preference (in KTD the values entered are: 0|0.12|0.1965). 2. Create a new basket (or use an existing one). 3. Add a new order to the basket. 4. On the accounting details form, note that the default value for the 'Tax rate' field is 19.65% and the other options are 0% and 12%. 5. Complete adding the order to the basket. 6. On the acquisitions home page, note that the ordered amount is tax inclusive and is calculated correctly. 7. Change the TaxRates system preference to: 0.15|0.20 8. Repeat steps 2-3. 9. Note that on the accounting details form for the 'Tax rate' field: . the options available are 15%, 20%, and 19.65%, with the 19.65% shown as the default - even though 19.65% is not a value entered for the system preference . there is a warning for the field: "Tax rate not defined in system preference TaxRates!" 10. Select the 15% option, and repeat steps 5-6. The tax inclusive amount is correctly calculated, despite the warning that was on the form. [1] Current description in master, with default values used in KTD: Tax rates are [0|0.12|0.1965]. Enter in numeric form, 0.12 for 12%. The first item in the list will be selected by default. For more than one value, separate with | (pipe). Please note: The database will only accept values up to 4 decimals precision, further values will be rounded. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 32283] New: Capitalization: opac users of this domain to login with this identity provider
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '22

08 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32283 Bug ID: 32283 Summary: Capitalization: opac users of this domain to login with this identity provider Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org opac is an abbreviation and needs to be written in capitals: OPAC koha-tmpl/intranet-tmpl/prog/en/modules/admin/identity_provider_domains.tt:261 opac users of this domain to login with this identity provider -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 32282] New: Capitalization: User id
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '22

08 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32282 Bug ID: 32282 Summary: Capitalization: User id Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org ID is an abbreviation and as such should always be capitalized: User id => User ID koha-tmpl/intranet-tmpl/prog/en/modules/admin/identity_providers.tt:406 -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 28235] New: Cover images are showing very large in search results
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '22

08 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28235 Bug ID: 28235 Summary: Cover images are showing very large in search results Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org Cover images are showing very large on search result. At least when using CustomCoverImages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 32261] New: Insufficient user feedback when selecting patron in autocomplete
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '22

08 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32261 Bug ID: 32261 Summary: Insufficient user feedback when selecting patron in autocomplete Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Staff interface Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(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.

1 16

[Bug 31381] New: [Intranet/REST-API] Searching patrons by letter broken when using non-mandatory extended attributes
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '22

08 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31381 Bug ID: 31381 Summary: [Intranet/REST-API] Searching patrons by letter broken when using non-mandatory extended attributes Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: oliver.behnke(a)aei.mpg.de CC: tomascohen(a)gmail.com Hi, searching for patrons by letter like this returns an empty list: /cgi-bin/koha/members/members-home.pl?firstletter=A I find the following in intranet-error.log: [cgi:error] AH01215: [warn] OpenAPI >>> GET api/v1/patrons [{"message":"Expected string - got null.","path":"\\/body\\/10\\/extended_attributes\\/0\\/value"},{"message":"Expected string - got null.","path":"\\/body\\/14\\/extended_attributes\\/0\\/value"}]: /usr/share/koha/api/v1/app.pl, referer: /cgi-bin/koha/members/members-home.pl?firstletter=A We have defined a single extended attribute which isn't mandatory, so it might not exist for some patrons. If I interpret "10" and "14" as representing borrower_attributes.borrowernumber (table.attribute) values then "10" does indeed lack an entry, but "14" has one. Not a smoking gun yet... Maybe this is a regression due to this? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27857 Cheers -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 32325] New: Valid 006/00 values should not depend on Type of Material selection
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '22

07 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32325 Bug ID: 32325 Summary: Valid 006/00 values should not depend on Type of Material selection 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, nick(a)bywatersolutions.com Depends on: 32321 In the 006 control field, the value in position 00 sets the "form of material" ("language material," "notated music," etc). That value informs the type of material configuration ("Books," "Computer files," etc). For example, if the leader position 06 and the 006 position 00 are "m," then the material type should be "Computer files" and the other 006 positions and parts of the 008 should behave accordingly. (https://www.loc.gov/marc/bibliographic/bd008c.html) In both the regular and advanced cataloging editors, Koha shows one both the 006 position 00 value *and* the material type. That's handy, but Koha makes the material type manually editable rather than derived from the position 00 value. In fact, Koha forces position 00 to only allow one to enter values that match what you've selected for material type. So to change the value in position 00, one must first change the type of material. Instead, one should be able to set 006/00 to any value allowed in the MARC specifications and that choice should set the Type of Material and thereby define how the rest of the 006 behaves. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32321 [Bug 32321] 006 field not correctly prepopulated in Advanced cataloging editor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3