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

[Bug 14250] Don't allow to generate discharges for patrons with fines
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '25

31 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14250 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy(a)rijksmuseum.nl Status|Signed Off |Patch doesn't apply -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24778] New: Move from Memcached to Redis to solve L1 caching issues?
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '25

31 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24778 Bug ID: 24778 Summary: Move from Memcached to Redis to solve L1 caching issues? 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Would it be worthwhile to switch from Memcache to Redis? Redis has pub/sub which in theory would allow all processes to listen for syspref changes and update their L1 caches if necessary. What made me think of this is bug 23640 I have no idea if this is worth the time and effort, but it seems like it would solve the major issue we have with memcached. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 38947] New: Koha workflow presets
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38947 Bug ID: 38947 Summary: Koha workflow presets Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I'm wondering if it would be beneficial to be able to design some presets for Koha admin. For example, there are bugs that have been long standing, asking for mechanisms to be able to close branches for a season, like schools. What if there was a table that remembered all the settings for scenarios? It remembers rules, branch settings, transport cost matrix, transfers - not necessarily the other admin preferences that would break something. But how things move. I could see a preset being made to reset to the normal operating mode. I could see a preset for school closures. I could see a preset for emergencies. I could see a preset for testing. Thoughts? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39004] New: Statistical patron account should have limitations
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39004 Bug ID: 39004 Summary: Statistical patron account should have limitations Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To replicate: 1. Create a patron category and set the type as statistical. 2. Create a patron and assign the statistical patron category 3. Test by checking an item out to the patron and see local use recorded. 4. From the patron account, search to place a hold an item and place the hold. See the statistical patron now has a hold. I would not expect the statistical patron to be able to place a hold. 5. Add a fine 6. Place a purchase suggestion. 7. Make something bookable and place a booking. 8. Add to a club 9. Add to a patron list 10. Make an article request It appears the checkout options are logged as local use, but other account features are still available. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 39002] New: Unable to import XPM local cover image
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39002 Bug ID: 39002 Summary: Unable to import XPM local cover image Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I stumbled upon this by accident, I don't know if this functionality is used very much, or at all. Note: I used the image teapot.xpm on this page https://people.math.sc.edu/Burkardt/data/xpm/xpm.html to test. I also tried to make one with GIMP with the same result. To recreate: 1. Enable LocalCoverImages 1.1. Go to Administration > System preferences 1.2. Search for LocalCoverImages 1.3. Change the value to 'Show' 1.4. Click 'Save all Enhanced content preferences' 2. Import an XPM image as a cover image 2.1. Download the teapot.xpm image from the site above, or another .xpm image 2.2. Search for a record and go to the detailed page 2.3. Click the 'Images (0)' tab 2.4. Click 'Upload' --> Note that the help message above the box to select a file says 'The tool will accept images in GIF, JPEG, PNG, and XPM formats.' 2.5. Click 'Drop files here or click to select a file' 2.6. Choose the .xpm image --> Note that at this point, the image preview is a broken image 2.7. Click 'Process images' --> Error message: 'Cannot process file as an image. Please ensure you only upload GIF, JPEG, PNG, or XPM images.' I opened the teapot.xpm image in GIMP and it opens fine. It's not corrupted as far as I know. I think we should either fix the XPM import or remove the mention that the tool accepts XPM format. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 28337] New: Add System-control-number index for authorities to MARC21 indexes
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28337 Bug ID: 28337 Summary: Add System-control-number index for authorities to MARC21 indexes 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: nick(a)bywatersolutions.com https://www.loc.gov/marc/authority/ad035.html The 035 field in authorities can contain a system control number, this is useful for authority cleanup work as it can contain a non-Koha id for the record When importing, however, we cannot use this field for matching as it is not indexed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 38835] New: filters on ERM report results are not working
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38835 Bug ID: 38835 Summary: filters on ERM report results are not working Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Created attachment 176163 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=176163&action=e… capture filters on ERM report results are not working. And a global search seems to be stuck See capture, after a TR_J1 report (note they are a lot of other reports already loaded in database, maybe the cause for the issue?) -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 38937] New: Password must contain at least characters
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38937 Bug ID: 38937 Summary: Password must contain at least characters Change sponsored?: --- Product: Koha Version: 24.11 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: judithjoni(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 176859 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=176859&action=e… i tried more then 50 time same error is showing faceign this issue Password must contain at least characters. unable to finish onboarding Web installer › Create Koha administrator patron tried several password not working -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

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

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |39000 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39000 [Bug 39000] "Encoding errors" block on detail page hurt the eyes -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32444] New: Identify patrons as a group or family unit
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '25

30 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32444 Bug ID: 32444 Summary: Identify patrons as a group or family unit Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For years, Koha has used guarantors to link families together. Progress was made when we were able to link more than one person to a child. However, there are other areas where it might be beneficial to link patrons together that don't involve parents. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31329 proposes to block linked accounts when one is restricted. But before we do that, I think it might be worth looking at the guarantors a little bit and refine our approach with this functionality before proceeding with 31329 (sorry Wally!). I think guarantors should be updated to something more universal, linking any patron to any patron. Right now we limit it to linking a parent or guardian to a child. But what if we wanted to link a household. That might just be siblings in the same house. What if it was husband and wife? What if it was an organization? There are some great ideas with linked accounts, like what 31329 proposes. And I am sure that there are others. For example, maybe your library has some resources that you want to limit 1 per household. Right now we can't do that, but perhaps we could with a re-imagined linking system. What if we wanted to update information in the linked accounts? This would be a good start. What does this re-imagined linking look like? Perhaps: * Eliminate the limitation allowing the links to just child accounts. * Name the organizational grouping: Household, School name, business name, etc. * Identify and an all guarantors in the grouping. * Can the grouping exist without a guarantor? * If not, if the last guarantor is removed from the group, should someone else in the grouping be marked as guarantor, should the grouping be allowed to carry on without a guarantor, or should the grouping be dissolved? There may be other aspects we might want to consider in this functionality, but this is a good start. Once this is reworked, then we could look at options of linking blocks to particular groups, updating groups, circulation limitations to groups, etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10