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

[Bug 10842] New: Allow for new type of LDAP authentication - Further Enhancement
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '14

11 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10842 Bug ID: 10842 Summary: Allow for new type of LDAP authentication - Further Enhancement Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org This is related to Bug 7379 where Elliott Davis describes a new authentication method as follows: For some ldap setups there is a different sequence for authentication that koha doesn't account for. The steps are: 1) Bind with a service account 2) Search for user entered 3) Bind as user if found The final patch that went in allowed for a method as follows: 1) Bind with an Anonymous user 2) Search for user entered 3) Bind as user if found. This is close to what Elliott described but not exact. My patch enclosed adds the original method into the accepted and pushed patch such that the initial bind can take place upon a specified service user OR and an anonymous user. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 10908] New: Fix broken auth_by_bind LDAP mode
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '14

11 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10908 Bug ID: 10908 Summary: Fix broken auth_by_bind LDAP mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: robin(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Bug 7973 breaks LDAP for many users, particularly those using active directory by removing the normal auth_by_bind behaviour and requiring that there is an anonymous user to search LDAP with. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 7686] New: Tax rate wrong calculation in reception summary page
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '14

10 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7686 Priority: P3 Change sponsored?: --- Bug ID: 7686 Assignee: koha(a)univ-lyon3.fr Summary: Tax rate wrong calculation in reception summary page QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: koha(a)univ-lyon3.fr Hardware: All Status: NEW Version: rel_3_6 Component: Acquisitions Product: Koha Created attachment 8098 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8098&action=edit Tax rate wrong calculation in reception summary page In the Already received table (bottom of the page) : Tax rate is purely added to Total without beeing multiplied by it example for a 5,5% tax rate (0,055) on a 455 Total : The Total displays 455,06 (455 + 0,055 round to 0,06) instead of 455 + (455 x 0,055)= 480,02. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 11129] New: Limiting the display of Serial issues OR Searching a specific Serial issue
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '14

09 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11129 Bug ID: 11129 Summary: Limiting the display of Serial issues OR Searching a specific Serial issue 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com One can easily have thousands of Serial issue items in the database. Currently they are shown in the OPAC and Staff Client in one huge table. Finding and placing a hold on the desired issue number is hard. Also there are performance considerations when showing huge amounts of issues unnecessarily. By filtering the display of issues before they are loaded on screen, we can fulfill those requirements. Changing the default view from huge blob to the most recent items saves DB effort. All these modifications apply only to biblios which have subscriptions and more than AllSerialIssuesDisplayThreshold -system preference items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 7901] New: Add batch delete borrowers script
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '14

09 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7901 Priority: P5 - low Change sponsored?: --- Bug ID: 7901 Assignee: gmcharlt(a)gmail.com Summary: Add batch delete borrowers script QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: kyle.m.hall(a)gmail.com Hardware: All Status: NEW Version: master Component: Command-line Utilities Product: Koha Add simple script to batch delete borrowers via a list of cardnumbers. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 7413] New: Allow OPAC renewal x days before due date
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '14

09 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7413 Bug #: 7413 Summary: Allow OPAC renewal x days before due date Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com Currently RenewalPeriodBase can be set to 2 different options: 1) When renewing checkouts, base the new due date on current date. This means that when a patron renews the item at the checkout date, the renewal counter will increment, but the due date will not change - the loan period is still the same. If he renews one day after checkout - he will get a reneal of one day and so on. 2) When renewing checkouts, base the new due date on the old date of the checkout. This means the renewals can be done immediately after checkout. So if you allow 3 renewals and a loan period of 4 weeks, the patron can log into his account and do all the renewals immediately. This will mean he effectively gets a loan period of 4 + 3*4 weeks = 16 weeks. I see no reason why a clever student shouldn't do this to make sure he can keep the text books as long as possible without any holds forcing him/her to return the books. One solution here would be to allow renewals only x days before the book is due. As the loan periods can be very different (overnight loans, 4 weeks, 7 days...) it would be cool if this could be implemented in circulation rules. -- 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 79

[Bug 8244] New: Script to find exporter problems
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '14

04 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8244 Priority: P5 - low Change sponsored?: --- Bug ID: 8244 CC: jonathan.druart(a)biblibre.com Assignee: julian.maurice(a)biblibre.com Summary: Script to find exporter problems Severity: enhancement Classification: Unclassified OS: All Reporter: julian.maurice(a)biblibre.com Hardware: All Status: NEW Version: master Component: Test Suite Product: Koha About one month ago, we (BibLibre) discover a bug in our source code. The problem was: a page that used to work correctly suddenly refuse to work because of "Undefined subroutine &get_infos_of at C4/Items.pm (line 1075)" (approximative message) in reserve/request.pl The piece of code in cause was a "use C4::Members" in C4/Budgets.pm. A modification of C4::Budgets was causing reserve/request.pl to crash... (ouch!) In fact it introduced a circular dependency. To avoid this kind of discovery, we decide to write a script that try to detect as many problems as possible. Patch and description follow. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 6716] New: Database Documentation
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '14

03 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6716 Bug #: 6716 Summary: Database Documentation Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: ASSIGNED Severity: enhancement Priority: P5 Component: Developer documentation AssignedTo: nengard(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org This is a bug that will have many patches. I have (as doc manager) agreed to document the mysql structure in Koha. To make it easy for others to submit patches and help me I'll submit a patch with what I've done in the day (or that time of day) so that others can submit patches as well without us doing the same work. It was voted that I will enter comments using the -- notation, for example: `frameworkcode` varchar(4) NOT NULL default '', --primary key, identifier for the framework table This report should not be closed until all fields have been documented. If you're adding new fields please document them using the above notation when adding them. -- 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 160

[Bug 5340] New: bulk subscription renewal
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '14

27 Mar '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5340 Summary: bulk subscription renewal Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Subscription_renew al_RFC OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 A feature will be added to bulk renew subscription (from the expiring subscription check screen) -- 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 10916] New: confusing notes on serial results
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '14

27 Mar '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10916 Bug ID: 10916 Summary: confusing notes on serial results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Created attachment 21252 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=21252&action=edit serial notes results When you search for a subscription you see a notes column. This notes column is a bit confusing because it shows the 500 note from the bibliographic record along with the notes that are on the subscription, but when you click the subscription you only see the note from the subscription and there is no indications of where the other text is coming from. I vote that we don't show the 500 notes on the serials page - or that we label it so that it's clear where it's coming from because it's confusing a lot of libraries. In the attached example the Notes column says: Vols. <18-> published: Warsaw : Polish Scientific Publishers. (Email to Nardecchia for vol. 36-41 and cont., they will provide. June 2013. IP 23/07/2013 created publication pattern--for some reason it didn't migrate correctly and SH created new publication pattern on 05/09/2013.) The part before the parens is from the 500 in the bib record and the part in the parens is the note on the subscription. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2