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

[Bug 34203] New: CollapseFieldsPatronAddForm should have an option to check if fields are empty
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '23

14 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34203 Bug ID: 34203 Summary: CollapseFieldsPatronAddForm should have an option to check if fields are empty Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is a great feature, but would be even better if we had the option to ignore collapsing a section if that section has information in it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 31661] New: libcache-memcached-fast-safe-perl not available on ARM64
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '23

13 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31661 Bug ID: 31661 Summary: libcache-memcached-fast-safe-perl not available on ARM64 Change sponsored?: --- Product: Koha Version: 22.05 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: notifications(a)perceptisys.co.uk QA Contact: testopia(a)bugs.koha-community.org I have just attempted to install Koha on a Raspberry Pi 4 (8Gb) running Ubuntu 22.04 following your instructions at https://wiki.koha-community.org/wiki/Debian Reviewing your koha-common package requirements in aptitude, I find that all the required packages are "satisfiable" *except* `libcache-memcached-fast-safe-perl` which is marked as "unavailable". Following the same instructions (via a bash script) on an Intel based laptop (running Ubuntu 22.04) shows all required packages are "satisfiable". This suggests that you are missing the ARM64 version of `libcache-memcached-fast-safe-perl`. --------- For a *small* (school) library, a Raspberry Pi 4 (8GB) should be sufficient, and more importantly inexpensive and greener to run 24/7. --------- -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31868] New: Add search options for searchable patron attributes to pull down list
by bugzilla-daemon＠bugs.koha-community.org 11 Aug '23

11 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31868 Bug ID: 31868 Summary: Add search options for searchable patron attributes to pull down list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com, michaela.sieber(a)kit.edu When a patron attribute is marked as searchable, it can be searched within the Standard search option, but this is not really transparent and sometimes not so helpful when you have multiple YES_NO options for example. It would be nice if any patron attribute marked searchable would automatically show as a search option in the pull down list. We already do this with other additionally configurable fields in serials and acq, so this would also make things more consistent. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 33671] New: Database update 22.06.00.048 breaks when there are borrower_relationships.guarantor_id with NULL
by bugzilla-daemon＠bugs.koha-community.org 11 Aug '23

11 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33671 Bug ID: 33671 Summary: Database update 22.06.00.048 breaks when there are borrower_relationships.guarantor_id with NULL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) 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 Depends on: 30472 We've had 2 reports of this database update breaking the update on bug 30472. The database update altered the table without checking/dealing with existing NULL values: PabloAB: Upgrading to 22.11.02-1 from an updated 22.05 on a Debian 11: Upgrade to 22.06.00.048 [18:33:27]: Bug 30472 - borrower_relationships.guarantor_id NOT NULL ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change column 'guarantor_id': used in a foreign key constraint 'r_guarantor' at /usr/share/koha/lib/C4/Installer.pm line 739 Maybe the same issue as on bug 32399? ------ Mona Panchaud: Hello. While upgrading from 22.05 to 22.11 we are running into the following problem that is related to this change: "Upgrade to 22.06.00.048 [20:19:53]: Bug 30472 - borrower_relationships.guarantor_id NOT NULL ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change column 'guarantor_id': used in a foreign key constraint 'r_guarantor' at /usr/share/koha/lib/C4/Installer.pm line 743" Is there any workaround? What can we do to get the upgrade working? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30472 [Bug 30472] Field borrower_relationships.guarantor_id should be marked as NOT NULL -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 29333] New: Importing UNIMARC authorities in MARCXML UTF-8 breaks the encoding
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '23

10 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29333 Bug ID: 29333 Summary: Importing UNIMARC authorities in MARCXML UTF-8 breaks the encoding Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Related to bug 17754 MARC::Record and MARC::File::* modules sometimes use the position 09 of the leader to detect encoding. A blank character means 'MARC-8' while an 'a' means 'UTF-8'. In a UNIMARC authority this position is used to store the authority type (see https://www.transition-bibliographique.fr/wp-content/uploads/2021/02/AIntro… [FR]). In this case, 'a' means 'Personal Name'. The result is that the import will succeed for a Personal Name authority, but it will fail for all other authority types. Steps to reproduce: 0. Be sure to have a Koha UNIMARC instance. 1. Download the MARCXML for "Honoré de Balzac" curl -o balzac.marcxml https://www.idref.fr/02670305X.xml 2. Verify that it's encoded in UTF-8 file balzac.marcxml (should output "balzac.marcxml: XML 1.0 document, UTF-8 Unicode text") 3. Go to Tools » Stage MARC for import and import balzac.marcxml with the following settings: Record type: Authority Character encoding: UTF-8 Format: MARCXML Do not touch the other settings 4. Once imported, go to the staged MARC management tool and find your batch. Click on the authority title "Balzac Honoré de 1799-1850" to show the MARC inside a modal window. There should be no encoding issue. 5. Write down the imported record id (the number in column '#') and go to the MARC authority editor. Replace all URL parameters by 'breedingid=THE_ID_YOU_WROTE_DOWN' The URL should look like this: /cgi-bin/koha/authorities/authorities.pl?breedingid=198 You should see no encoding issues. Do not save the record. 6. Import the batch into the catalog. Verify that the authority record has no encoding issue. 7. Now download the MARCXML for "Athènes (Grèce)" curl -o athènes.marcxml https://www.idref.fr/027290530.xml 8. Repeat steps 2 to 6 using athènes.marcxml file. At steps 4 and 5 you should see encoding issues and that the position 9 of the leader was rewritten from 'c' to 'a'. Strangely, importing this batch fix the encoding issue, but we still lose the information in position 09 of the leader -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 34248] New: Curbside pickup times should follow TimeFormat preference
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '23

10 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34248 Bug ID: 34248 Summary: Curbside pickup times should follow TimeFormat preference 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: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When scheduling a pickup at a specific time, the time is in 24-hour format. It would make sense for the time slot selection formatting to follow the TimeFormat preference. This can be observed by: -Enabling the CurbsidePickup syspref -Configuring a branch with time slots at or beyond 13:00 (1:00 PM) -Switching the TimeFormat syspref to 12 hour format -Scheduling a pickup at that branch (time slots remain in 24-hour format) This is especially confusing for patrons who are accustomed to the 12-hour format choosing to schedule pickups themselves in the OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 33397] New: Adding custom authorized values for bsort1/bsort2 can result in data loss
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '23

