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

[Bug 19992] New: use Modern::Perl in Admin perl scripts
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '18

06 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19992 Bug ID: 19992 Summary: use Modern::Perl in Admin perl scripts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com use Modern::Perl in the place of use strict; use warnings; Relevant in following cases admin/admin-home.pl admin/aqcontract.pl admin/aqplan.pl admin/auth_tag_structure.pl admin/branch_transfer_limits.pl admin/check_budget_parent.pl admin/check_parent_total.pl admin/checkmarc.pl admin/classsources.pl admin/clone-rules.pl admin/didyoumean.pl admin/edi_accounts.pl admin/edi_ean_accounts.pl admin/import_export_framework.pl admin/item_circulation_alerts.pl admin/marctagstructure.pl admin/matching-rules.pl admin/printers.pl admin/smart-rules.pl admin/systempreferences.pl admin/transport-cost-matrix.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 19451] New: Let borrowers-force-messaging-defaults.pl optionally add preferences only when not already present
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '18

06 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19451 Bug ID: 19451 Summary: Let borrowers-force-messaging-defaults.pl optionally add preferences only when not already present Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz A welcome addition to borrowers-force-messaging-defaults.pl would be to allow adding the messaging defaults only to patrons without such preferences. This will be made possible with the empty_only option. It copies the prefs only when the borrower prefs are empty (read: are not present). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 19996] New: use Modern::Perl in cataloguing perl scripts
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '18

06 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19996 Bug ID: 19996 Summary: use Modern::Perl in cataloguing perl scripts 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl use Modern::Perl should be used instead of use strict; use warnings; Relevant in: addbiblio.pl addbooks.pl additem.pl linkitem.pl moveitem.pl value_builder/normarc_field_007.pl value_builder/normarc_field_008.pl value_builder/normarc_leader.pl value_builder/unimarc_field_010.pl value_builder/unimarc_field_100.pl value_builder/unimarc_field_105.pl value_builder/unimarc_field_106.pl value_builder/unimarc_field_110.pl value_builder/unimarc_field_115a.pl value_builder/unimarc_field_115b.pl value_builder/unimarc_field_116.pl value_builder/unimarc_field_117.pl value_builder/unimarc_field_120.pl value_builder/unimarc_field_121a.pl value_builder/unimarc_field_121b.pl value_builder/unimarc_field_122.pl value_builder/unimarc_field_123a.pl value_builder/unimarc_field_123d.pl value_builder/unimarc_field_123e.pl value_builder/unimarc_field_123f.pl value_builder/unimarc_field_123g.pl value_builder/unimarc_field_123i.pl value_builder/unimarc_field_123j.pl value_builder/unimarc_field_124.pl value_builder/unimarc_field_124a.pl value_builder/unimarc_field_124b.pl value_builder/unimarc_field_124c.pl value_builder/unimarc_field_124d.pl value_builder/unimarc_field_124e.pl value_builder/unimarc_field_124f.pl value_builder/unimarc_field_124g.pl value_builder/unimarc_field_125.pl value_builder/unimarc_field_125a.pl value_builder/unimarc_field_125b.pl value_builder/unimarc_field_126.pl value_builder/unimarc_field_126a.pl value_builder/unimarc_field_126b.pl value_builder/unimarc_field_127.pl value_builder/unimarc_field_128a.pl value_builder/unimarc_field_128b.pl value_builder/unimarc_field_128c.pl value_builder/unimarc_field_130.pl value_builder/unimarc_field_135a.pl value_builder/unimarc_field_140.pl value_builder/unimarc_field_141.pl value_builder/unimarc_field_210c.pl value_builder/unimarc_field_210c_bis.pl value_builder/unimarc_field_225a.pl value_builder/unimarc_field_4XX.pl value_builder/unimarc_field_686a.pl value_builder/unimarc_field_700-4.pl value_builder/unimarc_leader.pl z3950_auth_search.pl z3950_search.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 19562] New: Inventory: How can we skip convolutes marked as problematic with no_barcode?
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '18

06 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19562 Bug ID: 19562 Summary: Inventory: How can we skip convolutes marked as problematic with no_barcode? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org We have two biblio records, but one item. It is a convolute, a bound set of actually two items. We added one item to each biblio, added Convolute in the item notes and gave the bound set one barcode recorded in one of the items. When doing inventory and comparing with a barcode file, you can imagine that the item without the barcode (having the same callnumber as the item with the barcode) is reported as a problem (no_barcode). A simple custom solution is: $item->{problems}->{no_barcode} = 1 unless $item->{itemnotes} =~ /convolute/i; Do you have any suggestions or ideas to resolve similar problems with convolutes, if you have them ? How do you record this situation ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 20497] New: LibraryThing access should using https instead of http
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '18

02 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20497 Bug ID: 20497 Summary: LibraryThing access should using https instead of http Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 17137 As per bug 17137, we should be using SSL for all external resources. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17137 [Bug 17137] Omnibus: Always use SSL when referencing external sources -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 20494] New: Remove unused code in neworderempty.pl and addbiblio.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '18

02 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20494 Bug ID: 20494 Summary: Remove unused code in neworderempty.pl and addbiblio.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org z3950authortemplate is referenced in some comments and there are a few other lines commented out that seem to be cruft -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20392] New: Multiple biblio holding does not work when patron is not set
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '18

02 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20392 Bug ID: 20392 Summary: Multiple biblio holding does not work when patron is not set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 To recreate: 1) Set the system preference DisplayMultiPlaceHold to enable 2) Search in staff client catalogue 3) On results page check more then one result and click on Place hold button at the top of the page 4) Search for patron, but don't be to specific, you need to have more then one result 5) Click on one of the found patron 6) Now you are going to confirm a hold, but only for one record! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 19527] New: Alter Zebra indexing to sort by descending document ID
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '18

01 Apr '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19527 Bug ID: 19527 Summary: Alter Zebra indexing to sort by descending document ID Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk We are receiving complaints about the sorting order of relevance ranked searches. One specific example was where the older edition of a work appears higher up the list than the more recent version. According to http://www.indexdata.com/zebra/doc/administration-ranking.html: “If one defines the staticrank:1 directive in the main core Zebra configuration file, the internal document keys used for ordering are augmented by a preceding integer, which contains the static rank of a given document, and the index lists are ordered first by ascending static rank, then by *** ascending *** document ID.” Would it not be better to have the secondary rank in terms of ** descending *** document ID? That way there is much better likelihood that the most recently published version of various editions will appear closer to the top of the OPAC list, and certainly (all else being equal) above the earlier edition(s) of the specific work. Ray Delahunty University of the Arts London -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 8643] Add important constraint to marc subfields
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '18

31 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8643 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #44 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Charles, a lighter yellow would work for me. I retested, but I can't get the message to show up now, neither for an important field or subfield. Can you please check? Tiny thing: marc_tag_structure - maybe move the new field after mandatory? +-- $dbh->do("ALTER TABLE marc_tag_structure ADD COLUMN important TINYINT(4) NOT NULL DEFAULT 0 AFTER frameworkcode"); -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8457] No results found on term/phrase click in scan index results list
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '18

31 Mar '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8457 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|No results found on |No results found on |term/phrase click in scan |term/phrase click in scan |index results list . |index results list --- Comment #9 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I am still seeing very different result lists when clicking on an index term. -- You are receiving this mail because: You are watching all bug changes.

1 0