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

[Bug 16959] New: E-mail alerts for saved searches
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16959 Bug ID: 16959 Summary: E-mail alerts for saved searches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It would be nice if Koha allowed to send e-mails to patrons when a new record is created for a saved search. Examples: - New records are added within a specific call number range - New records where the title contains certain words It should be possible to set this up individually per patron. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 32448] New: Datatable filtering problem whith hidden column
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32448 Bug ID: 32448 Summary: Datatable filtering problem whith hidden column Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In biblio record details page for items table : When a column is hidden, the column filters seems have problem. Test plan for KTD : 1) Go to /cgi-bin/koha/catalogue/detail.pl?biblionumber=312 2) See that by default in items table columns 'Checkouts' and 'Renewals' (after 'Last seen') are hidden by default 3) Activate filters 4) Search in column 'Date accessioned' with '2', no results 5) Hide column 'Item type' 6) Search in column 'Collection' with 'e', no results Looks like the search is performed on next column. 7) Search in column 'Home library' with 'Reference', no line is filtered! -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30406] New: Our DT tables not filtering on the correct column if hidden by default
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30406 Bug ID: 30406 Summary: Our DT tables not filtering on the correct column if hidden by default 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org To recreate, hide city_state for the cities table, create some cities and notice that using the "Country" column filter will actually filter on the hidden "State" column (the one on the left) Coming from bug 30063 comment 23 (point 5) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 31025] New: Reports with too many params can exceed length limit of URI
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '23

04 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31025 Bug ID: 31025 Summary: Reports with too many params can exceed length limit of URI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Our reports submit the form as a GET request - this is useful for saving links to report results, however, when using the <<Param|list>> feature, too much data can be submitted to the form and cause a 414 error: Request-URI Too Long The requested URL's length exceeds the capacity limit for this server. Apache/2.4.53 (Debian) Server at kohadev-intra.myDNSname.org Port 80 We should, optionally, submit large requests as 'POST' Dirty sample code: $("#rep_guided_reports_start textarea[id^='sql_params']").change(function(){ console.log('Garsh'); let param_length = 0; $("textarea[id^='sql_params']").each(function(index,value){ param_length += $(this).val().length; }); if( param_length > 900 ){ $("#rep_guided_reports_start form").attr('method','post'); $("#rep_guided_reports_start form input[type='submit']").after('<p>Too much params! Wil submit as post!</p>'); } }); -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 22384] New: Make the title of an ILL clickable
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '23

04 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22384 Bug ID: 22384 Summary: Make the title of an ILL clickable 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: magnus(a)libriotech.no Target Milestone: --- Today we have one column with the unclickable title of an ILL item and one column with the clickable biblionumber. It would be potentially less confusing if the title was clickable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 33346] New: Add Help link to Koha manual in ERM module
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33346 Bug ID: 33346 Summary: Add Help link to Koha manual in ERM module Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: catrina(a)bywatersolutions.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 All other pages/modules in Koha show the Help button hyperlinked to the relevant portion of the manual. This link is missing throughout the ERM module and should be added in. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 27667] New: Display the number of non-indexed records
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27667 Bug ID: 27667 Summary: Display the number of non-indexed records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr On "About Koha" page are displayed the numbers of indexed biblios and authorities with ES. It could be great if we could have comparison with the number of records in the database to display the number of non-indexed datas. We could have on the same page something like : Indices: koha_robin_biblios (count: 834999 on 1056480 = 221481 missing) Or on the "System information" tab with the other "Data problems". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 26639] New: Turn auto_savepoint ON
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26639 Bug ID: 26639 Summary: Turn auto_savepoint ON Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org We have been adding transactions a lot lately, and we have just found that we are expecting a behaviour that is not the one we have. Take a look at the code posted on bug 26518 comment 7. If we turn auto_savepoint on, we will get the behaviour we expect. This patch has been initially attach on bug 21684 comment 2, but then dropped. See also https://metacpan.org/pod/distribution/DBIx-Class/lib/DBIx/Class/Manual/Cook… -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 26529] New: Holds rules enforced incorrectly when not set at library level
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26529 Bug ID: 26529 Summary: Holds rules enforced incorrectly when not set at library level Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(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 - Set ReservesControl to item home library 2 - confirm your circ rules allow holds at both the All Libraries and library-specific levels 3 - confirm Default checkout, hold and return policy is totally unset at both the All Libraries and library-specific levels 4 - place a hold on an item at Branch A for pickup at Branch A 5 - check item in, confirm hold triggers 6 - cancel hold 7 - go to Default checkout, hold and return policy for Branch A 8 - enter 1 for Total current checkouts allowed, save that with no other values entered 9 - re-place hold, confirm no error when placing hold 10 - check item in, hold does not trigger 11 - set Hold policy and Hold pickup library match at to Any Library at All Libraries level 12 - confirm hold still doesn't capture set Hold policy and Hold pickup library match at to Any Library for Branch A 13 - confirm hold now captures If these rules aren't set at the branch level we should be falling back to All Libraries. If they're not set anywhere, we should be assuming holds are allowed is the circ rules allow them. Starting from default testing docker data, this is what my db shows at step 7: MySQL [koha_kohadev]> select * from circulation_rules; +----+------------+--------------+----------+-------------------+------------+ | id | branchcode | categorycode | itemtype | rule_name | rule_value | +----+------------+--------------+----------+-------------------+------------+ | 1 | NULL | NULL | NULL | maxissueqty | 5 | | 2 | NULL | NULL | NULL | maxonsiteissueqty | 5 | +----+------------+--------------+----------+-------------------+------------+ And this is what it shows at step 8: MySQL [koha_kohadev]> select * from circulation_rules; +----+------------+--------------+----------+--------------------------+------------+ | id | branchcode | categorycode | itemtype | rule_name | rule_value | +----+------------+--------------+----------+--------------------------+------------+ | 1 | NULL | NULL | NULL | maxissueqty | 5 | | 2 | NULL | NULL | NULL | maxonsiteissueqty | 5 | | 8 | CPL | NULL | NULL | patron_maxissueqty | 1 | | 9 | CPL | NULL | NULL | returnbranch | | | 10 | CPL | NULL | NULL | hold_fulfillment_policy | | | 11 | CPL | NULL | NULL | patron_maxonsiteissueqty | | | 12 | CPL | NULL | NULL | max_holds | | +----+------------+--------------+----------+--------------------------+------------+ I cannot recreate this on master. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 20755] New: Allow separate email configuration for acq emails
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20755 Bug ID: 20755 Summary: Allow separate email configuration for acq emails 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the emails in acuisistion (claims and orders) are sent with the email address of the librarian that triggers the sending. This is not practical in all cases for several reasons and it would be nicer if a general acquisition team email could be used. The development should allow to configure the email on library level with a from, replyto and returnpath address similar to the branchemail and it's options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41