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

[Bug 23341] New: Hold Notes should allow for HTML tags
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23341 Bug ID: 23341 Summary: Hold Notes should allow for HTML tags Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor 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 Koha version in 18.11, HTML tags should be allowed in Hold Notes. THis is similar to bug 23194, 22702, 22501. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 22081] New: Alternate merging functionality
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22081 Bug ID: 22081 Summary: Alternate merging functionality Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: simon.hohl(a)dainst.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Currently the merging process let's you select which fields ought to be copied over to the "winning" record from the "loosing" record(s). Afterwards, the "loosing" record is deleted (moved to tables "deletedbiblio" etc.). One problem with the current solution: You can't tell after the fact, which deleted record was merged with which existing record. This is bad if you want to provide stable links to bibliographic records, for citation in research papers for example: Ideally you would want to be able to redirect to the "winning" records if somebody calls URL to a deleted record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 24098] New: Capitalization: Fees & Charges
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24098 Bug ID: 24098 Summary: Capitalization: Fees & Charges Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We have quite some templates where "Fees & Charges" appears. It should be "Fees & charges" instead. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 24027] New: Adding multiple items is slow
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24027 Bug ID: 24027 Summary: Adding multiple items is slow Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nugged(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In cataloguing/additem.pl?biblionumber=XXX when we choose "add multiple copies of the item" it's adds very slowly. I did analysis and there's one big inefficiency of calling ModZebra( $item->{biblionumber}, "specialUpdate", "biblioserver" ); in every AddItem call: it requests update for same biblionumber after adding each new item and time for execution of this ModZebra grows exponentially. My set of patches (preparatory + fix) I will provide here will make this call to ModZebra happen once in the end of adding of the whole number of these items once. Also I will attach a few smaller follow-up patches where I propose optimisations for extra operations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 63

[Bug 19475] New: Calendar copy creates duplicates
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19475 Bug ID: 19475 Summary: Calendar copy creates duplicates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Calendar of current branch can be copied to another branch. This may be done several times creating duplicates. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 25157] New: delete_patrons.pl is never quiet, even when run without -v
by bugzilla-daemon＠bugs.koha-community.org 11 May '20

11 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25157 Bug ID: 25157 Summary: delete_patrons.pl is never quiet, even when run without -v Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When running delete_patrons.pl in cron, you still get the 'success' messages and problem cases listed, even if you don't run with the -v. It would be great if there was an option to make this script "quiet" unless a real problem occurs. Not counting users with fines and checkouts that were not deleted as a problem - that's correct behaviour. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 24963] New: Terminology: auto renewal, auto-renewal or autorenewal?
by bugzilla-daemon＠bugs.koha-community.org 11 May '20

11 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24963 Bug ID: 24963 Summary: Terminology: auto renewal, auto-renewal or autorenewal? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I've encountered all three forms, plus automatic renewal in Koha and wonder, if we can pick one to standardize on? Which is the 'most correct' spelling? - auto renewal - auto-renewal - autorenewal -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 23514] New: Call numbers are not splitted in Label Creator with layout types other than Biblio
by bugzilla-daemon＠bugs.koha-community.org 11 May '20

11 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23514 Bug ID: 23514 Summary: Call numbers are not splitted in Label Creator with layout types other than Biblio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org In Label Creator, - when one chooses any "Layout type" OTHER THAN Biblio - AND "Split call numbers" IS checked the splitting does not work at all, regardless of the classification standard used. Indeed in Label.pm, the splitting functions are applied only when printing_type=BIB I think this is a residue from the past and should be removed (or altered to exclude printing_type=BAR) -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 25081] New: new item for a received issue is (stochastically) not created
by bugzilla-daemon＠bugs.koha-community.org 11 May '20

11 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25081 Bug ID: 25081 Summary: new item for a received issue is (stochastically) not created Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com The Bug 23435 introduced the idea of multiple copies added while receiving a new issue. Unfortunately, under some circumstances, it causes no items being added at all. It occurs stochastically, only under some conditions. But it is quite likely to happen while receiving a supplemental issue. So, to reproduce, have a subscription with the option "Create an item record when receiving this serial" active and try to receive a supplemental issue. Control that a new item under the biblio record (usually) will not be created. (Sometimes it occurs also while receiving back issues). The reason fot hist is that, in serials-edit.pl, line ca 292 and infra, @num_copies is treated in the same way as @tags, while it should be treated similarly to @bibnums. It will be obvious after examining the content of parameters tag, subfield, field_value, ..., number_of_copies. In other words, for every edited issue number_of_copies is a scalar. A patch will follow. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 22937] New: Searching by library groups uses group Title rather than Description
by bugzilla-daemon＠bugs.koha-community.org 11 May '20

11 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22937 Bug ID: 22937 Summary: Searching by library groups uses group Title rather than Description Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When using library search groups, the title of the group shows up in advanced search rather than the description. The description doesn't seem to be present anywhere except when calling <<X|GROUPS>> in a report. This seems confusing as most places the description label is what will show in pulldowns (both in Auth. values and itypes parameter setup.) Lisette -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27