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

[Bug 7029] Searching : fuzzy and stemming
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7029 --- Comment #12 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- This is from: /etc/zebradb/etc/word-phrase-utf.chr Seeing if there is a difference between ICU and grs would also be interesting. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 7029] Searching : fuzzy and stemming
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7029 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|searching : fuzzy et |Searching : fuzzy and |steming |stemming --- Comment #11 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think it might actually be something else at play here: chine and chiene i = ie + auto-truncate pain and paien + auto-truncate Can you check if turning of QueryAutoTruncate? Thinking about something like this: 18 equivalent iíìîịĩĭįǐȉȋ 19 equivalent ï(ie) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. You are the QA Contact for the bug.

1 0

[Bug 7957] Routing lists: manage several routing list for each subscription, and export them as CSV
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7957 --- Comment #92 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to David Cook from comment #91) > (In reply to Katrin Fischer from comment #82) > > Multiple routing lists per subscription. > > What is the purpose/use of having multiple routing lists per subscription? I think there are different use case. Some libraries don't want to use x subscriptions, while they still receive x issues for one. So having differnt routing lists could go on multiple issues of the same subscription. In other cases libraries might want to keep the lists shorter / more anonymous, thus using different ones. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9872] Logs explode with messages when adding a new order in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9872 --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Aleisha, I just tried. I used the ACQ framework that is now standard, so that step in the test plan is on longer necessary: Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14648] Batch remove reserve items
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14648 --- Comment #6 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Sounds perfect, thank you! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14648] Batch remove reserve items
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14648 --- Comment #5 from Joe Sikowitz <joe(a)flo.org> --- Hi Katrin. Thanks for the feedback on the patch. I'll update it without tabs and make the change in the language of the button. I'll then readd the patch and post it for testing. Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23257] New: OPACHoldsIfAvailableAtPickup not working correctly for single branch installations
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23257 Bug ID: 23257 Summary: OPACHoldsIfAvailableAtPickup not working correctly for single branch installations Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Found this testing in 17.11, needs to be confirmed for versions higher up: - Have only 1 library in your system - Set OPACHoldsIfAvailableAtPickup to "not allow" - Create a circulation condition allowing "on shelf holds" - Go to the OPAC - try to place a hold. It won't be possible. (NOT OK) - Go to the staff side- try to place ahold. It will be possible. (OK) - Change the pref - Holds should work in both staff and OPAC. - Change the pref back to "not allow", add a second library - Holds will be possible. (NOT OK it requires a second library) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 14713] updatecharges permissions also require borrowers permission
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14713 --- Comment #9 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Jonathan Druart from comment #8) > Katrin, I think it's not correct for all the subperms. > > I found, at least: > > koha-tmpl/intranet-tmpl/prog/en/modules/circ/returns.tt > 750 [% IF ( > CAN_user_updatecharges_writeoff && overduecharges ) %] > > to display "Forgive overdue charges" Hm, I think this is a somewhat special case that will also require a different permission (circulate). I could amend the note maybe: From: Requires permissions to view patron details. To: Requires permissions to view patron details or circulation. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12769] Notice fee management
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12769 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Failed QA --- Comment #39 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I believe with all the comments and more so changes to the notices (think TT syntax) and fee management (configurable debit types) these patches will need rethinking and changes. I am marking Failed QA, but they will also no longer apply. I personally think it'd be great to have a separate configuration page and table for this that ties in with the configurable debit types. That would take care of descriptions and entries to the accountlines tables quite nicely. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14083] Make it possible to record the date the order was placed/sent to the vendor
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14083 --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- There is a bit of a gap here in what Koha thinks the vendor date is and what will happen if you use an automated process I think. In Koha closing the basket will switch the status from new to ordered and we record this date in aqbasket.closedate. So for the system, closing the basket indicates things were ordered and we do display the close date as ordering date at least in some places already. It makes sense to me to tie the status change to the date in some way. But maybe it should be possible to edit the ordering/closing date if necessary to allow backdating and similar? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0