10 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33397 Bug ID: 33397 Summary: Adding custom authorized values for bsort1/bsort2 can result in data loss Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 To recreate: 1. Without having custom authorized values for bsort1/bsort2 create of edit some patrons with sort1 and sort2 values in their borrower information. 2. sort1/sort2 are free text fields 3. Create a new bsort1 and bsort2 authorized values. 4. Go back to the patron record and notice the free text field is now a dropdown with the newly create authorized values. 5. Save the patron record without changing anything. 6. The initial values for sort1/sort2 are now empty. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 30981] New: Add option to configure preferred pronouns as a pull down
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '23

10 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30981 Bug ID: 30981 Summary: Add option to configure preferred pronouns as a pull down Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com This could work just like bsort1 and bsort2 for the statistic fields. We add a AV category that is emtpy, but once it is filled in, the pronouns field will show up as a pull down. While it's empty, it's a free text field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 32554] New: Test prediction pattern does not consider subscription length (uses only subscription end date)
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '23

10 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32554 Bug ID: 32554 Summary: Test prediction pattern does not consider subscription length (uses only subscription end date) 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When creating a new serial subscription, it used to be that we could enter either a subscription length (number of issues, months or weeks) OR a subscription end date. When we would test the prediction pattern, it would show the right number of issues based on one of these values. Now it seems that if we only enter a number of issues for the subscription length and test the prediction pattern, not only does it tell us we're not being consistent with our end date (I thought it was optional?) but it also doesn't show the correct number of issues. To test: 1. For this, I created my own record, but you can skip this step and use any existing record 1.1. Go to Cataloging 1.2. Click on New record 1.3. Fill out the manadatory fields (in MARC21, typically 000, 003, 005, 008, 040$c, 245$a and 942$c) 1.4. Click Save 1.5. Note the record number, do not create an item 2. Create a serial subscription 2.1. Go to Serials 2.2. Click on New subscription 2.3. Enter the record number 2.4. Click Next (and confirm you're not using a vendor) 2.5. Fill out the second form as follows - First issue publication date: 2023-01-01 - Frequency: 1/month - Subscription length: issues 24 - Subscription start date: 2023-01-01 - Subscription end date: leave empty - Numbering pattern: Number - Locale: leave empty - Begins with: 42 - Inner counter: leave empty 2.6. Click on Test prediction pattern --> Note there is a message saying "End date is not consistent with subscription length." even if, normally, only one is needed --> Only the issues until today are displayed (in my case, only the January 2023 issue), even if we said our subscription was for 24 issues There is no problem if we enter a subscription end date. This means either the subscription length problem is a bug, or end date is now mandatory and should be displayed in red like other mandatory fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 34442] New: Info around CSV export profiles edition not correct for sql option
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '23

10 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34442 Bug ID: 34442 Summary: Info around CSV export profiles edition not correct for sql option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hello everyone, When you edit a CSV export profile, we can have a few examples to see how it works, such as. "For late issue claims, you can use data from the following tables: serial, subscription, biblio, biblioitems and aqbookseller". But there's an error here, if I want to add subscription.callnumber for example (or id etc...) it doesn't work... Perhaps we can correct this description a little? But how? Just to say that there are only these fields you can include: [SQL query extracted from the GetLateOrMissingIssues function] "serialid, aqbooksellerid, name, biblio.title, biblioitems.issn, planneddate, serialseq, serial.status, serial.subscriptionid, claimdate, claims_count, subscription.branchcode, serial.publisheddate" This may be a bit longer, but I'd rather ask the community what's the best way to be clear on this point. Thanks for your feedback -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3