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

[Bug 10734] Add Publication Date Facet in Searching
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 Séverine Queune <severine.queune(a)bulac.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |severine.queune(a)bulac.fr -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14783] Allow patrons to change pickup location for non-waiting holds
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

1 0

[Bug 26298] New: If MaxItemsToProcessForBatchMod is set to 1000, the max is actually 999
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26298 Bug ID: 26298 Summary: If MaxItemsToProcessForBatchMod is set to 1000, the max is actually 999 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org So this is similar to bug 10163, but I don't think it's the same thing. I noticed that if you have 1000 in MaxItemsToProcessForBatchMod, and you try to process 1000 items, there's an error message "Too many items (1000): You are not allowed to edit more than 1000 items in a batch." The message itself is a bit confusing because 1000 is not "more than" 1000. And you're probably thinking "well, just put 999 items in your file and voilà!", but if you batch modify using the reports, the options are 10, 20, 50, 100, 200, 300, 400, 500, and 1000. If you have a lot of batches to do, the difference between 500 and 1000 is double the work. To reproduce: 1- Set MaxItemsToProcessForBatchMod to 1000 2- Go to Reports 3- Make a report for itemnumbers that will give you at least 1000 items (ex. SELECT itemnumber FROM items) 4- Save and run the report 5- In "Rows per page", choose 1000 6- Click on "Batch operations with 1000 visible records" > Batch item modification 7- Notice that the item modification form isn't there and that the message says "Too many items (1000): You are not allowed to edit more than 1000 items in a batch." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 9553] Link authorities to bibs when imported
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9553 --- Comment #6 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Andrew Fuerste-Henry from comment #2) > On master currently, bulk-imported bibs *will* be linked to authorities as > part of the import if BiblioAddsAuthorities is turned on. > > I don't feel like connecting this behavior and syspref makes much sense. I'd > rather have a separate syspref in the Linker section of the Authorities > syspref, something like LinkerOnImport. I totally agree with you. It drives me a bit crazy. Unfortunately, not on my list of priorities at the moment though... -- 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 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 --- Comment #277 from David Cook <dcook(a)prosentient.com.au> --- I could potentially take over some work on this in the near future, although I might be more valuable as a tester/QAer. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15565] Place multiple holds at once for the same record in OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15565 --- Comment #239 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Aleisha Amohia from comment #237) > I have a bit of time now, tackling this again. I'll try and fix the patches > so they are easier to work with. Awesome! Feel free to ping me when you're ready and I'll happily test. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15565] Place multiple holds at once for the same record in OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15565 Martha Fuerst <mfuerst(a)hmcpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfuerst(a)hmcpl.org --- Comment #238 from Martha Fuerst <mfuerst(a)hmcpl.org> --- Thanks, Aleisha! We're very interested in this. -Martu Fuerst, Huntsville-Madison County Public Library -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9805] Lost items are un-lost if returned, but not if renewed
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9805 --- Comment #63 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- (In reply to Cheryl from comment #62) > So with this fix, if the lost item is renewed and the status of lost (long > overdue lost) is taken off, what happens with the lost item cost? Does the > patron still owe it? and if the patron still owes the lost item cost after > renewing the item, and then returns the item, does that mean that they do > not get a refund for the item, since the item was not in a lost status at > the time of return? > > It seems like some libraries would want to be able to renew lost items, but > also to refund the lost item cost if the item is returned OR renewed. (Our > library does not allow renewals on lost items because if you renew a lost > item, the lost item cost stays on there and we don't want that.) > > We are okay with how it works for us now (no renewal of lost items), but I > wanted to bring up the issue of the lost status coming off when the item is > renewed, and then the patron possibly not being refunded if the item is > returned later. At the very least, there should be an option as to whether or not the charge is maintained if the item is checked in or renewed. Our libraries don't charge the lost price if the item is returned. We simply want our things back. Some libraries refund the price, but retain the late fees, because, after all, they were very late. Personally, I think it is wrong to charge a replacement cost for something that is returned. Late fees, yes, absolutely keep them on the patron account. But charging for the replacement cost after it is returned seems like theft. UNLESS the item has actually been replaced. THEN the cost should be maintained. Wouldn't it be nice if there was a way to indicate on an item record if the item was replaced? Then Koha would know if maintaining the cost of replacement is justified. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9805] Lost items are un-lost if returned, but not if renewed
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9805 Cheryl <clackman(a)fargolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clackman(a)fargolibrary.org --- Comment #62 from Cheryl <clackman(a)fargolibrary.org> --- So with this fix, if the lost item is renewed and the status of lost (long overdue lost) is taken off, what happens with the lost item cost? Does the patron still owe it? and if the patron still owes the lost item cost after renewing the item, and then returns the item, does that mean that they do not get a refund for the item, since the item was not in a lost status at the time of return? It seems like some libraries would want to be able to renew lost items, but also to refund the lost item cost if the item is returned OR renewed. (Our library does not allow renewals on lost items because if you renew a lost item, the lost item cost stays on there and we don't want that.) We are okay with how it works for us now (no renewal of lost items), but I wanted to bring up the issue of the lost status coming off when the item is renewed, and then the patron possibly not being refunded if the item is returned later. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15565] Place multiple holds at once for the same record in OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15565 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |ASSIGNED --- Comment #237 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- I have a bit of time now, tackling this again. I'll try and fix the patches so they are easier to work with. -- You are receiving this mail because: You are watching all bug changes.

1 0