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

[Bug 27768] New: Saving an item with an invalid dateaccessioned or replacementpricedate throws
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '24

13 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27768 Bug ID: 27768 Summary: Saving an item with an invalid dateaccessioned or replacementpricedate throws Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Steps to reproduce: 1. Edit any item, change either the "d - Date acquired" or "w - Price effective from" to anything not-a-date (I like 24.99, due to mispasting Replacement price into Price effective from 2. Save the record Actual result: Invalid value passed, items.replacementpricedate=2 expected type is date at /usr/share/perl5/Exception/Class/Base.pm line 88 You can hit Back in the browser to go back and fix it, assuming you know what an items.replacementpricedate is or have an English speaker handy to tell you it's the Дата, для якої чинна ціна заміни. Expected result: Human readable message in a popup or in the page itself, giving the name of the field in the editor, rather than the name of the field in the database -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 23609] New: Tie patron gender to an authorized value
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '24

13 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23609 Bug ID: 23609 Summary: Tie patron gender to an authorized value Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the interest of allowing greater flexibility, it'd be great to have gender tied to an authorized value so libraries can edit/add/delete options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 25621] New: Some tests in t/DateUtils.t fail when timezone is not UTC
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '24

11 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25621 Bug ID: 25621 Summary: Some tests in t/DateUtils.t fail when timezone is not UTC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Test Suite Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org To reproduce: 1. Verify that TZ environment variable is not defined 2. Verify that $KOHA_CONF does not contain <timezone> 3. Run `date` to verify that you have a local time different than UTC 4. prove t/DateUtils.t Expected output: % prove t/DateUtils.t t/DateUtils.t .. 1/76 # Failed test 'dt_from_string handles seconds with 1 decimal place' # at t/DateUtils.t line 130. # got: '1325447940' # expected: '1325462340' # Failed test 'dt_from_string handles seconds with 2 decimal places' # at t/DateUtils.t line 133. # got: '1325447940' # expected: '1325462340' # Failed test 'dt_from_string handles seconds with 3 decimal places' # at t/DateUtils.t line 136. # got: '1325447999' # expected: '1325462399' # Failed test 'dt_from_string handles seconds with 3 decimal places and a timezone' # at t/DateUtils.t line 139. # got: '1325447999' # expected: '1325462399' # Looks like you failed 4 tests of 76. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 21559] New: Rules for automatic framework codes
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '24

11 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21559 Bug ID: 21559 Summary: Rules for automatic framework codes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Allow setting rules in a system preference, what framework code should be automatically set for biblio, based on the MARC record fields. Does not affect anything if the MarcToFrameworkcodeAutoconvert system preference rules aren't used. The "Default" framework is always overridden, if the rules match, but some other framework chosen by you is always used. Explanation of the rule format: ------------------------------- The syspref is YAML, with a specific format: - <field> <value>: <frameworkcode> If the <field> in the record contains <value>, the <frameworkcode> is used for the record. <field> is one of: "xxx" (field xxx in the MARC record) "xxx/yy" (field xxx, character location yy) "xxx/yy-zz" (field xxx, character locations yy-zz) "xxx$v" (field xxx, subfield v) Fields can be combined with plus-sign, then the field values have plus-sign between them. The field-rules are checked in order from top to bottom, and the first rule with a matching value is used. If the (sub)field has been repeated in the MARC record, only the first matching (sub)field is checked. If none of the rules match, the framework code is not changed. Example: - 008/35-37 + 000/06: fin+a: BKSFIN - 000/06: a: BKS c: MU e: MP This would make record with 000/06 = "a" AND 008/35-37 = "fin" use the BKSFIN framework, and any other record with 000/06 = "a" use BKS, 000/06 = "c" would be MU, and 000/06 = "e" would give MP -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 26866] New: Items table on additem should sort by cn_sort
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '24

10 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26866 Bug ID: 26866 Summary: Items table on additem should sort by cn_sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: - create a bib - add three items with source of classification LCC, call numbers: -- JC43 .G6 1890 -- JC330 .F74 2000 -- JC480 .R63 2006 - on additem.pl, sort the items table by "Full call number" - notice items are order incorrectly, going 330, 43, 480 - use a report to pull the cn_sort values for your 3 items, confirm that ordering by cn_sort in your report correctly orders them 43, 330, 480 We should use cn_sort here to get them in the correct order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 20588] New: Elasticsearch - Apply dataTable on search fields and mapping tables
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '24

10 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20588 Bug ID: 20588 Summary: Elasticsearch - Apply dataTable on search fields and mapping tables Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Apply dataTable on search fields and mapping tables to be able to sort and filter data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 20388] New: Elasticsearch - Ability to add index from UI
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '24

10 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20388 Bug ID: 20388 Summary: Elasticsearch - Ability to add index from UI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Currently indexes only coming from mapping.yaml. We need to add some using UI (admin/searchengine/elasticsearch/mappings.pl) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 213

[Bug 23840] New: Overlap of top menu
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23840 Bug ID: 23840 Summary: Overlap of top menu Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: fraktik(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 94403 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=94403&action=ed… picture of graphical overlap of top menu For more then one or two SHORT links in IntranetNav variable in Staff Client Preferences (Appearance) and variable window size there is some interval of page width, when an visual overlap between top menu from the right one (user/library related & Help) to the left one(general) happen. In previous version this do not happen (right menu jump one row down instead). Examples of both is shown in an attachment: 19.05: https://i.imgur.com/4aVrcRt.png 18.11: https://i.imgur.com/y4iJeMD.png -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 26633] New: Add advanced editor for transfer limits
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26633 Bug ID: 26633 Summary: Add advanced editor for transfer limits Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The current transfer limits editor works great for Koha instances with small numbers of branches. However, for consortiums with dozens or even hundreds of libraries, the editor does not work well or effectively. We should provide an "advanced" editor displays all to/from library combinations in a grid and allows them to be edited in a manner somewhat similar to the transport cost matrix editor. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 104

[Bug 18194] New: Elasticsearch should be able to add new indexes
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18194 Bug ID: 18194 Summary: Elasticsearch should be able to add new indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 14899 added a configuration page for elastic search indexes. It would be nice to allow for the addition/deletion of indexes as well as their configuration -- You are receiving this mail because: You are watching all bug changes.

1 4