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

[Bug 37697] New: CSS from HTML customizations previews bleeds through to rest of page
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37697 Bug ID: 37697 Summary: CSS from HTML customizations previews bleeds through to rest of page Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Currently, code in the "Preview" for "HTML customizations" can impact the "/cgi-bin/koha/tools/additional-contents.pl?category=html_customizations" page which is... not good. One suggestion is to use Shadow DOM to encapsulate the previews. I've used this elsewhere in Koha for maximum goodness. We could also try iframes. One way or another, something needs to be done... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 34128] New: Series entry in the 490 field causes the ordering of items to change in the holdings table
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34128 Bug ID: 34128 Summary: Series entry in the 490 field causes the ordering of items to change in the holdings table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The presence of a series entry in the 490 field causes the ordering of items to change in the holdings table. The different ordering is designed to display serial/journal items correctly but it shouldn't be triggered by a 490 entry for a "Books" item type To replicate: 1) In cataloging, click on New record 2) Fill in all the required fields with generic data, ensuring that the 942c field (Koha item type) is "Books" 3) In the 490a field - fill in any string as the Series statement 4) Click save 5) You should now be on the Add item page. We need to add 3+ items, making sure that the Home and Current libraries for each item are in reverse alphabetical order. e.g. Item 1: - Home library: Midway - Current library: Midway Item 2: - Home library: Fairview - Current library: Fairview Item 1: - Home library: Centerville - Current library: Centerville 6) In the top searchbar, find your new item that you have just added 7) On the item detail page, the holdings table will be displaying the items in reverse alphabetical order by library rather than in alphabetical order as it should be by default -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 34296] New: Non-Priority Hold customization
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34296 Bug ID: 34296 Summary: Non-Priority Hold customization Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 153557 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=153557&action=e… NonPriorityHold Some libraries may have one set of staff that needs to use the Non-priority hold option, while remaining staff would not ever need to use that option when placing a hold. It would be great if Koha permission settings allowed configuring the ability to place non-priority holds. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 --- Comment #59 from Alex Buckley <alexbuckley(a)catalyst.net.nz> --- (In reply to Alex Buckley from comment #58) > not backporting to 24.05.x unless requested - dependency not in 24.05 Correction this was for the follow-up bug report 38070 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Alex Buckley <alexbuckley(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexbuckley(a)catalyst.net.nz --- Comment #58 from Alex Buckley <alexbuckley(a)catalyst.net.nz> --- not backporting to 24.05.x unless requested - dependency not in 24.05 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35421] New: Is "A guarantor cannot be a guarantee." still correct?
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35421 Bug ID: 35421 Summary: Is "A guarantor cannot be a guarantee." still correct? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org With the ability to have adults guarantee for adults, I believe the above might no longer be true. Found while translating in koha-tmpl/intranet-tmpl/prog/en/modules/members/memberentrygen.tt:190 -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 Irene <i.tortorella(a)arts.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i.tortorella(a)arts.ac.uk -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '25

20 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 --- Comment #15 from Helen Jones <h.jones(a)ghil.ac.uk> --- Thank you, Heather! That describes the different approaches to bound-withs very well. This was the workflow for bound-withs that I used to use (Dynix/Voyager/Millennium/Sierra): 1. Create a completely standard bibliographic record for the first title [title A] in the bound-with volume. Add 501 Bound with: Title B / by author 2 -- Title C / by author 3. Add 590 Item No. x in classmark. $5 library code Add an item record with the classmark and barcode 2. Create bibliographic records for titles B and C. Do not add an item. 3. Using the bib record numbers of the bib records for titles B and C, link the item from title A to the bib records for titles B and C. And that's it. No parent record, no hierarchy. The item appears with each bib record just as it usually would for a non-bound-with bib-item record pair. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '25

19 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 Lauren Denny <lauren_denny(a)sil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lauren_denny(a)sil.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '25

19 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 Heather <flyingendpaper(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |flyingendpaper(a)gmail.com --- Comment #14 from Heather <flyingendpaper(a)gmail.com> --- This feature would be completely different from analytics--analytics have hierarchical relationships, those of "parent-child." A bound-with feature in most systems simply links an item to multiple bib records and *doesn't require* a "parent record" for the entire entity--analytics require a parent record for the child records. "Bound with" bib records would be like members of a team; all the bibs created for the one physical entity are equal, and the cataloging standards pre-RDA use a "Bound with" note explaining the relationship. It's easier cataloging, too, because catalog records may exist for the items which one library has all bound together, so they can be copy cataloged and the "bound with" note inserted. Creating a parent record and then using analytical relationships creates a lot more work, usually, than simply copy cataloging existing cataloging for the titles in the physical item, and then being able to link an item record to all the bibs, because a "bound with" is usually a unique physical items only held by one library. I know this sort of "bound with" workflow is difficult to describe to those who've only worked with Koha, and may not seem easier to people who understand linking entry fields & relationships, but for libraries that find themselves with a physical volume containing lots of bound together small titles, just copy cataloging some or all of them & then linking one item to all of the bibs is almost always a faster & easier cataloging operation than locally creating parent-child relationship records. -- You are receiving this mail because: You are watching all bug changes.

1 0