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

[Bug 16282] New: Usernames should be case sensitive
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '25

03 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16282 Bug ID: 16282 Summary: Usernames should be case sensitive 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: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently we don't care about case sensitivity for usernames, this is mostly ok, except when doing SSO ... with many systems who do care about case sensitivity, we can get username collisions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 16207] New: Incorporate circulation and fine rules for library groups
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16207 Bug ID: 16207 Summary: Incorporate circulation and fine rules for library groups Change sponsored?: --- Product: Koha Version: unspecified 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 think we could simplify circulation and fine rules by incorporating library groups into the mix. For example, I have 27 libraries, and 8 of them follow the same set of rules that are different from the defaults. So, what if instead of cloning these special rules to 8 different libraries (and who knows how many other duplicated sets of rules there are), we defined a set of rules for a library group. If the library is part of that group, it goes by those rules. I don't know if we want to use the same library groups that are already defined in the libraries and groups, or if we want to create a unique Circ rule group. Because, there is always the chance that one or more of the libraries in the 8 that are grouped together by affiliation or region could have a slightly different set of rules. However, I think rules by groups would make managing rules far less complicated than managing groups of cloned rules. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 16552] New: Add the ability to change the default holdings sort
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '25

14 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16552 Bug ID: 16552 Summary: Add the ability to change the default holdings sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org This new enhancement will add the ability to change the default holdings sort on OPAC displays to be by library. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 16759] New: make opac holdings table configurable
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '25

14 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16759 Bug ID: 16759 Summary: make opac holdings table configurable Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: jweaver(a)bywatersolutions.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: nicole(a)bywatersolutions.com Work to be done: * Make the holdings table in the OPAC configurable using the columns editor * Add columns hidden by default for home branch, holding branch, copy number and shelving location -- You are receiving this mail because: You are watching all bug changes.

1 44

[Bug 16735] New: Replace existing library search groups functionality with the new hierarchical groups system
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16735 Bug ID: 16735 Summary: Replace existing library search groups functionality with the new hierarchical groups system Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should replace the existing library search groups with the use of the new hierarchical groups system so that old system can be removed completely. General outline: 1) Add the option to each group for it to be a "search" group 2) Port over existing groups by creating a new group for each "categorycode" in the branchrelations table 3) Re-implement the group search using the new system, remove the old system -- You are receiving this mail because: You are watching all bug changes.

1 118

[Bug 17511] New: Authority linking subfield
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17511 Bug ID: 17511 Summary: Authority linking subfield Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently Koha links authority records and bibliographic records using subfield 9. What is the reason behind this choice? According to the MARC21 specification, subfield 0 is "Authority record control number or standard number", which seems more logical. Usually 9 is a locally defined field, and Libris, the National Union Catalogue in Sweden, uses subfield 9 for various other things already. What would it take to make the linking subfield into a configurable option? -- You are receiving this mail because: You are watching all bug changes.

1 49

[Bug 16157] New: C4::Koha::GetAuthorisedValues should not handle the selected option
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '25

22 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16157 Bug ID: 16157 Summary: C4::Koha::GetAuthorisedValues should not handle the selected option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 >From C4::Koha::GetAuthorisedValues # TODO: the "selected" feature should be replaced by a utility function # somewhere else, it doesn't belong in here. For starters it makes # caching much more complicated. Or just let the UI logic handle it, it's # what it's for. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 17505] New: REST API: Add route for messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 11 Aug '25

11 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17505 Bug ID: 17505 Summary: REST API: Add route for messaging preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org REST API: Add route for messaging preferences -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 16943] New: OverduesBlockCheckout ask for confirmation once per session
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '25

01 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16943 Bug ID: 16943 Summary: OverduesBlockCheckout ask for confirmation once per session Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: arm(a)hanover.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Just a minor suggestion... OverduesBlockCheckout has an option to 'ask for confirmation'. When checking out to a patron with any overdue items, the prompt to confirm comes up for each and every item you check out. I would prefer it to appear for staff confirmation just once for the current patron checkout session, the same as the AllFinesNeedOverride prompt does. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 16122] New: Item record needs to keep Local Use count
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '25

29 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16122 Bug ID: 16122 Summary: Item record needs to keep Local Use count Change sponsored?: --- Product: Koha Version: unspecified 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 Like the "issues" field in the items table, there should be a field for "local_use" to keep the count of local uses. While this information is kept in the statistics table, it is a task to acquire, and if a library wants to keep bloat down on their tables, the statistics are pruned on a regular schedule, which means loss of valuable data. This counter would keep that valuable information in one field in each item record, rather than having a separate field for each instance in the statistics table. Unless it is vital to someone to know the exact moment a local use occurred, I am suggesting that this piece of information not be recorded in the statistics table any longer. This would significantly reduce the growth of the statistics table in general. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 163