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

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 --- Comment #17 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #16) > But isn't this more a question of how the cn_sort is generated instead of > making sure it's using cn_sort for sorting? These are tightly coupled of course. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8425] Autobarcode generates duplicate barcodes with AcqCreateItems = on order
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8425 --- Comment #25 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Unless we totally rewrite the code of the module, which will de facto obsolete this patch, I do not know how we could solve this without that kind of tweak, but I'm not sure it would increase the technical debt since it is not more than a fixup to an existing debt and it simply improves the possibility of existing obsolete code. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21996] SPAM
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21996 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=38693 | Blocks|38691 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38691 [Bug 38691] FRBRizeEditions should look directly in the local catalog for other editions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 38691] New: FRBRizeEditions should look directly in the local catalog for other editions
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38691 Bug ID: 38691 Summary: FRBRizeEditions should look directly in the local catalog for other editions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently FRBRizeEditions only looks from a remote service for other editions for a given ISBN. Local queries are only done to validate that the local database has the results found from the external source. Instead/on-the-side we should do a local lookup for other editions of the same biblio. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 --- Comment #16 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- But isn't this more a question of how the cn_sort is generated instead of making sure it's using cn_sort for sorting? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA CC| |m.de.rooy(a)rijksmuseum.nl --- Comment #15 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to PTFS Europe Sandboxes from comment #14) > barcode TEST1 callnumnber D1015.B4 1965 > barcode TEST2 callnumnber D102.D3 1930 > barcode TEST3 callnumnber D101.2.A8 1951 > 8 - order is TEST3,TEST2,TEST1 (or reversed depending on sort direction) > > Signed-off-by: Heather Hernandez <flyingendpaper(a)gmail.com> While reading comment4 of Heather, I am not sure what the LCC order now should be. IIUC the order should be 1-11-2. But this test marks 101-102-1015 as correct while I expected 101-1015-102 ? Please clarify. PS The general scheme sorts also like 1-11-2 for our callnumbers like 10 A 1, 100 A 2 or 1000 A 3. Which is a pain since we started. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13870] Add warnings about subscriptions and orders when deleting items
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13870 --- Comment #9 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Hello all, I've just rebased it, thanks Katrin for your review, and Frido too ! I've changed my request to use prefetch like Frido said and I also fix the missing filter. For the tidiness.. I've tried to found it but maybe a "false positive" ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13870] Add warnings about subscriptions and orders when deleting items
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13870 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #152235|0 |1 is obsolete| | --- Comment #8 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 175440 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=175440&action=e… Bug 13870: Added a visual warning message on the item batch form I add a visual warn on item linked to subscription or concern by an order. I don't think that pop-up could be the solution so I put a warn triangle aside the delete action to I don't think another pop-up is the ideal solution so I chose to integrate a yellow triangle right next to the action leading to the deletion of the 'item' with a hover message if a subscription or order is linked. I'm looking forward to your feedback :) Test plan : 1) Apply this patch 2) Be sure to have item with order or can concern by a subscription 3) Edit them to go on the batch form 4) See the yellow triangle next to the 'delete' action in 'actions' dropdown menu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13870] Add warnings about subscriptions and orders when deleting items
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '24

13 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13870 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38692] New: Item search results table filters do not match date display preference
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38692 Bug ID: 38692 Summary: Item search results table filters do not match date display preference Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When looking at results in item search, there are filters at the top of each column. For columns containing dates, the filter always searches on ISO format (YYYY-MM-DD), but the data will display following the DateFormat system preference. So your item may show a value of "12/12/2024," but it won't be shown in your results if you enter "12/12/2024" as a filter, only if you enter "2024-12-12" We could put a datepicker on the filter search field? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2