January 2025 - Koha-bugs - lists.koha-community.org

[Bug 37304] New: The Created by filter in Acquisitions advanced orders search always shows zero results
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37304 Bug ID: 37304 Summary: The Created by filter in Acquisitions advanced orders search always shows zero results Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In the Order Search screen, the Basket Created By field results in 0 (zero) hits regardless of which member of staff is selected. To recreate: Go to Acquisitions then to Advanced Search from the left hand menu options In the Basket Created By field begin entering name of staff member who has baskets created in the system Select name from the suggestions dropdown, name is added beneath the search box Click Search Even though there are baskets created by this user zero results are returned with the message "Your search returned no results." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 37403] New: Wrong progress quantity in job details when staging records with match check
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37403 Bug ID: 37403 Summary: Wrong progress quantity in job details when staging records with match check Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging 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: m.de.rooy(a)rijksmuseum.nl I noticed that when you stage MARC records and do a match check ("Look for existing records in catalog?"), the progress quantity in the Details of the job is wrong. To recreate: 1. Go to Cataloging > Stage records for import 2. Choose a file with bibliographic records and click Upload file 3. In "Look for existing records in catalog?" choose a record matching rule (e.g. ISBN) 4. Click Stage for import 5. Click View detail of the enqueued job --> Progress show 2/1 I've also seen 4/2 and 12500/1000 (it's not always double) The number seems ok if you don't check for existing records. This has been the case at least since 23.05. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 37606] New: Export module should replace double quotes with simple quotes
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37606 Bug ID: 37606 Summary: Export module should replace double quotes with simple quotes Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When exporting as csv, the exporter does not check the presence of double quote in the fields. Hence, if there is one double quote, the csv is broken. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 38177] New: ERM - HoldingsIQ pagination does not work
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38177 Bug ID: 38177 Summary: ERM - HoldingsIQ pagination does not work Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jeremy.evans(a)ukhsa.gov.uk, jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com To reproduce: 1) Setup all the system preferences in ERM: <staff_url>/cgi-bin/koha/admin/preferences.pl?tab=erm 2) Enable EBSCO in ERMProviders. Set the ERMProviderEbscoApiKey and ERMProviderEbscoCustomerID prefs. 3) Do a search that returns more than 20 records. Click on a page other than 1. Notice the records do not change (Page is the same). -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 37836] New: Prevent submitting empty barcodes in Self check-in
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37836 Bug ID: 37836 Summary: Prevent submitting empty barcodes in Self check-in Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Circulation Assignee: bosse(a)gustavsson.one Reporter: bosse(a)gustavsson.one QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When pressing "Submit" on the "Self Check-in" page with the barcode field left empty, the barcode element still appears in the list. To recreate this bug: Enable the "SelfCheckInModule". Open the page and press the "Submit" button. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 37505] New: Statistical patrons don't display information about item status if item wasn't checked out
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37505 Bug ID: 37505 Summary: Statistical patrons don't display information about item status if item wasn't checked out Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an item is scanned with a statistical patron, the the page is meant to display an alert if the item has any current checkouts, holds, recalls, return claims, or lost/withdrawn status (as well as automatically ending checkouts and clearing lost statuses). However, the page is not currently displaying those alerts unless the item has a current checkout, even though the other statuses are unrelated to whether the item is currently checked out or not. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 38062] New: If not using RecordLocalUseOnReturn, "Return" statistic is recorded regardless of whether item was checked out in the first place
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38062 Bug ID: 38062 Summary: If not using RecordLocalUseOnReturn, "Return" statistic is recorded regardless of whether item was checked out in the first place Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: In Discussion Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Checking in a book will always add a "return" stat to the statistics table, even if the book was not checked out in the first place. The only exception is if a "localuse" stat is recorded instead (when RecordLocalUseOnReturn is enabled). It seems to me that a return should only be recorded if the item was actually checked out in the first place. This has been the behavior for a while, though, so we should get feedback from libraries before changing it. One thing that has been mentioned is that the "return" statistic can be useful for capturing things like an item being scanned to fill an on-shelf hold. Should we make a new statistics type for local handling like that, which some libraries might want to track but others might not want to count as a circulation stat? Use action_logs to track that sort of thing instead? See also bug 9717 for a similar discussion regarding the "localuse" stat -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 18273] New: Bulkmarcimport inserts authority duplicates
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18273 Bug ID: 18273 Summary: Bulkmarcimport inserts authority duplicates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When importing authorities through bulkmarcimport with the -match option, there are 3 possibilities: 1) An existing authority has been found in koha according to the -match criteria. The authority is replaced if needed (005 are checked first). This is ok. 2) No authority is found in koha according to the -match criteria. The authority is inserted. This is also ok. 3) Multiple authorities have been found in koha according to the -match criteria. The authority is inserted. => Is this the expected behavior? As the -match criteria is used for deduping, the existing authorities are very likely to be already existing duplicates. Do we really want to add another one? My feeling is that in this case, the authority should NOT be inserted. Can I have your opinion on this? -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 35769] New: Untranslatable string in requeste.tt
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35769 Bug ID: 35769 Summary: Untranslatable string in requeste.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Created attachment 160797 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=160797&action=e… Screenshot of the untranslatable pop up There is a untranslatable string In requeste.tt: "Please make sure all selected titles have a pickup location set" (line 1552). See the attachment. The string shows up when you are making a multi-hold and leave one of the titles without pick-up place and then try to save the holds. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 37787] New: Undocument koha-worker --queue elastic_index
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37787 Bug ID: 37787 Summary: Undocument koha-worker --queue elastic_index Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Documentation for koha-worker --queue elastic_index was added in Bug 36009, and as far as I can tell, that was the right thing to do at the time. Then koha-es-indexer was added in Bug 33108, and after that running both koha-es-indexer and "koha-worker --queue elastic_index" at the same time leads to problems, like only every other elastic_index job getting processed. We should remove the mention of "--queue elastic_index" from the koha-worker docs. (And maybe add a note that only koha-es-indexer should be run.) koha-es-indexer has been introduced to 23.05.00 and 22.11.06, so a fix should not be backported to older versions than that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20