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

[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 10407] New: allow MARCXML records to be imported via Koha's GUI
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '15

27 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10407 Bug ID: 10407 Summary: allow MARCXML records to be imported via Koha's GUI Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com currently, you can only import MARCXML records into Koha using the ./bulkmarcimport.pl tool, from the command-line this bug will attempt to add that functionality to Koha's GUI -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 10773] New: Replace item-level codes with names/descriptions for Label Printing
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '15

26 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10773 Bug ID: 10773 Summary: Replace item-level codes with names/descriptions for Label Printing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label printing Assignee: cnighswonger(a)foundations.edu Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Currently, if you include "ccode","homebranch","holdingbranch","location", or "permanent_location" when printing labels, you'll end up with a code rather than a descriptive name/label. While I don't know how often you would necessarily use all of these, I have had a request come in for a label (instead of a code) for "homebranch" as they want their labels to include their library name. Makes sense to me. We already do it with item type. Collection code might be another one or location/permanent_location, depending on how they work their collections. "Holdingbranch" probably never but best perhaps to throw it in for good measure... -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 10827] New: List of holds does not update correctly
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '15

25 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10827 Bug ID: 10827 Summary: List of holds does not update correctly Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: costalc(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When an item has many patron's holds and it is checked-in, the first priority patron hold in the list of holds is set as "waiting". Then when this hold expires o is cancelled the hole list of holds doesn't update: the next patron in the list of holds "keeps on hold" but not "waiting" and no email is inserted in the message queue table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49