April 2020 - Koha-bugs - lists.koha-community.org

[Bug 20437] New: Force requirement for HTTP::OAI 3.27
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '20

23 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20437 Bug ID: 20437 Summary: Force requirement for HTTP::OAI 3.27 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Until HTTP::OAI is patched so it actually works, and bug 17704 fixes the API change Koha-side, we need to explicitly pull the right version. Otherwise people using Debian 9+ derived distros (Ubuntu 16.04+) are seeing production issues. This implies packaging our custom libhttp-oai-perl distribution in the meantime. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 24657] New: Fix tests of bug 22284 - Groups of pickup locations for holds
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '20

22 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24657 Bug ID: 24657 Summary: Fix tests of bug 22284 - Groups of pickup locations for holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Tests in bug 22284 had conditions where they randomly fail -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 24443] New: Consider NULL as 0 for issues in items search
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '20

21 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24443 Bug ID: 24443 Summary: Consider NULL as 0 for issues in items search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In items search, we can filter by items issues count, data coming from items.issues. Most of the time, for an item with no issues this column contains NULL. This enhancement proposes to consider NULL as 0 to allow searching items with no issues. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 17697] New: Notes Blacklist only blacklists fields on the OPAC main detail view ( not the OPAC MARC display)
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '20

20 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17697 Bug ID: 17697 Summary: Notes Blacklist only blacklists fields on the OPAC main detail view (not the OPAC MARC display) 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: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org To replicate: Add a note to a field in a record (let's say 500) Verify the note shows in both the OPAC Detail and OPAC MARC views Add a blacklist entry to the NotesBlacklist system preference for field 500 Verify the note does not appear on the OPAC detail Verify the note DOES appear on the OPAC MARC detail. Blacklisted notes shouldn't display anywhere in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 21292] New: Patron Deletion Tool
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '20

20 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21292 Bug ID: 21292 Summary: Patron Deletion Tool Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 78312 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=78312&action=ed… this is what Koha produces from a patron list of 3 people when only 1 could be deleted. Currently, the patron deletion tool will not delete patrons who has fines and/or checkouts. Unfortunately, the tool does not indicate the patrons that were not deleted because of these constraints. It would be nice to have Koha identify the # of patrons that were requested to be deleted, the number of patrons successfully deleted (with possibly a list) and the number and specifics of the patrons that could not be deleted due to checkouts/fines. This would give clear indication what was accomplished with this tool for libraries. The current functionality of entering patrons that have checkouts/fines that have been requested to be deleted, Koha all but ignores those patrons and doesn't say anything. For example, if I had a patron list of 3 patrons and I requested Koha delete this entire list of patrons. If 2 of those patrons had fines/checkouts, Koha would only display 1 patron deleted. This would not be a link to the patron that was deleted - just a simple number. In addition, the manual does not have correct information regarding this tool - as it indicates - this is quoted from the 17.11 manual : "Important Patrons with outstanding fines or items checked out are not saved. They are not completely removed from the system (they are only moved to the delete_borrowers table), but this tool does not provide as many checks as one may desire." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 23128] New: Missing Net::OAuth2::AuthorizationServer dependency
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '20

20 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23128 Bug ID: 23128 Summary: Missing Net::OAuth2::AuthorizationServer dependency Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Target Milestone: --- The Net::OAuth2::AuthorzationServer library packaging is missing a dependency: Crypt::PRNG. This causes the OAuth2 protocol to fail for production sites. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 22728] New: Manual for BorrowerMandatoryField should include note on extended attributes
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '20

18 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22728 Bug ID: 22728 Summary: Manual for BorrowerMandatoryField should include note on extended attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- In explaining BorrowerMandatoryField, we should include a note on how to denote extended patron attributes. They can be made mandatory by entering "patron_attr_1" (or other correct number), but I don't see that documented anywhere. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 23311] New: Normalization Rules set up in Record Matching Rules in Administration Module
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '20

18 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23311 Bug ID: 23311 Summary: Normalization Rules set up in Record Matching Rules in Administration Module Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: training(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, when researching Record Matching Rules in the 18.11 Koha Manual, the manual defines the Normalization Rules as: “Koha only has one ‘Normalization rule’ that removes extra characters such as commas and semicolons. The value you enter in this field is irrelevant to the normalization process.” However, currently, there are 4 options for Normalization Rules: remove spaces, upper case, lower case and Legacy Default. It would be helpful if these normalization rules were clarified in the manual for users. For example What does it mean Legacy Default? What does Uppercase mean? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 19426] New: Single Branch Exception to a Repeating Holiday Affects Closed Branches
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '20

17 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19426 Bug ID: 19426 Summary: Single Branch Exception to a Repeating Holiday Affects Closed Branches Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: cslone(a)camdencountylibrary.org QA Contact: testopia(a)bugs.koha-community.org Scenario: You have some branches that are open every day of the week, and several that are closed on Sundays all year round. Due to the fact that these Sunday closures do not affect every location, each branch that is closed on Sundays has its own repeating holiday set up. However, if you add an exception for a single branch to this holiday it will affect the due dates for the items being checked out from any of the other branches that are still closed that day. This is despite the fact that the calendar for the closed branches still lists them as being closed. To test: 1.) Set the "useDaysMode" preference to "calculate the due date using the calendar to push the due date to the next open day." 2.) Create a repeating holiday (individually) for two or more branches. 3.) Add an exception to this repeating holiday for one of the branches. 4.) Confirm that the exception is shown only for the intended branch. 5.) Log-in to the branch to which you did not add the calendar exception and checkout an item that should get pushed forward to be due the day after the repeating holiday - For example, you have the repeating holidays on Sunday, are logged-in on a Thursday, and checkout an item that circulates for three days, which should then get pushed from being due on Sunday to Monday 6.) Confirm that the item was made to be due on the repeating holiday for that branch instead of the day after -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23312] New: Add ability to mark an item ‘Lost’ from ‘Holds Queue List
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '20

17 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23312 Bug ID: 23312 Summary: Add ability to mark an item ‘Lost’ from ‘Holds Queue List Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: training(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In 18.11 bug 19287 was passed into Koha, allowing staff to mark an item lost from the Holds to Pull list. This is an extremely helpful process- and with this feature, Koha will even send a notice to the patron that the item cannot be filled in a hold since it is lost. It would be great to see this same functionality with the Holds Queue report, as so many libraries are multibranch and generally use the Holds Queue report. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5