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

[Bug 25788] New: Club holds should have an optional expiration date
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25788 Bug ID: 25788 Summary: Club holds should have an optional expiration date Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 There is no way to set an expiration date for club holds. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25784] New: Flag to make individual items non-holdable
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25784 Bug ID: 25784 Summary: Flag to make individual items non-holdable Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: fiona.borthwick(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Items can be made non-holdable by item type - can set the 'holds policy' in the 'Default hold policy by item type' area. This works fine if we have a set of items that should be non-holdable. The NOT_LOAN authorised value can also play a role in identifying items that can be placed on hold. e.g. -1 = Ordered (holdable), 1 = Not for loan (non-holdable) Problems arise however if only individual items should be non-holdable or if there are specific collections (identified by ccode) that should be non-holdable BUT these items can go out on loan. We have a customer who have a set of items that belong in a specific collection (ccode). These are a mixutre of item types (e.g. Book, Audio Book etc) that link to different circ rules. All these items can go out on loan. In this case we cannot really advise allocating a new item type as loan periods differ by current item types. We could of course then duplicate the item type - e.g. have BK (Book) and BK-NH (Book Non-holdable) but this adds unnecessary complexity and would have implications on the circulation rules! It is not really an option to add a NOT_LOAN status to these records as this would mean that staff would have to override a checkout transaction each time and there would be problems at the self issue machines. The status would also not look correct. It would be really good if we could add some flag into the item record or find some other method to mark items as non-holdable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 25736] New: ClaimsReturnedWarningThreshold should be disabled by being unset
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25736 Bug ID: 25736 Summary: ClaimsReturnedWarningThreshold should be disabled by being unset Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Tangential to bug 25733 If ClaimsReturnedWarningThreshold is empty, it should be ignored and no message should be shown in patron account. Imagine: - a library decides to use Claims Returned, sets it up, uses it for a while - the library decides not to use it anymore and removes the values from ClaimReturnedLostValue and ClaimReturnedWarningThreshold - Koha treats the blank in ClaimReturnedWarningThreshold as a zero, shows the warning for anyone who still has 1 or more claims in the database - With ClaimReturnedLostValue unset, there is no longer a way to see or address those claims -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 25719] New: Add system preference for logged in patrons to display only the patron's first name
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25719 Bug ID: 25719 Summary: Add system preference for logged in patrons to display only the patron's first name Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org We'd like to see a system preference created that would allow libraries to select whether they would like to display the full patron name or only the first name for patrons who are logged into the OPAC. This would provide a cleaner display since some patron names can be rather long. In addition, most commercial websites will only display a first name for logged in users. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 25766] Install error on 20.05
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25766 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Jonathan Druart from comment #1) > What is the full error you see in the Koha log file? There wasn't any additional information provided to help resolve the issue. Closing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 25737] New: Allow for Claims Returned status in Lost Authorized Value to be branch specific
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25737 Bug ID: 25737 Summary: Allow for Claims Returned status in Lost Authorized Value to be branch specific Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, in the Lost Authorized value set up - a lost status can be specific to a branch. So only that branch/es can use that specific lost status. This is super helpful in consortiums. With this new Claims Returned feature, you assign a lost value for your Claims returned, and in the set-up (Authorized Value) it does show that it can be branch-specific, however, this is currently not working as expected. This could be due to this bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24279 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 17735] New: Merge boraccount and pay pages into one
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17735 Bug ID: 17735 Summary: Merge boraccount and pay pages into one Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We don't really need to have this agenda on two pages - using the one pages would be simpler and makes the workflow more straightforward -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 24079] New: Convert paycollect 'page' to a modal
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24079 Bug ID: 24079 Summary: Convert paycollect 'page' to a modal Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org Depends on: 24078 Blocks: 17596 As the title says, I think we could modernise the UX for accounts by converting the various paycollect displays into a modal. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17596 [Bug 17596] Simplify accounting UI in staff client https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24078 [Bug 24078] Convert manual credit 'tab' to a modal -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 25976] New: Add 'Writeoff' button under Transactions tab in patron accounting
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25976 Bug ID: 25976 Summary: Add 'Writeoff' button under Transactions tab in patron accounting Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: josef.moravec(a)gmail.com, joy(a)bywatersolutions.com, julian.maurice(a)biblibre.com, kyle(a)bywatersolutions.com, lucas(a)bywatersolutions.com, martin.renvoize(a)ptfs-europe.com Blocks: 24079 Nearly all over actions are now available via the transactions page directly.. we should add write-off to complete the set. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24079 [Bug 24079] Convert paycollect 'page' to a modal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 25900] New: Double quotes breaks search with Zebra and QueryWeightFields
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25900 Bug ID: 25900 Summary: Double quotes breaks search with Zebra and QueryWeightFields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Search with Zebra and system preference QueryWeightFields on builds a query with surrounding double quotes : q=tree => q="tree". Therefore existing double quotes are replaced by a space : q="tree" => q=" tree ". Looks like the leading space breaks the search, 0 results. Experimented on Ubuntu Xenial and Bionic with Indexdata repository so Zebra version is 2.1.4. It might be specific to this version. You can reproduce with direct CCL query (regardless QueryWeightFields) : https://demo.biblibre.com/cgi-bin/koha/opac-search.pl?idx=&q=ccl%3Dti%2Cphr… https://demo.biblibre.com/cgi-bin/koha/opac-search.pl?idx=&q=ccl%3Dti%2Cphr… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36