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

[Bug 7335] Allow custom parameters for sorting in SQL reports
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '23

10 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7335 Katie Bliss <kebliss(a)dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss(a)dmpl.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[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

[Bug 34512] New: "Changed" flag and Reset link missing when changing matching rules in manage marc import page
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '23

09 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34512 Bug ID: 34512 Summary: "Changed" flag and Reset link missing when changing matching rules in manage marc import page 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 154342 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=154342&action=e… Sample MARC21 file When importing MARC records, it's possible to change the matching rule after the records are staged. Before, if we changed the option, there was a "Changed" flag with a "Reset" link next to the changed option. It seems the flag is still in the .tt file, but it doesn't show on the screen in the staff interface. To recreate: 1. Stage a MARC file (I attached one in case you don't have any handy) 1.1. Go to Cataloging > Stage records for import 1.2. Choose a marc file and click Upload file 1.3. Click Stage for import 2. View the staged file 2.1. Click "View lot" or go to Cataloging > Managed staged records and click on the file name 3. Change matching options --> No Changed flag or Reset option I checked in 22.05 and Emily checked in 22.11 and the flag is there. In 23.05 and master, the flag doesn't show. In the koha-tmpl/intranet-tmpl/prog/en/modules/tools/manage-marc-import.tt file, around line 83 <span class="change-status">Changed. <a href="#" class="reset" id="reset_new_matcher_id">Reset</a></span> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 30434] New: Convert catalog merge page tabs to Bootstrap
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '23

09 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30434 Bug ID: 30434 Summary: Convert catalog merge page tabs to Bootstrap Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 29226 Continuing the process of phasing out jQueryUI, this patch will replace jQueryUI tabs in the catalog merge template with Bootstrap. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29226 [Bug 29226] OMNIBUS: Replace the use of jQueryUI tabs -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 34510] New: connexion_import_daemon.pl should flush logs to make them more useful / timely
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '23

09 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34510 Bug ID: 34510 Summary: connexion_import_daemon.pl should flush logs to make them more useful / timely Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: JBoyer(a)equinoxOLI.org QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Created attachment 154338 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=154338&action=e… Flush Connexion Import Daemon Log The connexion_import_daemon.pl tool can output logs to the location specified in its config file, but because it uses buffered files (fine) and never flushes the buffer (not fine) the latest log entries are not available until additional records are submitted or the daemon is restarted and the log filehandle closed. The attached patch flushes the log only at the end of the request so the logs are usefully up to date without spamming i/o flushes on every call to log(). To test, pre-patch: 1. Export or locate a single marc record in binary format 2. Setup the connexion_import_daemon.pl as in https://koha-community.org/manual/19.11/en/html/third_party_software.html#o… and take note of the logging location 3. Using Connexion or netcat, send the record to the specified port ( nc koha-host 8000 < recrd.mrc ) 4. Check the logfile configured in 2. It will likely end somewhere in the middle of the "Response: XYZ" output (probably somewhere in the middle of some marcxml) 5. Stop the daemon and verify that the remainder of the response is logged 6. Apply the patch 7. Restart the import daemon and resend the record from step 3 8. This time the full response should be logged as soon as the record is sent -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 10734] Add Publication Date Facet in Searching
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '23

09 Aug '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 --- Comment #13 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- *** Bug 33666 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

1 0