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

[Bug 18637] New: Handle Free Text vendor notes on Edifact Quotes
by bugzilla-daemon＠bugs.koha-community.org 07 Sep '21

07 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18637 Bug ID: 18637 Summary: Handle Free Text vendor notes on Edifact Quotes 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: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org At present we store servicing instructions from the GIR segment of the quote in vendornote field of the order. We dont process the FTX segment (segment 25) of the quote. Some vendors (Ebsco) do use this for important information so we need to expand handling to handle Servicng instructions in GIR segment (both coded and free text) and vendor notes in FTX (both free text and coded ) and be able to include these in the generated orders -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 20492] New: Add missing case for advanced search in _fix_limit_special_cases
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '21

06 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20492 Bug ID: 20492 Summary: Add missing case for advanced search in _fix_limit_special_cases 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: glasklas(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 22524] New: Elasticsearch - Date range in advanced search
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '21

06 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22524 Bug ID: 22524 Summary: Elasticsearch - Date range in advanced search Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca Target Milestone: --- Hi, There is a problem with date range search in advanced search with ES. Search "2001-2010" will give a list of results with 2001-2010 entered in marc field like 260$c2001-2010 or 264$2001-2010 Records with just 2001 in marc field will not be displayed in search results. Maybe it's just a bad configuration in searchengine/elasticsearch/mappings.pl? Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 27499] New: serialsUpdate doesn't create all late issues
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '21

03 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27499 Bug ID: 27499 Summary: serialsUpdate doesn't create all late issues 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Created attachment 115449 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=115449&action=e… New subscription form 2/2 I'm not sure if this is intended behaviour or not. I was trying to get a subscription with lots of late issues to test something. But every time I run serialsUpdate, it only create 1-3 issues instead of all the late issues up to today. To test: 1) Go to Serials 2) Create a subscription for a weekly serial starting 2020-01-01 (I attached a screenshot of my new subscription form 2/2) 3) Go to serial collection -- There should be the first issue of the subscription, 2020-01-01 4) Go to the terminal and run ./misc/cronjobs/serialsUpdate.pl -c -v 5) Go back to the serial collection -- Only the next issue has been created (2020-01-08) I would have expected this to create all missing issues from 2020-01-01 to 2021-01-13. Right now, it only replaces the "Generate next" button. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24019] New: Patron batch modification based on borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '21

03 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24019 Bug ID: 24019 Summary: Patron batch modification based on borrowernumber Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org It would be useful for librarians to be able to batch modify patrons based on a list of borrowernumbers instead of just lists of cardnumbers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 28695] New: Add shelving location column to overdue report (overdue.tt)
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '21

03 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28695 Bug ID: 28695 Summary: Add shelving location column to overdue report (overdue.tt) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some librarians would find it handy if the circulation overdue report (overdue.tt) included a shelving location column. Since the table is already column configurable the new column would need to be added to columns_settings.yml as well -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 27395] New: Add warning to PatronSelfRegistrationDefaultCategory to avoid accidental patron deletion
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '21

02 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27395 Bug ID: 27395 Summary: Add warning to PatronSelfRegistrationDefaultCategory to avoid accidental patron deletion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: System Administration 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 If you have set up the cronjobs for deleting unverified and "unfinished" opac self registrations, a wrong setting in the PatronSelfRegistrationDefaultCategory system preference can lead to accidental deletion of a lot of your patrons. This will happen if you enter one of your regular patron category codes instead of using a specific one for self registrations. It will then delete all patrons that have registere more than PatronSelfRegistrationExpireTemporaryAccountsDelay days ago. This is also a complete deletion, not moving the data to deletedborrowers, making it even harder to fix the mistake. I think it would be great to add a hint or warning about this to the system preference description. It currently reads: Use the patron category code ____ as the default patron category for patrons registered via the OPAC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 28710] New: Formatting values startng with 0 in numbering patterns are confusing to users
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '21

02 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28710 Bug ID: 28710 Summary: Formatting values startng with 0 in numbering patterns are confusing to users Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com When training the advanced numbering patterns in the serials module it's always confusing to the participants that in order to get "January" written out in a pattern, you have to use 0. The same is true for days of the week or seasons. It would be nice if we could change the GUI to either allow using 1 for January and the like (still storing 0) or by offering a pulldown that allows you to select "January" and others depending on the formatting value selected for the pattern. This would have to be an API/Ajax call, that reacts on changes on the formatting pull down and possibly also take the Locale into account. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 28326] New: If ElasticSearch enable is not possible to edit or save records with ' ES reserved charset' like []
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '21

01 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28326 Bug ID: 28326 Summary: If ElasticSearch enable is not possible to edit or save records with ' ES reserved charset' like [] Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es With ElasticSearch enabled it is not possible to create or edit any record with special charset in the title like [] [2021/05/12 06:29:49] [WARN] [Request] ** [hxxxxxx]-[400] [query_shard_exception] Failed to parse query [(host-item:[Romanza appassionata])], with: {"index_uuid":"VlZbj1MfQtWjWgdlnkSUXA","index":"koha_cxxx_biblios"}, called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 96. With vars: {'status_code' => 400,'body' => {'error' => {'grouped' => bless( do{\(my $o = 1)}, 'JSON::PP::Boolean' ),'root_cause' => [{'reason' => 'Failed to parse query [(host-item:[Romanza appassionata])]','index_uuid' => 'VlZbj1MfQtWjWgdlnkSUXA','index' => 'koha_xxxx_biblios','type' => 'query_shard_exception'}],'reason' => 'all shards failed','failed_shards' => [{'reason' => {'index_uuid' => 'VlZbj1MfQtWjWgdlnkSUXA','caused_by' => {'type' => 'parse_exception','caused_by' => {'type' => 'parse_exception','reason' => 'Encountered " <RANGE_GOOP> "appassionata "" at line 1, column 20. Was expecting: "TO" ... '},'reason' => 'Cannot parse \'(host-item:[Romanza appassionata])\': Encountered " <RANGE_GOOP> "appassionata "" at line 1, column 20. Was expecting: "TO" ... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 28738] New: Value builder marc21_linking_section.pl for creating 77x is broken
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '21

29 Aug '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28738 Bug ID: 28738 Summary: Value builder marc21_linking_section.pl for creating 77x is broken Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is quite a neat plugin to create links between records that usually works on all 7xx. But in latest 20.11 (and possibly higher up as my research turned up no changes), this is broken. To test: * link marc21_linking_section.pl as value builder to 773 a or another 77x subfield. * Make sure some of the important subfields like a, t, w, etc. are visible in your framework * Create a new record within that framework within the standard editor * Look for your 7xx subfield with the plugin and click the plugin icon * Search for the record to link * Click on choose * Verify a new window opens and the subfields are not filled in the framework -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12