- Koha - lists.katipo.co.nz

Elasticsearch: [query_string] cannot use [fields] parameter in conjunction with [default_field]; in Koha 19.05 with Elasticsearch 6.
by Simon Hohl 26 Feb '22

26 Feb '22

Hello everybody, in light of the Log4j debacle last year, I am currently trying to update Elasticsearch to the current version of 6, from our old version 5. I read in the wiki (https://wiki.koha-community.org/wiki/Elasticsearch) that > Note: As of 20.05.00, 19.11.05 and 19.05.10 releases, we recommend > Elasticsearch 6.x We are at 19.05.17. I updated accordingly and did a complete re-index, but I get the appended error for searches. Did I miss something? An upgrade to the current Koha version is planned for later this year, but will require more testing to make sure all our local changes get re-applied after upgrading via package. Kind regards Simon > [2022-02-17T07:50:10,007][DEBUG][o.e.a.s.TransportSearchAction] > [vgY4zBy] All shards failed for phase: [query] > org.elasticsearch.index.query.QueryShardException: failed to create > query: { > "query_string" : { > "query" : "(_all:A*)", > "default_field" : "_all", > "fields" : [ > "_all^1.0" > ], > "type" : "best_fields", > "default_operator" : "and", > "max_determinized_states" : 10000, > "enable_position_increments" : true, > "fuzziness" : "AUTO", > "fuzzy_prefix_length" : 0, > "fuzzy_max_expansions" : 50, > "phrase_slop" : 0, > "analyze_wildcard" : true, > "lenient" : true, > "escape" : false, > "auto_generate_synonyms_phrase_query" : true, > "fuzzy_transpositions" : true, > "boost" : 1.0 > } > } > at > org.elasticsearch.index.query.QueryShardContext.toQuery(QueryShardContext.java:335) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.index.query.QueryShardContext.toQuery(QueryShardContext.java:318) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService.parseSource(SearchService.java:806) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService.createContext(SearchService.java:653) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:604) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:388) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService.access$100(SearchService.java:127) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService$2.onResponse(SearchService.java:360) > [elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService$2.onResponse(SearchService.java:356) > [elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.search.SearchService$4.doRun(SearchService.java:1129) > [elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) > [elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:41) > [elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:778) > [elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) > [elasticsearch-6.8.23.jar:6.8.23] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [?:1.8.0_322] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [?:1.8.0_322] > at java.lang.Thread.run(Thread.java:750) [?:1.8.0_322] > Caused by: org.elasticsearch.index.query.QueryValidationException: > Validation Failed: 1: [query_string] cannot use [fields] parameter in > conjunction with [default_field]; > at > org.elasticsearch.index.query.QueryValidationException.addValidationError(QueryValidationException.java:43) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.index.query.AbstractQueryBuilder.addValidationError(AbstractQueryBuilder.java:183) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.index.query.QueryStringQueryBuilder.doToQuery(QueryStringQueryBuilder.java:977) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.index.query.AbstractQueryBuilder.toQuery(AbstractQueryBuilder.java:106) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.index.query.QueryShardContext.lambda$toQuery$2(QueryShardContext.java:319) > ~[elasticsearch-6.8.23.jar:6.8.23] > at > org.elasticsearch.index.query.QueryShardContext.toQuery(QueryShardContext.java:331) > ~[elasticsearch-6.8.23.jar:6.8.23] > ... 16 more

2 1

Migrate from one framework to another framework
by Pedro Miguel Nunes Ferreira 26 Feb '22

26 Feb '22

Hello, is it possible to migrate all records from an incomplete framework to a more complete framework ? I have ~400 records in the framework CD and i want to migrate all the records to another framework more complete called AUDIO Thanks --

2 1

Koha 21.11.03 released!
by Kyle Hall 25 Feb '22

25 Feb '22

The Koha community is proud to announce the release of version 21.11.03. Thank you very much to everyone involved in this release! The release notes can be found at https://koha-community.org/koha-21-11-03-released/ Kyl*e*

1 0

Koha Installation Manual Needed/2022-Reg.
by Sebastian R 25 Feb '22

25 Feb '22

Dear All, Greetings Always... Kindly share the full installation link and the manual. Thanks & Regards, R.Seba.

1 0

Koha 19.11.26 released
by Wainui Witika-Park 25 Feb '22

25 Feb '22

Kia ora koutou/Hello everyone! The Koha community is proud to announce the release of version 19.11.26. The full release notes can be found at: https://koha-community.org/koha-19-11-26-released/ Thank you to everyone involved! Cheers, Wainui Witika-Park (she/her)

1 0

Lost ISBD File Yields BOOM
by Charles Kelley 25 Feb '22

25 Feb '22

Hi, all! We encountered an ISBD view problem: The file turns up lost. Here are the conditions that we have identified: - In OPACHiddenItemsException, the patron type is not listed as an excepted type. - The patron looks for a work in our collection through our catalog. We own a copy, so it isn't a matter that we don't own the title. Instead, 942 ‡n = "1". Method of search does not matter: author, title, subject, word, call number all work fine. - The record is listed in the OPAC results. - The patron happens to select the version whose 942 ‡n = "1". The record, in Normal view, is rendered in the window. All three view tabs (Normal view, MARC view, ISBD view) are listed. - The patron clicks on ISBD view. BOOM! Here's the output from Koha. Software error: The method Koha::Item->lost is not covered by tests! Trace begun at /usr/share/koha/lib/Koha/Object.pm line 780 Koha::Object::AUTOLOAD('Koha::Item=HASH(0x5637bb245f10)') called at /usr/share/koha/lib/Koha/Item.pm line 478 Koha::Item::__ANON__ at /usr/share/koha/lib/Koha/Item.pm line 478 Koha::Item::hidden_in_opac('Koha::Item=HASH(0x5637bb245f10)', 'HASH(0x5637bb191908)') called at /usr/share/koha/lib/Koha/Biblio.pm line 258 Koha::Biblio::__ANON__ at /usr/share/koha/lib/Koha/Biblio.pm line 258 Koha::Biblio::hidden_in_opac('Koha::Biblio=HASH(0x5637ba6cbfd0)', 'HASH(0x5637bb2460a8)') called at /usr/share/koha/opac/cgi-bin/opac/opac-ISBDdetail.pl line 91 For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. Clicking on MARC view or Normal view does not render the above bug. Pressing the back arrow restores the record's listing and all other OPAC features. If we change the patron's type to one in OPACHiddenItemsException, or if add the patron's type to OPACHiddenItemsException, the ISBD bug vanishes in subsequent searches for the work that produced the error after the changes propagate through Koha. We would say this is a bug, and an extermination request will be filed. -- よろしくお願いします。 -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

1 0

Erro Plugin
by Victor Barroso Oliveira 24 Feb '22

24 Feb '22

Hi, I have an error in the plugin "Koha::Plugin::Carrousel ERRORS Error found whilst attempting to load plugin " How can I resolve this error?

3 3

Koha 20.11.15 released
by Victor Grousset/tuxayo 24 Feb '22

24 Feb '22

Hello! :) The Koha Community is happy to announce the release of Koha 20.11.15 The full release notes can be found at: https://koha-community.org/koha-20-11-15-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo

