October 2023 - Koha-bugs - lists.koha-community.org

[Bug 23241] New: Does misc/bin/koha-index-daemon-ctl.sh still belong in community koha?
by bugzilla-daemon＠bugs.koha-community.org 24 May '24

24 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23241 Bug ID: 23241 Summary: Does misc/bin/koha-index-daemon-ctl.sh still belong in community koha? Change sponsored?: --- Product: Koha Version: unspecified 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We have had a daemon mode in rebuild_zebra.pl for a long time and have been using that as the default indexing daemon for years.. Should we deprecate the above script to prevent confusion for new users where indexing should just work out of the box without the need for installing external dependancies. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 34032] New: Holds expirationdate left blank if waiting status is reverted
by bugzilla-daemon＠bugs.koha-community.org 24 May '24

24 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34032 Bug ID: 34032 Summary: Holds expirationdate left blank if waiting status is reverted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Pretty much what summary says. To reproduce: 1) Make sure you have DefaultHoldExpirationdate syspref enabled. 2) Find hold with status "Waiting". 3) Revert waiting status. => Note that hold has no expiration date set. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 30898] New: Elasticsearch/Indexer.t fails on 'No nodes are available'
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30898 Bug ID: 30898 Summary: Elasticsearch/Indexer.t fails on 'No nodes are available' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This could be expected when you only run Zebra.. But it would be nice to catch this situation. t/db_dependent/Koha/SearchEngine/Elasticsearch/Indexer.t .. 2/4 # Failed test 'create_index() tests' # at t/db_dependent/Koha/SearchEngine/Elasticsearch/Indexer.t line 88. [NoNodes] ** No nodes are available: [http://localhost:9200] called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/Koha/SearchEngine/Elasticsearch/Indexer.pm line 403.# Looks like your test exited with 11 just after 2. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 34328] New: Scottish Gaelic is missing from the language_rfc4646_to_iso639 table
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34328 Bug ID: 34328 Summary: Scottish Gaelic is missing from the language_rfc4646_to_iso639 table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org For languages to appear in the advanced search options they must appear in the language_rfc4646_to_iso639 table. Scottish Gaelic is missing, iso639 code gd and rfc4646 code gla. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 35093] New: ILL table is broken
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35093 Bug ID: 35093 Summary: ILL table is broken 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: pedro.amorim(a)ptfs-europe.com CC: pedro.amorim(a)ptfs-europe.com Depends on: 30719 Caused by last minute refactoring of 30719. To reproduce: Install FreeForm and enable ILLmodule, run: bash <(curl -s https://raw.githubusercontent.com/ammopt/koha-ill-dev/master/start-ill-dev.…) Visit /cgi-bin/koha/ill/ill-requests.pl BOOM Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30719 [Bug 30719] ILL should provide the ability to create batch requests -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 30136] New: Add back to top button when scrolling
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30136 Bug ID: 30136 Summary: Add back to top button when scrolling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Like in many websites, when scrolling down the page make a button appear to go back to top. This can be very useful specially in search results page. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 24143] New: buildQuery should disable Query* on identifier search
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24143 Bug ID: 24143 Summary: buildQuery should disable Query* on identifier search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Currently, QueryWeightFields, QueryFuzzy, QueryStemming, QueryAutoTruncate are disabled in buildQuery in several cases: - Date of Publication - Date of Acquisition - ISBN,ISSN,Standard Number Those modifiers should also be disabled when searching on identifiers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 32420] New: Set focus for cursor to barcode input box in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32420 Bug ID: 32420 Summary: Set focus for cursor to barcode input box in batch item modification Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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: gmcharlt(a)gmail.com It would be great if the focus would be automatically set to the barcode input box in the batch item modification screen. Right now, the focus is on the catalogue search. But if you went to that page, you went to batch edit item. To test: 1. Go to Cataloging > Batch item modification --> Notice that the cursor is set to the 'Search catalog' box at the top of the page, it would be better to have it in the barcode input box under 'Scan items one by one' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 30687] New: Unable to override hold policy if no pickup locations are available
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30687 Bug ID: 30687 Summary: Unable to override hold policy if no pickup locations are available 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Set the following settings: Reserves policy by item type for Branch A: Item type: BK Reserve policy: From home library Reserve pickup library match: any library Return policy: Item returns home AllowHoldPolicyOverride: Allow Create a biblio with an item: Item home library: Branch A Item type: BK Log in to the staff client as a Patron that belongs to Branch B. Go to place a hold on the Biblio. Notice that you are blocked because there is no valid pickup location, and unable to override it. Previously we could override this restriction, but we now can't. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52

[Bug 31185] New: Link authorities automatically doesn't detect duplicate authorities
by bugzilla-daemon＠bugs.koha-community.org 23 May '24

23 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31185 Bug ID: 31185 Summary: Link authorities automatically doesn't detect duplicate authorities 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: adolfo.rodriguez(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When cataloging a bibliographic record, the template addbiblio.tt has a code to show that there is more than one local match for the entry point (MULTIPLE_MATCH) but the function LinkBibHeadingsToAuthorities never returns that code. This means that when the authority you are looking for is duplicated and you click the "Link authorities automatically", you obtain the following message "No matching authority found." instead of "More than one local match found. Possibly a duplicate authority!" This gives the false impression that the authority doesn't exist. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38