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

[Bug 23031] New: Improve UX of buttons on order search page
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23031 Bug ID: 23031 Summary: Improve UX of buttons on order search page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When the change for bug 21364 was made, there as some discussion about what buttons should be accessible immediately and what should be hidden in the menu. Owen's last suggestion was: The "View" part of the split button is an unnecessary duplication of the linked basket name earlier in the table. I think the actions column should have two possible buttons: "Add to basket" and "Close basket." Maybe we could implement this? As I understand it, we would remove the view part which would leave us with 2 (or 3: uncertain prices instead of close basket) buttons that show outside of a menu. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 18227] New: Koha::Logger utf8 handling defeating " wide characters in print"
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18227 Bug ID: 18227 Summary: Koha::Logger utf8 handling defeating "wide characters in print" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org One must explicitly tell the Log4perl-appenders to deal with utf8. Poor Log4perl. Poor utf8 in Perl. this patch adds utf8=1 to log4perl.conf -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 22685] New: Koha::Acquisition::Bookseller->baskets returns a dbic resultset rather than Koha::Objects
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22685 Bug ID: 22685 Summary: Koha::Acquisition::Bookseller->baskets returns a dbic resultset rather than Koha::Objects Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- As the title says.. the relationship accessor passthrough here returns a plain dbic resultset rather than a Koha::Objects bassed object. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 22437] New: Subsequent authority merges in cron cause biblios to lose authority information
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22437 Bug ID: 22437 Summary: Subsequent authority merges in cron cause biblios to lose authority information Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: pjamorim91(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Here's how to reproduce the problem: AuthorityMergeLimit syspref is default 50. Here's an example list of 3 authorities (A, B and C) that should be merged together - resulting in 1 authority - and the total count of biblios linked to each respective authority (similar to the interface you get when searching authorities): A 100 B 60 C 2 The good scenario: If you merge the authorities like this: First: C -> A Second: B -> A All is good, after the first merge (C -> A), A has 102 biblios. After second merge (B -> A), B no longer exists and A still has 102 - as expected, because the merge is scheduled to the cron. After forcing the cron koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/merge_authorities.pl -b -v authority A now has 162 biblios, as expected. The bad scenario: The problem occurs if authorities are merged like this: First: C -> B Second: B -> A After the first merge (C -> B), B has 62 biblios. After the second merge (B -> A), B no longer exists and A still has 100 - as expected, because the merge is scheduled to the cron. However, after forcing the cron koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/merge_authorities.pl -b -v authority A still has 100 biblios, and the 62 biblios that were previously linked to B have effectively lost the authority information they previously had. After some testing, I noticed that Koha will schedule an authority merge for the same authority (on itself), even when the biblios count doesn't surpass AuthorityMergeLimit, I'll explain: For the C -> B merge, the 2 biblios from C will be updated immediately in the application (because 2 < 50), but simultaneously Koha will schedule the cron merge B -> B. I think this happens because the merge.pl script first modifies the reference authority using ModAuthority (that calls the merge function), and then calls the merge function, can be seen here: https://github.com/Koha-Community/Koha/blob/18.11.x/authorities/merge.pl#L79 Which means that Koha will run the merge function, twice, for each authority merge made in the application. I think this is by design, because if B gets modified, Koha will have to update 60 biblios with the new authority information, updated subfields information etc, and this should be indeed postponed to the cron, hence the merge on itself B -> B caused by ModAuthority. However, because B -> A happened (deleting B) after C -> B and before the cron had the chance to run, by the time the cron has to run B -> B, B has already been deleted, cleaning the authority information from the 60 (or 62) biblio records. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 62

[Bug 20648] New: Attribute option "Display in check-out" should be rename
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20648 Bug ID: 20648 Summary: Attribute option "Display in check-out" should be rename Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Attributes checked "Display in check-out" are now displayed on side panel of all tabs in patron account thanks to Bug 12159. The description "Display in check-out: Check to show this attribute in patron check-out" on the "Attribute menu" should be modifiy now. --> "Display in patron's brief information" ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 21921] New: Add date publication year to biblio Z39.50 search form
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21921 Bug ID: 21921 Summary: Add date publication year to biblio Z39.50 search form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 20399] New: Remove "did you mean" for the staff interface
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20399 Bug ID: 20399 Summary: Remove "did you mean" for the staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The amdin page for the "did you mean" feature has two block for setting it up in the staff interface, and a note saying this isn't implemented on the staff interface yet. We should remove the part about the staff interface until it actually is implemented. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 22655] New: Onboarding tool should offer to add Hold rule in addition to Circulation rule
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22655 Bug ID: 22655 Summary: Onboarding tool should offer to add Hold rule in addition to Circulation rule Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: hayleymapley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Currently, when doing a fresh install of Koha, no Holds rules are set during the Onboarding process. This means that users testing Holds or new users to Koha have to set up Hold rules in the Tools before placing any Holds. We should allow users to set up default Hold rule while setting up the Circulation rules. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 19313] New: Typo in UNIMARC field 130 plugin
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19313 Bug ID: 19313 Summary: Typo in UNIMARC field 130 plugin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dubyk(a)ukr.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Small typo: http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=koha-tmpl/intrane… https://books.google.com.ua/books?id=I9rPDkF0_ZQC&pg=PA195&lpg=PA195&dq=uni… Exists: 245 [% END %] 246 [% IF ( f7d ) %] 247 <option value="d" selected="selected">unknown</option> 248 [% ELSE %] 249 <option value="d">unknown</option> 250 [% END %] 251 [% IF ( f7u ) %] 252 <option value="u" selected="selected">mixed emulsion</option> 253 [% ELSE %] 254 <option value="u">mixed emulsion</option> 255 [% END %] Must be: 245 [% END %] 246 [% IF ( f7u ) %] 247 <option value="u" selected="selected">unknown</option> 248 [% ELSE %] 249 <option value="u">unknown</option> 250 [% END %] 251 [% IF ( f7v ) %] 252 <option value="v" selected="selected">mixed emulsion</option> 253 [% ELSE %] 254 <option value="v">mixed emulsion</option> 255 [% END %] -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 20816] New: add user expiration date to SIP2 message
by bugzilla-daemon＠bugs.koha-community.org 16 May '20

16 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20816 Bug ID: 20816 Summary: add user expiration date to SIP2 message Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org add a user's expiration date to the SIP2 message in its own field, at least Patron Information Response (64), and probably the Patron Status Response (24) -- You are receiving this mail because: You are watching all bug changes.

1 27