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

[Bug 7411] New: remove diacritics when automatically generating userid
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '15

05 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7411 Bug #: 7411 Summary: remove diacritics when automatically generating userid Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: sophie.meynieux(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com When userid is automatically generated from firstname and surname, diacritics should be removed because login with diacritics may results in failure -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 23

[Bug 5517] New: After removal of koha-common package in Debian Squeeze cron jobs are not deleted
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '15

05 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5517 Summary: After removal of koha-common package in Debian Squeeze cron jobs are not deleted Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: gaurav.paliwal1989(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When someone remove the koha-common in debian squeeze the cron jobs that are automatically added at the time of installation are not automatically removed even after the complete removal of the koha-common package. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 8

[Bug 7021] New: patron category in the statistics table
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '15

04 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7021 Bug #: 7021 Summary: patron category in the statistics table Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com The patron category code should be in the statistics table. We track the item type and item number, but we only track the borrowernumber for the patron and part way through the year the patron's category could change from child to adult - or the patron could be deleted and that will mess with the statistics on circulation/actions based on patron category. Once that data is added to that table, the circulation stats wizard will need to be updated as well. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 29

[Bug 7651] New: Updating currency exchange rates should not require 'parameters' permission
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '15

04 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7651 Priority: P5 - low Change sponsored?: --- Bug ID: 7651 Assignee: katrin.fischer(a)bsz-bw.de Summary: Updating currency exchange rates should not require 'parameters' permission QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: katrin.fischer(a)bsz-bw.de Hardware: All Status: NEW Version: master Component: Acquisitions Product: Koha Currently it's not possible to update exchange rates in acquisitions without giving the user 'paramters' permission, which means access to a lot of administration parameters. I suggest following change: Parameters: - change active currency - add new currencies (?) New permission: acquisition > manage_currencies - update exchange rates for existing currencies - add new currencies (?) Not sure about adding new currencies. Any opinions on this? Is it a good idea? Should it work differently? -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 7683] New: stat wizrad :cataloging
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7683 Priority: P5 - low Change sponsored?: --- Bug ID: 7683 Assignee: gmcharlt(a)gmail.com Summary: stat wizrad :cataloging QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: stephane.delaye(a)biblibre.com Hardware: All Status: NEW Version: rel_3_8 Component: Reports Product: Koha In the cataloguing wizard, add the following lines that can be used as row/column/filter: * status * item creation date (range with dynamic calendar) * item suppresion date (range with dynamic calendar) * origin : items.materials - authorized value list "origin" 995$s * Domaine : 995$t items.statisticvalue "domain" av list Adds options for distinct biblionumber count on title and items. Add 3 options (radio buttons) - Titles count "COUNT (biblionumber)" - Counting of copies "COUNT (ItemNumber)" (current behavior) - Counting of copies deleted "COUNT (deleteditems.itemnumber)" - Add to selected row or column + filter combo: - items.notforloan - items.materials - items.statisticvalue For each of these fields, retrieve the label and the code value allowed in the grid cataloging default. If no MARC field is mapped to the field in question, it does not show this line in the wizard. If the MARC field is associated with a legal value, it displays a dropdown list for the filter, if a text field. - Add to selected row or column + filter on a date range - Items.dateaccessioned (create Date) - Deleteditems.timestamp (date deleted) (Only if the third option (eg count. Del.) Is selected) -- You are receiving this mail because: You are watching all bug changes.

1 146

[Bug 9537] New: Add a list of the patches that have been applied to a koha installation
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9537 Bug ID: 9537 Summary: Add a list of the patches that have been applied to a koha installation Classification: Unclassified 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: egpetridis(a)yahoo.com CC: gmcharlt(a)gmail.com I wonder if it would be useful to add a tab in the home, about koha section, displaying a list patches that have been applied to the specific koha installation, similar to the list of pearl modules. This could prove handy when trying to ascertain why a bug that doesn't exist in the main distribution manifests itself in some git derivative or other. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 7397] New: Patron search from Checkout tab does 'contains' instead of 'starts_with' search
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7397 Bug #: 7397 Summary: Patron search from Checkout tab does 'contains' instead of 'starts_with' search Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com When searching for a patron using the Checkout tab, instead of the main Patron search, inexact searches (those returning more than 1 hit) do a 'contains' search instead of a 'starts_with' search (as one would expect from the Patron search module's behaviour). The result is many, many more results than one would otherwise expect. The call to Search() in circ/circulation.pl seems to be malformed given the documentation for how C4::Members::Search works. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

[Bug 8612] New: System preference to have custom fields in exort csv basket
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '15

27 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8612 Priority: P5 - low Change sponsored?: Sponsored Bug ID: 8612 Assignee: koha-bugs(a)lists.koha-community.org Summary: System preference to have custom fields in exort csv basket Severity: enhancement Classification: Unclassified OS: All Reporter: pelletiermaxime(a)gmail.com Hardware: All Status: NEW Version: master Component: Acquisitions Product: Koha New system preference where you can write the fields you want to have in the "Export this basket as CSV" button in a basket page of the acquisition module. This could be done in better ways, but this is what I came up with, in the time I had. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 9370] New: use Library::CallNumber::LC when splitting LC call numbers for spine labels
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '15

23 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9370 Bug ID: 9370 Summary: use Library::CallNumber::LC when splitting LC call numbers for spine labels Classification: Unclassified 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: gmcharlt(a)gmail.com We should switch to using Library::CallNumber::LC for splitting LC call numbers when generating spine labels for several reasons: [1] Library::CallNumber::LC was written specifically for parsing LC call numbers, while the current code in Koha was developed based on very few examples. [2] The module is currently being used by Evergreen. Any future efforts to improve LC call number parsing by updating Library::CallNumber::LC would benefit both ILS projects. [3] In bug 6281, I'm proposing using this module to improve sorting of LC call numbers. Using the module would reduce redundancy in Koha's code base. [4] And, perhaps most importantly, it solves a problem reported by a library. The immediate motivation for this change is an example call number that one of our customers noted is being split incorrectly. The LC number 'QH541.15.C6 C25 2012' is currently being split like this: QH 541 .15 .C6 C25 2012 It should actually be split as follows: QH 541.15 .C6 C25 2012 The ".15" after "541" is part of the main class number; it isn't a Cutter. To test: [1] Add an item record with the call number QH541.15.C6 C25 2012 and set it classification source to lcc. [2] Generate a spine label and verify that the call number is split like this: QH 541.15 .C6 C25 2012 -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 5302] New: Replace current call number splitting code with a plug-in system based on classification source
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '15

23 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5302 Summary: Replace current call number splitting code with a plug-in system based on classification source Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: cnighswonger(a)foundations.edu QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 RFC began here: http://wiki.koha-community.org/wiki/Call_Number_Splitting_Plugin_System Please feel free do comment, etc. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 7