January 2016 - Koha-bugs - lists.koha-community.org

[Bug 15486] New: Restrict number of holds placed by day
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15486 Bug ID: 15486 Summary: Restrict number of holds placed by day Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All URL: http://devs.bywatersolutions.com/projects/restrict-num ber-of-holds-placed-by-day/ OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com For example: A patron is allowed to place 5 holds (or other variable number set by the library) per day but can not exceed 30 holds (set by circ rules). Work to be done: 1) Add new database column reservesallowed_daily to the table issuingrules 2) Add new database column “created_on” to the table reserves 3) Modify C4::Reserves::AddReserve to populate “created_on” with the current timestamp 4) Add new column “Holds allowed (daily)” to the circulation and fine rules. 5) Modify “Holds allowed (count)” to “Holds allowed (total)” for clarity 6) Modify CanItemBeReserved to check if max daily holds has been exceeded If so, it must return new error code ‘TooManyReservesToday’ 7) Modify all code calling CanItemBeReserved to handle this new error code 8) Add unit tests for new CanItemBeReserved behavior Seeking Co-Sponsors: http://devs.bywatersolutions.com/projects/restrict-number-of-holds-placed-b… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15485] New: Show 520 on lists
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15485 Bug ID: 15485 Summary: Show 520 on lists Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Lists Assignee: jweaver(a)bywatersolutions.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Goal of Development: To add 520 field to lists Work to be done: 1) Split system preference for lists XSLT into a separate system preference from search results XSLT 2) System preference will default to existing default search results XSLT 3) Once the development is in Koha, add custom XSLT file to your server to display the 520 field for lists -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15484] New: subscription enddate is miscalculated when it has predictable non published issues
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15484 Bug ID: 15484 Summary: subscription enddate is miscalculated when it has predictable non published issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com In cases when subscription have non standard number of issues ( example for a weekly serial 44 instead of 52 a year because there is no publication in Summer), the enddate is miscalculated if you let the program do. May be that not diserves a code correction because it seems there are 2 solutions to avoid this ( if I get it correctly) : - Enter the enddate by yourself - Set numberlength to 52 (if your WhenMoreThan parameter in the numbering pattern is set to 44 the prediction should work). May be but maybe I miss something... And if the case, that would diserve to be clearly explained. Olivier Crouzet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15483] New: in a weekly serial subscription, the second planned issue corresponds to third publisheddate
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15483 Bug ID: 15483 Summary: in a weekly serial subscription, the second planned issue corresponds to third publisheddate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Created attachment 46333 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=46333&action=edit skipping_second_planneddate in a weekly serial subscription, the second planned issue corresponds to third plannedddate Lest's take the following simple example : a weekly serial, subscription startdate 2016-01-01, enddate 2017-12-31, beginning by number 1 planned on 2016-01-02 we are expecting number 2 to be planned on 2016-01-09 but the results is : N°1 - 2016 2016-01-02 N°2 - 2016 2016-01-16 N°3 - 2016 2016-01-23 Curiously, it works from the 2016-01-04 as first planneddate. N°1 - 2016 2016-01-04 N°2 - 2016 2016-01-11 N°3 - 2016 2016-01-18 But, we have sometimes the same problem when going through one year to another : N°43 - 2015 2015-12-21 N°44 - 2016 2016-01-04 N°1 - 2016 2016-01-18 Olivier Crouzet -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 7314] New: Remove singleBranchMode system preference in favour of counting configured branches
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7314 Bug #: 7314 Summary: Remove singleBranchMode system preference in favour of counting configured branches Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P4 Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: jonathan.druart(a)biblibre.com Instead of relying on a system preference to determine whether there is only a single branch in the system or not, why not just count how many distinct branches are in the branches table? This will reduce the number of moving parts, so to speak. Proposed subroutine in C4::Branch: GetBranchCount(). No inputs, returns integer value 0 or greater, corresponding to the output of SELECT count(*) FROM branches; Once this subroutine is in place, we can slowly remove references to singleBranchMode syspref, which will fix numerous bugs involved with that particular feature. -- 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 4

[Bug 12489] New: Ajax checkout table: no "loading..." popup
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12489 Bug ID: 12489 Summary: Ajax checkout table: no "loading..." popup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There is a "Loading..." stuff on the checkouts table of the "Check out" tab, but no on the table on the "Details" tab (member/moremember.pl). A line "No data available" is displayed and could be confusing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 15138] New: typo in reports/borrowers_out.pl - issues.timestamap
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15138 Bug ID: 15138 Summary: typo in reports/borrowers_out.pl - issues.timestamap Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 14426 Referenced Bugs: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14426 [Bug 14426] SQL Injection in Staff Client -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 15148] New: Serials: Test prediction pattern starts at First issue date, not Subscription start date
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15148 Bug ID: 15148 Summary: Serials: Test prediction pattern starts at First issue date, not Subscription start date 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: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To reproduce: add or edit a serial, Set dates for First issue, Subscription length Subscripton start Test prediction pattern. You will get a list with the number of issues matching 'subscription length' value, but starting from First issue date, not Subscription start date. Expected: use subscription start and end date to determine the range of issues to show in prediction. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 15149] New: Serials: Test prediction pattern does not consider Subscription start and end date
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15149 Bug ID: 15149 Summary: Serials: Test prediction pattern does not consider Subscription start and end date 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: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To reproduce: add or edit a serial, Set dates for First issue, Subscripton start Subscription end do not set Subscription length. Test prediction pattern. You will get a list of 1000 issues, starting from first issue date (not subscription start date) and going well beyond subscripton end date. Expected: show only the issues within the date range. If subscription length is set to a number of issues, you only get these in the pattern. Also expected: start at subscription start date, not first issue date. I opened an extra bug for that, see Bug 15148 (Numbering pattern in my tests was set to 'Number') -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 15480] New: Number of issues displayed by prediction pattern test and setting of not published issues
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '16

06 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15480 Bug ID: 15480 Summary: Number of issues displayed by prediction pattern test and setting of not published issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com May be this post could have been added to bug 15148 and 15149, but it's seen here under a different aspect, so I opened a new bug. By now the number of issues displayed by prediction pattern test is related to the number set in "subscription length". But sometimes when a serial has predictable not published issues to be set on the prediction pattern checkboxes, this behaviour can make it impossible : Imagine a weekly serial that has only 46 issues a year, say it's not published in August and during the last 2 weeks of december. Initially, you would be tempted to set the number of issues to 46, but then, the last november and the december issues will not be displayed by the prediction pattern test and so you will not be able to check all the not published issues. >From what I experienced, you can set the issues number to the standard 52, and if the WhenMoreThan parameter of numbering pattern is correctly set to 46, it will be ok. But that is not very intuitive and should be at least documented. And may be, it would be preferable to fix automatically this parameter according to periodicity. Olivier Crouzet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1