1 0

Electronic Resource Management for Koha
by Auld, Andrew 24 Feb '22

24 Feb '22

Electronic Resource Management (eRM) and Koha It is becoming increasingly clear that adding an integrated Electronic Resource Management (eRM) module in Koha has become a priority. Many academic libraries and some non academic institutions have a need to manage their electronic resources more effectively and an eRM provides this ability. Competing library systems - now often referred to as ‘Library Services Platforms’ - have eRM functionality built in as core modules alongside all of the other library system modules. For Koha to continue to grow in adoption and use across all library sectors, the addition of an integrated eRM is vital. With this in mind, PTFS Europe, ByWater Solutions and BibLibre are co-funding a focussed development project to build a fully integrated eRM module for Koha. The specification has been developed collaboratively by these three organisations and as well as sponsoring the development costs of the project, each organisation is committing resources to ensure that the module is able to be added to the community releases of Koha in line with the community’s quality and security assurance requirements. Though the first version will be highly functional, there will no doubt be further iterations of development of the eRM module that will follow and all three organisations will welcome the contributions of any members of the community that are interested in the ongoing enhancement of Koha eRM. Jonathan Druart has been commissioned as lead developer on the project supported by a team of people from the three partner organisations. Jonathan Field of PTFS Europe is liaising between the project partners so if you have any questions he would welcome your thoughts and contributions on jonathan.field(a)ptfs-europe.com *Andrew Auld* <https://www.ptfs-europe.com/> Commercial Director *Phone:* +44 (0) 1483 378728 ext. 1010 *Mobile:* +44 (0) 7811 370 104 *Email:* andrew.auld(a)ptfs-europe.com www.ptfs-europe.com *Sign up for our newsletters here <http://eepurl.com/dPjjkn> or by scanning the QR code* Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

1 0

Equals sign in a macro?
by Bales (US), Tasha R 23 Feb '22

23 Feb '22

I would like to create a Macro that enters the base of a URL. However, I find that I cannot execute the macro due to errors caused by the use of an equals sign. Curly braces also seem to cause a problem. I played around trying to see if I could escape the problem characters, but didn't get anywhere. I also tried substituting in "=" and "=" , which I think are HTML codes for "=", just in case, but both seem to be ignored and don't make it into the 856 that is created. Anyone know of a way around this? Thanks! Tasha Bales Enterprise Services http://isesi.web.boeing.com/

3 2