July 2012 - Koha-bugs - lists.koha-community.org

[Bug 8326] New: allow attributes to be made repeatable
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8326 Priority: P5 - low Change sponsored?: --- Bug ID: 8326 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: allow attributes to be made repeatable Severity: enhancement Classification: Unclassified OS: All Reporter: nengard(a)gmail.com URL: cgi-bin/koha/admin/patron-attr-types.pl?op=edit_attrib ute_type&code=DL Hardware: All Status: NEW Version: master Component: Patrons Product: Koha I understand not letting people edit attribute codes or the fact that it's a unique identifier after it has been saved, but I see no reason why an attribute can't be made repeatable retroactively. I think this value should be editable - at least from 'not repeatable' to 'repeatable' since it might cause problems going from 'repeatable' to 'not repeatable'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 8460] New: Improve Error Handling
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8460 Priority: P5 - low Change sponsored?: --- Bug ID: 8460 Assignee: gmcharlt(a)gmail.com Summary: Improve Error Handling Severity: enhancement Classification: Unclassified OS: All Reporter: thatcher.rea(a)bywatersolutions.com Hardware: All Status: NEW Version: unspecified Component: Architecture, internals, and plumbing Product: Koha We've had a few scenarios recently when a library patron experiences a catalog error. The default messages say "For help, please send mail to the webmaster (test(a)example.com) giving this error message and the time and date of the error." 9 times out of 10, the patron will simply copy the error, and provide no additional information about the event at all. Not even what catalog they were working on, which makes these messages effectively useless. I propose that these messages be written instead to say "Please click here to send the system administrator an error report." Which can then send an internally generated message containing: * referring link * the error message * server info * koha version, etc This could be sent to the address in the KohaAdminEmailAddress sypref. Regards, :T -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 8528] New: Move C4::Calendar to Koha::Closure
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8528 Priority: P5 - low Change sponsored?: --- Bug ID: 8528 Assignee: koha-bugs(a)lists.koha-community.org Summary: Move C4::Calendar to Koha::Closure Severity: enhancement Classification: Unclassified OS: All Reporter: elliott(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Holidays Product: Koha This will be a blanket ticket for the smaller encompassing tickets for moving and cleaning up holidays. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 8060] New: Wrong length for category_code in borrower_attribute_types
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8060 Priority: P5 - low Change sponsored?: --- Bug ID: 8060 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Wrong length for category_code in borrower_attribute_types Severity: enhancement Classification: Unclassified OS: All Reporter: gaetan.boisson(a)biblibre.com Hardware: All Status: NEW Version: master Component: Patrons Product: Koha The category_code column in the borrower_attribute_types which is a varchar(1) is meant to refer to the categorycode column in the categories table which is a varchar(10). Category codes get truncated when trying to restrict an extended attribute to a specified category, breaking the functionnality unless the categorycode is one letter long. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 8245] New: in acqui-home.pl with hierarchic bugdets the calculation of a sum spent in sub-budget is not in the budget
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8245 Priority: P5 - low Change sponsored?: --- Bug ID: 8245 Assignee: koha-bugs(a)lists.koha-community.org Summary: in acqui-home.pl with hierarchic bugdets the calculation of a sum spent in sub-budget is not in the budget Severity: enhancement Classification: Unclassified OS: All Reporter: christophe.croullebois(a)biblibre.com Hardware: All Status: NEW Version: master Component: Acquisitions Product: Koha Created attachment 10275 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=10275&action=edit snapshot of budgets in acqui-home.pl See snapshot, in "Spent" column, the parent budget "hist" have "0", must have "136,50", because "histjeun" and "histvieil" are its sub-budgets. Big work to do... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 6068] New: New feature: capability to blanking subfields in BatchMod
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6068 Bug #: 6068 Summary: New feature: capability to blanking subfields in BatchMod Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: alex.arnaud(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org -- 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 17

[Bug 6688] New: capability to blanking subfields in BatchMod = disable form
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6688 Bug #: 6688 Summary: capability to blanking subfields in BatchMod = disable form Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org I would recommend an improvement that does what Owen suggests in #6068 and make it so that you can't select if the check box is checked -- 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 4

[Bug 4944] New: Create separate noItemTypeImages preferences for OPAC and staff client
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4944 Summary: Create separate noItemTypeImages preferences for OPAC and staff client Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 At the moment the noItemTypeImages preference controls only the staff client. If my patch for Bug 4359 is approved it will affect both the staff client and the OPAC. Neither is ideal: There should be separate preferences for OPAC and staff client. -- 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 2

[Bug 6659] New: show opacnav on the log in page
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6659 Bug #: 6659 Summary: show opacnav on the log in page Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org It would be nice if the opacnav showed on the log in page in the OPAC (there's plenty of room there). -- 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 1

[Bug 6253] New: Unified Patron Search subroutine
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6253 Bug #: 6253 Summary: Unified Patron Search subroutine Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Patrons AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 1707, 4340, 4945, 5266, 5595, 5730, 5945, 6127, 6217, 5676 Currently Koha uses two patron search routines, Search() and SearchMember(). SearchMember() is used in most places where a patron search is performed, and does not respect Extended Attributes, branchcode/categorycode limits or paging of results. It does, however, return exact matches for cardnumbers quickly, making it very desirable for Circulation. Search() is only used on members/member.pl to do an in-depth search of patrons. It makes use of SQLHelper.pm, which gives us support for Extended Attributes OR branchcode/categorycode limits (can't have both, it seems) and results paging. It's easy to add new fields from the borrowers table to search. Koha should really only have 1 search routine for searching for patrons. This routine should support Extended Attributes, branchcode/categorycode limits and pagination. Exact matches on cardnumber OR unique, searchable Extended Attributes should return immediately, without having to go through the full search routine. It should also be easy to configure which fields in the borrowers table are searchable. -- 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 52