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

[Bug 18705] New: collections_tracking-table is missing index/ foreign key to items
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18705 Bug ID: 18705 Summary: collections_tracking-table is missing index/foreign key to items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This makes searches such as circ/pendingreserves.pl rather slow and very noticeable on HDDs -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 25781] New: Remove duplicate days_forward method from Koha::Calendar
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25781 Bug ID: 25781 Summary: Remove duplicate days_forward method from Koha::Calendar 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org With bug 15260 the 'next_open_days' method learnt to accept an integer number of days to add before calculating the next open day date. This, in effect, removes the requirement for the days_forward method that does the same. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25295] New: Allow customization of staff client based on login location
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25295 Bug ID: 25295 Summary: Allow customization of staff client based on login location Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With more library systems or multiple-branch libraries using Koha, it would be really helpful to be able to customize the look of the staff client based on the library a staff member is logged in at. For instance, allow a library system to designate a header or background color on the staff client based on the branch. So branch A would be green, branch B would be purple, etc. This would allow users to easily and quickly identify which branch they are logged in to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 26275] New: Deleting item should not automatically delete volume
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '25

28 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26275 Bug ID: 26275 Summary: Deleting item should not automatically delete volume Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - create a bib - add an item - create a volume - add item to volume - in the Holdings table on detail.pl, check the box to select your item and pick Delete selected items - on the next page, do not check "Delete records if no items remain" - click Delete selected items - return to your bib. the item and volume are both gone I don't think we should automatically delete the volume when removing the last item. I'd like to see another check box on the batch deletion screen -- "delete volumes if no items remain" to parallel "delete records if no items remain" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 26867] New: Holds to Pull should use cn_sort
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26867 Bug ID: 26867 Summary: Holds to Pull should use cn_sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client 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 To recreate: - create three bibs, each with one item. those items should have these call numbers: -- JC43 .G6 1890 -- JC330 .F74 2000 -- JC480 .R63 2006 - place an item level hold on each item - go to Holds To Pull, sort by call number - notice items are order incorrectly, going 330, 43, 480 - use a report to pull the cn_sort values for your 3 items, confirm that ordering by cn_sort in your report correctly orders them 43, 330, 480 We should use cn_sort here to get them in the correct order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17507] New: Preference to limit how old an offline circ file can be when uploaded
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '25

26 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17507 Bug ID: 17507 Summary: Preference to limit how old an offline circ file can be when uploaded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 We recently ran into an issue where old transactions were uploaded from offline circ. This caused a BIG MESSS. Mistakes will happen. It would be great if there was a setting in Koha to limit the number of days old a file can be when uploaded. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 18626] New: Add ability to track cardnumber changes for patrons
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '25

25 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18626 Bug ID: 18626 Summary: Add ability to track cardnumber changes for patrons 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries want to keep a history of cardnumber changes for a patron. This is a feature that another ILS has. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 26062] New: Membership Expiry can not be limited by Patron Category
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '25

24 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26062 Bug ID: 26062 Summary: Membership Expiry can not be limited by Patron Category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Currently, the membership expiry cron runs and can be limited by branchcode, to exclude specific branches. However, it can not limit by patron category. It would be extremely helpful for libraries to be able to utilize a different way of using this cron by allowing the limiting by patron category. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 21412] New: Opac upload file access
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '25

21 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21412 Bug ID: 21412 Summary: Opac upload file access Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: scdogan(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 79410 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=79410&action=ed… step1 I want to restrict access to the files I upload in the Koha automation system. What steps can I use? Thank you. 1. 1. Opac Display - Disable ( This collection will be private) 2. https://www.youtube.com/watch?v=mbYgsodcPaU (How to attach a file to a MARC Record in Koha) 3. Cataloging step 4.Copy upload file link ( For Example : http://193.140.223.100/cgi-bin/koha/opac-retrieve-file.pl?id=eca42072bd9eb8… ) 5. Log out Koha 6. Paste link any browser than file is open. I want to system asked username and password -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 20185] New: Some scripts does not pass perl -wc
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20185 Bug ID: 20185 Summary: Some scripts does not pass perl -wc Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: In Discussion Severity: normal 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 -- You are receiving this mail because: You are watching all bug changes.

1 23