February 2024 - Koha-bugs - lists.koha-community.org

[Bug 5920] Optionally remove HTML from downloaded reports
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5920 Brendan Lawlor <blawlor(a)clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blawlor(a)clamsnet.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33842] New: Search for authid not returning right results with QueryAutoTruncate ON
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33842 Bug ID: 33842 Summary: Search for authid not returning right results with QueryAutoTruncate ON 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: adolfo.rodriguez(a)xercode.es Conditions to replicate this bug: 1) Preference QueryAutoTruncate activated 2) Have authorities with low authids 3) ElasticSearch, though it should also happen with Zebra. You can try it on this demo, it's on the master branch. Intranet: https://intranet.koha-community.es OPAC: https://catalog.koha-community.es/ User demo/demo The following searchs return different results: 1) Search in the catalog an:1 The QueryAutoTruncate adds * so it returns all the biblios that use authorities with authids that begin with 1, which are 81. That doesn't make sense as those authorities have nothing in common. https://intranet.koha-community.es/cgi-bin/koha/catalogue/search.pl?q=an%3A1 2) The authority with the id 1 is Mika Ninagawa, if you search her in the Authorities module, it says the authority is being used in two records, which is correct. https://intranet.koha-community.es/cgi-bin/koha/authorities/authorities-hom… 3) In the authority detail, Koha makes the same query as in point 1 so it appears it's being used in 81 records. https://intranet.koha-community.es/cgi-bin/koha/authorities/detail.pl?authi… I think this disparity in results can be confusing for librarians and readers, as they won't understand why Koha is recovering records that are unrelated to the author/subject... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 6796] Overnight checkouts taking into account opening and closing hours
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6796 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@ptfs-europe | |.com --- Comment #70 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Are you still intending to follow-up here Aleisha? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8133] hourly loans doesn't know when library closed
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8133 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=22514 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10869] Can't cancel order line if title deleted
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10869 --- Comment #105 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Marcel de Rooy from comment #104) > (In reply to Katrin Fischer from comment #103) > > (In reply to Marcel de Rooy from comment #102) > > > (In reply to Andrew Fuerste-Henry from comment #95) > > > > I would disallow the deletion and instead direct the user to first cancel > > > > the order. > > > > > > This makes sense. Probably many Koha installs contain pollution due to > > > allowing the deletion of biblio records while being used in ACQ. > > > > if you want to cancel, that's ok. But if you want to delete the record > > because it has left the collection? I think the solution needs some more > > complexity. > > As suggested, if you want to delete, then remove the linked orders first; > you can always add a new order.. Maybe we are misunderstanding each other. I hope this helps: If the orderstatus is "new" or "ordered" things are probably easy and we could do with the check and note. For standing orders it already gets a bit more complicated, so we need to add "partial" as well. But we will also need to think about how to handle deleting records for aqorders with orderstatus "cancelled" or "received". But this might be out of scope here I realize. Also you can't really 'remove linked orders'. We can only cancel or delete a whole basket. If you have multiple order lines in a basket, there is no way to remove just one (odd, right?) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 36058] New: Renew and Checkin Buttons greyed out
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36058 Bug ID: 36058 Summary: Renew and Checkin Buttons greyed out Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the introduction of separate buttons for renew/check in on the patron's circulation screen, bug 35068, Koha has the option for staff to choose renew or checkin items. However, when a patron has items to be renewed, Koha does mark them as renewable, however, the renew marked buttons are greyed out. The 'renew marked' buttons are only clickable when the items are unchecked renew and re-checked. This is an extra step added in this process with this new enhancement. It would be nice if the button was just clickable, as those items can be renewed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 26978] New: Add item type criteria to batch extend due date tool
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26978 Bug ID: 26978 Summary: Add item type criteria to batch extend due date tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In the Change due date plugin by inLibro, there is a possibility of choosing specific item types to extend due dates. I think the original purpose of the batch extend due date tool was for COVID and the purpose was to extend everything regardless, as the libraries were closed. However, it would be nice if we could discontinue de plugin in favour of the native tool. But that would require that the native tool have all the options that the plugin has. https://inlibro.com/en/changeduedate-instructions/ One example of use case would be where a school would want to extend loans for textbooks, because the semester was extended, but not the other types of items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 36057] New: Deleting uploaded file does not show the alert anymore
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36057 Bug ID: 36057 Summary: Deleting uploaded file does not show the alert anymore 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Does no longer work somehow: [% IF msg %] ShowAlerts( [% msg | html %] ); [% END %] Reproduce: Upload a file, delete it on the result form. No alert? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 2646] Add sort option for the series number
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '24

08 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2646 --- Comment #4 from Barbara Johnson <barbara.johnson(a)bedfordtx.gov> --- I have a new cataloger and she just asked me why Koha doesn't do this. We'd love to see items in a series sort in series order in the OPAC based on the 490$v. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 32166] New: When adding to a basket from a staged file we may use the wrong inputs
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '24

08 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32166 Bug ID: 32166 Summary: When adding to a basket from a staged file we may use the wrong inputs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On addorderiso2709.pl we loop over the records in the staged batch: for my $biblio (@$biblios){ $biblio_count++; skipping any not selected, which inlcudes any already imported: next if not grep { $_ eq $$biblio{import_record_id} } @import_record_id_selected; Later we use that count to find the inputs: my @homebranches = $input->multi_param('homebranch_' . $biblio_count); The problem being that if a record is already imported, our count increases, but the input on the page still counts from 1 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21