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

[Bug 16721] New: Serial claims table too wide
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '26

09 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16721 Bug ID: 16721 Summary: Serial claims table too wide 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 The serial claims table gets far too wide, especially when new subscription fields are added to it. It should be possible to configure if those display or not, but it also looks like a general problem. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 17473] New: Reverse payment permission
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '26

07 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17473 Bug ID: 17473 Summary: Reverse payment permission 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice to have permission just for reverse payments -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 19897] New: Make status 'on hold' more specific
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19897 Bug ID: 19897 Summary: Make status 'on hold' more specific Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In some cases 'on hold' can mean the item is waiting (item detail page in OPAC), in other cases it just means that someone has placed a hold (no renewal possible because...). It would be nice if we could be more clear about this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 20161] New: Show same information for format, material type etc. on the detail page as in the result list
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20161 Bug ID: 20161 Summary: Show same information for format, material type etc. on the detail page as in the result list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org A lot of libraries ask, why there is less information about the material type, format and literary format shown on the detail page than in the result list. I suggest to match both displays and make it possible to hide with CSS as you can already do on the result list (using the same classes). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 20022] New: use Modern::Perl in t (test) perl scripts
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '25

23 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20022 Bug ID: 20022 Summary: use Modern::Perl in t (test) perl scripts Change sponsored?: --- Product: Koha Version: unspecified 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org use Modern::Perl should be used instead of use strict; use warnings; Relevant in: 00-checkdatabase-version.t 00-deprecated.t 00-valid-xml.t AuthoritiesMarc_MARC21.t AuthoritiesMarc_UNIMARC.t Barcodes_EAN13.t Barcodes_annual.t Barcodes_hbyymmincr.t Barcodes_incremental.t Bookseller.t Budgets.t ClassSortRoutine.t ClassSortRoutine_Dewey.t ClassSortRoutine_Generic.t ClassSortRoutine_LCC.t ClassSource.t Contract.t Creators.t EdiInvoice.t Edifact.t Ediorder.t Ediordrsp.t External/Syndetics.t Form_MessagingPreferences.t Heading.t HtmlTags.t Installer_PerlDependencies.t Installer_pm.t ItemCirculationAlertPreference.t Koha_Util_MARC.t Labels.t Labels_split_ccn.t Labels_split_ddcn.t Labels_split_lccn.t Log.t Members_Attributes.t Members_Messaging.t Output.t Output_JSONStream.t Patroncards.t Patroncards_Batch.t Patroncards_Layout.t Patroncards_Lib.t Patroncards_Patroncard.t Patroncards_Profile.t Patroncards_Template.t Print.t QueryParser.t Scheduler.t Scrubber.t Stats.t SuggestionEngine.t TmplToken.t db_dependent/00-strict.t db_dependent/Amazon.t db_dependent/Heading_MARC21.t db_dependent/LDAP/test_ldap_add.pl db_dependent/Languages.t db_dependent/MungeMarcPrice.t db_dependent/Record/Record.t db_dependent/RecordProcessor_EmbedSeeFromHeadings.t db_dependent/Reports.t db_dependent/Service.t db_dependent/SuggestionEngine_ExplodedTerms.t db_dependent/Tags.t smolder_smoke_signal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 20019] New: use Modern::Perl in miscellaneous perl scripts
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '25

23 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20019 Bug ID: 20019 Summary: use Modern::Perl in miscellaneous perl scripts Change sponsored?: --- Product: Koha Version: unspecified 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org use Modern::Perl should be used instead of use strict; use warnings; Relevant in: services/itemrecorddisplay.pl suggestion/suggestion.pl tags/list.pl tags/review.pl virtualshelves/sendshelf.pl help.pl changelanguage.pl koha_perl_deps.pl debian/bd-to-depends debian/build-git-snapshot debian/list-deps docs/CAS/CASProxy/examples/koha_webservice.pl docs/CAS/CASProxy/examples/proxy_cas.pl docs/CAS/CASProxy/examples/proxy_cas_callback.pl docs/CAS/CASProxy/examples/proxy_cas_data.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 15789] New: Split borrowers permission into create/edit
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '25

18 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15789 Bug ID: 15789 Summary: Split borrowers permission into create/edit Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All URL: http://devs.bywatersolutions.com/projects/fine-overrid es/ OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Goal: Add ability to control if an individual staff user can override checkout restriction based on noissuescharge Work to be done: 1) Add new permission allow_fine_override 2) Set new permission for existing staff members with setting for AllowFineOverride 3) Remove use of AllowFineOverride, replace with use of new permission allow_fine_override Looking for sponsors here: http://devs.bywatersolutions.com/projects/fine-overrides/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 19917] New: Holds for self registered patrons
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19917 Bug ID: 19917 Summary: Holds for self registered patrons 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There needs to be a switch in place that does not allow a hold to be triggered if the hold is for a patron in the self registered category. Our library workflow: * Allows self registered patrons to place a couple of holds. * Doesn't assign an automatic card number. * Prints specialized hold slips * Allows self pickup Ideally, we would want the preference to not trigger the hold if the self registration category is in use on the patron with the hold, and a message to come up asking staff to go ahead and assign a card number, or something to that effect. Right now, when the hold is triggered, the slip comes out wrong because there is data missing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20271] New: Merge deleted/old tables with their "alive" cousins
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 Bug ID: 20271 Summary: Merge deleted/old tables with their "alive" cousins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P1 - high Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: boutrosboutrosboutros(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In Koha's DB, instead of having a "soft" deletion of entries by flagging the deleted one as so, the rows in the db is actually deleted, but only after a new row in a different table is inserted. Koha's DB is relational, so there is a cascade of links between each object: a biblio is referred by many items, and each item is referred by issues, holds, messages. E.g.: when a row in the item table is moved from "items" to "deleted_items", then all the references from holds, transfers and so on will be broken. The suggested more orthodox approach to this would be to add a "deleted_at" column, which is normally null unless the row is deleted, then it set to the timestamp of when it was deletion. This means that the row is still there and will still be referred by other tables, but it just won't be shown in the relevant lists. This would improve the maintenance of Koha in many ways (e.g.: the auto_increment id on those tables caused lots of issues when you add an item and delete it immediately after. the next new item will have the same itemnumber as the previously deleted one, clashing with it in many ways). This bug is about merging the all these tables: deletedborrowers => borrowers deletedbiblio => biblio deletedbiblioitems => biblioitems deletedbiblio_metadata => biblio_metadata deleteditems => items old_issues => issues old_reserves => reserves -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 383

[Bug 20269] New: Allow selecting default collate rule
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20269 Bug ID: 20269 Summary: Allow selecting default collate rule Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org For some languages, the default collate rule set in kohastructure.sql, utf8_unicode_ci, doesn't work correctly. For example, Finnish alphabet expects the alphabet to sort abc...xyzåäö, but the unicode_ci rule doesn't handle the åäö right. Instead, we need to use the swedish_ci rule. It would be nice to be able to define the default collate rule during install. Problem can be seen for example when you go catalogue a new record and have frameworks starting with 'ä' or 'ö', those will sort incorrectly. On the database, you can test this with: insert into biblio_framework (frameworkcode, frameworktext) values ('TEST', 'Äänikirja'); -- Note where the 'Äänikirja' is located select * from biblio_framework order by frameworktext collate utf8_unicode_ci; -- And then the correct order, with 'Äänikirja' last: select * from biblio_framework order by frameworktext collate utf8_swedish_ci; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6