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

[Bug 35616] New: Add a 'source' field to Koha::Tickets to denote the path taken to report the ticket
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '24

05 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35616 Bug ID: 35616 Summary: Add a 'source' field to Koha::Tickets to denote the path taken to report the ticket Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 This is the foundation for building a more generalised enquiry management option into Koha without losing the existing enquiry starting points. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 35386] New: Renewals via the API are recorded using the branch of the API account used
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35386 Bug ID: 35386 Summary: Renewals via the API are recorded using the branch of the API account used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com When renewing items via the API Koha records the branch of the renewal as the branch of the account that is signed in to the API. For outside service (Aspen, Communico) they may have a single API account that represents all user interactions. While this behavior may not be technically incorrect, it should be configurable like OpacRenewalBranch - allowing the library to decide which branch is recorded in the statistics table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 33036] New: REST API: Merge biblio records
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33036 Bug ID: 33036 Summary: REST API: Merge biblio records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de CC: tomascohen(a)gmail.com Related to the ongoing development of biblios API, what about an endpoint to merge existing biblios including items and acquisition data as the intranet already offers. Possible params should be - biblionumber_to_remain that remains - biblionumber_to_merge which will be merged into biblionumber_to_remain - optional MARCXML that represents the remaining biblio If no MARCXML is delivered the merge should take the MARCXML from the remaining biblio as reference. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 76

[Bug 34082] New: Cut some redundancy in OPAC JavaScript string translations
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34082 Bug ID: 34082 Summary: Cut some redundancy in OPAC JavaScript string translations 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 Depends on: 34035 A few templates in the OPAC still define a string in one place and then use the string in another. If the string is used only once I don't think it's necessary to separate the definition from the use. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34035 [Bug 34035] Move translatable strings out of opac-bottom.inc: Tags -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 35062] New: addbiblio: Allow a framework plugin to add class to prevent submit during ajax call
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35062 Bug ID: 35062 Summary: addbiblio: Allow a framework plugin to add class to prevent submit during ajax call Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I have a plugin that does a REST API call wrapped in an ajax construct: jQuery.ajax({ rest api stuff }).done(function() ...).fail(function() ...); Rapidly clicking Save (while the ajax is triggered by the Change event) lets the plugin shortly show an error before the form submits. Which is obviously undesirable. If we would replace this in addbiblio.tt: var onOption = function () { - return Check(); + if ( $('.plugin-blocks-submit').length==0 ) return Check(); } We can conditionally and temporarily block submittal. When the change event of the plugin fires, I add class plugin-no-submit to the html element involved. In the done and fail functions I remove the class again from the element. This effectively works. While several other approaches in addbiblio failed. (Removing the event handler is just too late.) This is a one-liner that will do the job. On bug 34860 I will still submit a ISBN/ISSN plugin using this class that will demonstrate its use. In the meantime this is a harmless check. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 31335] New: unnecessary holds fetch in serials/routing-preview.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31335 Bug ID: 31335 Summary: unnecessary holds fetch in serials/routing-preview.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The following code is not needed. my $holds = $biblio->current_holds; my $count = $holds->count; while ( my $hold = $holds->next ) { $count-- if $hold->is_waiting; } -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 27291] New: Change datetime format in Zebra logs
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27291 Bug ID: 27291 Summary: Change datetime format in Zebra logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au At the moment, Zebra logs using a dateformat of "hh:mm:ss-DD/MM". For example, "23:16:22-21/12". I propose that we change it to use the dateformat of "%F %T" or "%FT%T". For example, "2020-12-21 23:16:41" or "2020-12-21T23:21:19" It can be done by adding the following option to zebrasrv: -m "%F %T" or -m "%FT%T" While this option doesn't obviously appear in "man zebrasrv", it does appear in "man yaz-ztest" and the manpage for zebrasrv says that zebrasrv has the same options as "yaz-ztest". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 34717] New: Incorrect method call in addorderiso2709.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34717 Bug ID: 34717 Summary: Incorrect method call in addorderiso2709.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org There is an incorrect method usage in the script where GetBudgetByCode is used instead of GetBudget. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 32493] New: Vendor store loads unpaginated vendor list on ERM module main page
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32493 Bug ID: 32493 Summary: Vendor store loads unpaginated vendor list on ERM module main page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: matt.blenkinsop(a)ptfs-europe.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Work is in progress to implement pagination on select dropdowns to avoid loading large lists of data for select options. However, in the ERMMain component there is an API call to fetch all the vendors and then load these into a Pinia store. This vendor store is then used in tables throughout ERM. The store should probably be removed and a different solution found for fetching the data for those tables to avoid a slow initial load of the ERM module. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 23565] New: Add columns configuration and export options to item search results
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23565 Bug ID: 23565 Summary: Add columns configuration and export options to item search results 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 Depends on: 23543 As we add more options to item search the output gets more crowded. Adding column configuration would let the library choose to hide some of the columns in item search results. Question: Should this make the "Export results to CSV" option obsolete? The "Export results to CSV" button automatically exports all results. The DataTables export button exports only visible results. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23543 [Bug 23543] Adding Withdrawn to the Item Search -- You are receiving this mail because: You are watching all bug changes.

1 19