December 2021 - Koha-bugs - lists.koha-community.org

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '21

03 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24532] New: Some account types are converted to debits when they shouldn't be
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '21

03 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24532 Bug ID: 24532 Summary: Some account types are converted to debits when they shouldn't be Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 23049 converts some credit types to debit types The logic seems to be: 1 - Get all unique types where the accountline is a debit 2 - Convert all lines with these types to have debit codes But in step 1 if we have any type 'Pay' or 'W' for example, where the amount is greater than 0 (pathological credits which have debit amounts) then 'Pay' is added as a debit type and all 'Pay' lines get that as a debit code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 29132] New: API access denied after update to 19.11.22 due to not executed atomicupdate for api keys
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '21

03 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29132 Bug ID: 29132 Summary: API access denied after update to 19.11.22 due to not executed atomicupdate for api keys Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexander.borkowski(a)kau.se After updating from 19.11.21 to 19.11.22, API access to our Koha instance failed. The reason was that the installer/data/mysql/atomicupdate/bug_28772_api_keys.pl was not executed, likely due to the fact that installer/data/mysql/updatedatabase.pl only executes files that end in .perl or .sql, while the new one ends in .pl. Manually executing the equivalent code (hashing the API-keys) fixes the problem. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 29564] New: Use List::MoreUtils so SIP U16/Xenial does not break
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '21

02 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29564 Bug ID: 29564 Summary: Use List::MoreUtils so SIP U16/Xenial does not break Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org patch to come... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '21

02 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 --- Comment #366 from Michal Denar <black23(a)gmail.com> --- Great news, Aleisha! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '21

02 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |ASSIGNED --- Comment #365 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Hi everyone, I'll try to fix the patches today! Aleisha -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '21

02 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 Heather <heather_hernandez(a)nps.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |heather_hernandez(a)nps.gov --- Comment #4 from Heather <heather_hernandez(a)nps.gov> --- We're on 21.05, and the item search is the *only* place where Library of Congress call numbers are sorting correctly. I'm a little confused about your example, too--are the call numbers in your example Library of Congress call numbers, or call numbers in a different classification system? Library of Congress call numbers' initial alpha-numeric sequence are decimals after the period, so there wouldn't be a call number, "QA76.760" because this is the same as "QA76.76"--Library of Congress call numbers never end with a zero after the decimal. If it were a call number used locally, this sorting is correct: > Call Numbers in Item search results seem to be sorted ALPHABETICALLY, so > currently it is displayed: > QA76.76 > QA76.760 > QA76.77 The filing rule for this, if I remember correctly, is covered in the Library of Congress Filing Rules, illustrated by this example, where the absence of a character comes before the presence of a character--that is, "nothing comes before something:" A is for anatomy A4D desert speed run So this isn't correct, for Library of Congress call numbers: > where the results should be shown in the following order: > QA76.76 > QA76.77 > QA76.760 Because "point seven six zero" is less than "point seven seven." But if these aren't Library of Congress call numbers, then the sorting would be different? The LC Filing Rules say, "Arrange numerals after a decimal point digit by digit, one place at a time." So, also, ".760" can't come after ".77," if you're arranging digit-by-digit, one place at a time. (This is in section 14 of https://www.loc.gov/catdir/cpso/G100.pdf ) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '21

02 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 koha-US bug tracker <bugzilla(a)koha-us.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla(a)koha-us.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '21

02 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #78023|application/mrc |application/xml mime type| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29622] New: Add link for Lists to staff interface
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '21

02 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29622 Bug ID: 29622 Summary: Add link for Lists to staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the staff interface on search.pl and detail.pl it would be helpful if it was possible to see if a title is contained in a List. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0