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

[Bug 7802] New: A MySQLism is used to get the current date.
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7802 Priority: P5 - low Change sponsored?: --- Bug ID: 7802 Assignee: gmcharlt(a)gmail.com Summary: A MySQLism is used to get the current date. QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: marc(a)msys.ch Hardware: All Status: NEW Version: unspecified Component: Database Product: Koha To get todays date, the MySQL only function CURDATE() or CURRENT_DATE() is being used in many places. Neither CURDATE() nor CURRENT_DATE() must be used, but instead the standard form CAST(now() AS date). -- You are receiving this mail because: You are watching all bug changes.

1 49

[Bug 7172] New: Data Persistency
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7172 Bug #: 7172 Summary: Data Persistency Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 - high Component: Architecture, internals, and plumbing AssignedTo: paul.poulain(a)biblibre.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com Blocks: 7119 We need to fix up the code throughout the system to be able to handle data faster-than-CGI processors like Plack, FastCGI or mod_perl. At this time, most of Koha can run okay, but when errors happen, they crash HARD. Some issues than need attention: nested subroutines: mod_perl, and I think other systems, turn each script into a subroutine. If you have subroutines in subroutines (as we do in C4 and some of the scripts), and an inner subroutine modifies a variable declared outside in the outer subroutine, you will get an error "variable will not stay shared". This can sometimes (always?) be fixed by using "our" instead of "my". Or using better coding practices :) memory leaks: some memory may not be released, so a persistent engine could bloat over time. other issues may come up, as well. -- 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 48

[Bug 11071] New: RDA Helper
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '15

15 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11071 Bug ID: 11071 Summary: RDA Helper Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be great to have an RDA Helper like MarcEdit has (which is not open source - http://marcedit.reeset.net/features) built in to Koha so that you can easily add RDA fields to your MARC record with the click of a button or via a batch biblio modification tool. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 4888] New: pre-set of field indicators value
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '15

15 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4888 Summary: pre-set of field indicators value Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: s.bolelli(a)libercoop.it QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 Building a MARC Framework now is not possible to set default values for the field indicators. It would be very useful to set default values for indicators because in many cases they change very rarely -- 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 37

[Bug 10314] New: CanItemBeReserved does not respect the holds policies
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '15

15 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10314 Bug ID: 10314 Summary: CanItemBeReserved does not respect the holds policies Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle.m.hall(a)gmail.com CC: gmcharlt(a)gmail.com CanItemBeReserved will return 1 as long as the circulation rules have a non-zero number of holds allowed and the patron hasn't reached his or her "Holds allowed" count. However, the subroutine completely ignores the holds policies which would contravene reserving the item even if the patron has not reached the maximum holds allowed count. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 10839] New: Claim report of all vendors
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '15

14 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10839 Bug ID: 10839 Summary: Claim report of all vendors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: vimal0212(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Dear Friends, To get list of serial claims, librarian has to select each vendor. This facility is convenient for libraries have single serial vendor. Libraries suscribing serials direct from publishers need to select each vendor to get serial claims. In our library, 100 journals / magazines are receiving direct from publishers. In this situation, generating claim report is very time consuming. It is very convenient to get list of claims from all suppliers with one click from serial module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 11368] New: Add script to import Lexile scores
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '15

14 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11368 Bug ID: 11368 Summary: Add script to import Lexile scores Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha needs a script to automate the importing of Lexile score data for titles that have available scores but are not currently in the title's record. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 4948] New: canceling a hold missing steps for existing holds
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '15

13 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4948 Summary: canceling a hold missing steps for existing holds Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: cgi-bin/koha/circ/waitingreserves.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Hold requests 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 Estimated Hours: 0.0 on holds waiting report you click cancel and it tells you that there is a hold for someone else the button below that says submit query which isn't helpful and it doesn't present you with the option to confirm or cancel the hold or a way to print a slip -- all things that are needed in this scenario -- 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 10020] New: Remove old code related to 'ethnicity'
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '15

13 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10020 Bug ID: 10020 Summary: Remove old code related to 'ethnicity' Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de While updating our database documentation I found ethnicity and I suspect, that this is no longer used in current versions of Koha. Related code I found so far: - database table ethnicity - database columns ethnicity and ethnotes in borrowers and deletedborrowers - ethnicitycategories in C4/Members.pm - some code in memberentry.pl I can see no way in current versions for a library to enter data in the related fields and tables. Also we have a very flexible feature for patron attributes now, that I think, should make it possible to replicate this feature, if a library wanted to use it. -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 9305] New: Attach adults to each other
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '15

13 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9305 Bug ID: 9305 Summary: Attach adults to each other Classification: Unclassified 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: nengard(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice if you could attach adults to each other the way you can attach children to adults. That way you can group family members more accurately. This data would be visible only to the staff of course - unless patrons give permission to show it each other - and my request in http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9303 is filled :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2