December 2024 - Koha-bugs - lists.koha-community.org

[Bug 37430] New: (Bug 33407 follow-up) ISBD punctuation removal in ES searches
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37430 Bug ID: 37430 Summary: (Bug 33407 follow-up) ISBD punctuation removal in ES searches Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching - Elasticsearch Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: nick(a)bywatersolutions.com Depends on: 33407 Tiny adjustment for very special and malicious cases needed in the Koha::SearchEngine::Elasticsearch::QueryBuilder::clean_search_term. Extended unit tests should be added following Nick's suggestions in Bug 33407 discussion. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33407 [Bug 33407] With ES and QueryAutoTruncate on, a search containing ISBD punctuation returns no results -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 33407] New: With ES and QueryAutoTruncate on, a search containing ISBD punctuation returns no results
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33407 Bug ID: 33407 Summary: With ES and QueryAutoTruncate on, a search containing ISBD punctuation returns no results Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com With ES and QueryAutoTruncate on, a search with punctuation surrounded by spaces (like ISBD punctuation copied from other catalogue or bibliography) returns no results. E.g.: in a search for "Maria Stuart ; Die Jungfrau von Orleans / Schiller" (coded in record as 245 10 $a Maria Stuart ; $b Die Jungfrau von Orleans / $c Schiller) -- both semicolon and slash cause problems. One had to remove them manually to get results which is not what is desired. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 26479] New: Self checkout: option for returning items is missing with SCOAllowCheckin
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26479 Bug ID: 26479 Summary: Self checkout: option for returning items is missing with SCOAllowCheckin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When returning items from the self checkout screens is allowed, there is no link to do so in GUI. It looks like the table of checkouts should have a return item link in the manual, but there is only a renew link visible https://koha-community.org/manual/20.05/en/html/circulation.html#self-check… To test: - Activate WebBasedSelfCheck and SCOAllowCheckin - Go to the self checkout in OPAC - Check an item out - Verify there is only a renew link and no visible option to return it -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 23875] New: Elasticsearch - ES - When sorting by score we should provide a tiebreaker
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23875 Bug ID: 23875 Summary: Elasticsearch - ES - When sorting by score we should provide a tiebreaker Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com In ES if we sort by 'relevance' we actually don't pass anything to ES and results are ordered by score. When doing a search limiting only by collection or type, the scores are all the same. This is fine, except that editing any record will then cause a reordering of the results, even though it won't affect the score. We should provide a tie-breaker in the case of equal sort scores -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 38032] New: Make bulkmarcimport.pl -a respect embedded authtypecode
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38032 Bug ID: 38032 Summary: Make bulkmarcimport.pl -a respect embedded authtypecode Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org I have generated some authority records from some data exported from another ILS, and am trying to import them into Koha. I have put an authtypecode in 942$a, and thought that would be enough to get them into the categories I want. But it seems C4::AuthoritiesMarc::GuessAuthTypeCode() is overruling me, and assigning authorities to authtypecodes based on the fields present in the records. It would be nice if there was at least a command line switch to say 942$a should be respected. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 38718] New: main container wrapper
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38718 Bug ID: 38718 Summary: main container wrapper Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org On bug 38664 we are going to tidy the template file and so indent them properly. Most of our templates have the following structure: <div class="main container-fluid"> <div class="row"> <div class="col-md-10 order-md-2 order-sm-1"> <main> [% INCLUDE 'messages.inc' %]  </main> </div> <div class="col-md-2 order-sm-2 order-md-1"> <aside> </aside> </div> </div> </div> It would be useful to have a WRAPPER to avoid: * errors (sometimes we see the two divs with the same order: sm-2) * inconsistencies * 4 indentation blocks (will be replaced with a single one) -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 33017] New: SQL comments are not fully ignoring runtime parameters
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '25

07 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33017 Bug ID: 33017 Summary: SQL comments are not fully ignoring runtime parameters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org If you use SQL comments in a report, runtime parameters are not fully ignored. For example: /* WHERE branchcode = <<Library|branches>> */ When the report runs, it correctly ignores this parameter, but it still requires the a library branch to be selected before the report can run. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 30719] New: ILL should provide the ability to create batch requests
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '25

07 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30719 Bug ID: 30719 Summary: ILL should provide the ability to create batch requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Some interlibrary loan providers, for example Reprints Desk, allow for ILL requests to be submitted in batches. In the Reprints Desk case, a batch is created with the supplier, then requests are then submitted including the batch ID. Obviously, this workflow may differ according to supplier and these differences should be abstracted away into the supplier backend. For core Koha, we should provide the ability for it to recognise if a given backend can process batch requests. If so, we should provide an interface for creating and manipulating batches within Koha, then submitting a batch to the supplier. It should also be possible to view all batches and the contents of a given batch. The funding institution has defined the following workflow for creating and populating batches: - A encapsulating "batch" is created with a name and a requesting borrower - Requests are added to a batch via two methods: - In bulk: - A form which allows the user to paste in a collection of identifiers, such as DOI / PMID etc. - For each of these identifiers: - The request metadata should be populated via API queries to metadata suppliers, for example, PubMed API or LibKey/Browzine. This behaviour is governed by the presence of appropriate plugins. - (Optional) Once the metadata is populated for an item, we check for item availability via any installed ILL availability plugins - Individually: - A regular ILL request form, requests are added to the batch -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 194

[Bug 38261] New: JS warning "unreachable code after return statement"
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '25

07 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38261 Bug ID: 38261 Summary: JS warning "unreachable code after return statement" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com 792 function getTitle(meta) { 793 if (meta.article_title && meta.article_title.length > 0) { 794 return 'article_title'; 795 return { 796 prop: 'article_title', 797 value: meta.article_title 798 }; 799 } else if (meta.title && meta.title.length > 0) { 800 return 'title'; 801 return { 802 prop: 'title', 803 value: meta.title 804 }; 805 } 806 }; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37033] New: Plugin intranet_js won't load in Cart popup (intranet-bottom.inc missing)
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '25

07 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37033 Bug ID: 37033 Summary: Plugin intranet_js won't load in Cart popup (intranet-bottom.inc missing) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We need to make a modification to the cart view and tried to create a plugin that injects javascript to the cart view. It won't get applied to cgi-bin/koha/basket/basket.pl since it's template is missing it's [% INCLUDE 'intranet-bottom.inc' %] which loads the plugin subs called intranet_js to the browser. I added the code to basket.tt and now the plugin's intranet_js gets applied to the view. This issue may occur in similar popup views elsewhere in the Koha intranet too, where we have decided not to include the intranet-bottom.inc to the browser view. Should this ticket be made a generic one dealing with all similar occurences throughout Koha intranet (Z39.50 search for example)? Is there any downside for having the bottom bar in these views? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16