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

[Bug 7377] New: Feature Request: Add Lexile Search for Ranges of Lexile Scores
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '15

07 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7377 Bug #: 7377 Summary: Feature Request: Add Lexile Search for Ranges of Lexile Scores Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: lzuares(a)collsk12.org QAContact: ian.walls(a)bywatersolutions.com I would really appreciate the ability to search by Lexile range from within the OPAC and/or Staff Client. I was doing some Googling and came across two submitted patches, which don't appear to have made it into 3.6. The links are listed below. -Thanks http://lists.koha-community.org/pipermail/koha-patches/2010-January/010872.… http://lists.koha-community.org/pipermail/koha-patches/2010-January/010874.… -- 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 10707] New: inventory not removing lost status
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '15

07 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10707 Bug ID: 10707 Summary: inventory not removing lost status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When doing inventory it should remove the lost status if an item is marked seen ... cause if it's seen it's not lost. The problem / discussion here is on what should happen to items that are still 'checked out' and marked lost - should the patron be refunded? -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 9942] New: Circulation module cannot anonymise if anonymity user is not set up correctly.
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '15

06 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9942 Bug ID: 9942 Summary: Circulation module cannot anonymise if anonymity user is not set up correctly. Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: peterAtKohaBugzilla(a)pck.co.nz CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is related to bug 6506. The MarkIssueReturned sub of Circulation.pm contains the comment: # The default of 0 does not work due to foreign key constraints # The anonymisation will fail quietly if AnonymousPatron is not a valid entry As noted on bug 6506, this is unacceptable. Severity cloned from that bug. This is a guess, but I surmise that how to test is to enable privacy, check out a book, return that book, and see if the book is in your borrowing history. If it is, that's a fail. If it isn't, that's a pass. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 9936] New: SIP2 should use C4/Auth.pm for user authentication
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '15

05 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9936 Bug ID: 9936 Summary: SIP2 should use C4/Auth.pm for user authentication Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: colin.campbell(a)ptfs-europe.com SIP2 checks the password directly against the database instead of using C4/Auth.pm. This means that it won't work with LDAP and possibly CAS. Also, we should do authentication the same everywhere in Koha to ensure consistency. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 10253] New: tax rate only takes 1 decimal point
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '15

05 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10253 Bug ID: 10253 Summary: tax rate only takes 1 decimal point Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com Created attachment 18163 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=18163&action=edit tax rate preference See attached. The tax rate where I am is 6.85, but I can't get that to show in the tax pull down. It turns it in to 6.8 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 8215] New: Add Course Reserves
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '15

04 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8215 Priority: P5 - low Change sponsored?: --- Bug ID: 8215 CC: gmcharlt(a)gmail.com Assignee: koha.sekjal(a)gmail.com Summary: Add Course Reserves Severity: enhancement Classification: Unclassified OS: All Reporter: kyle.m.hall(a)gmail.com Hardware: All Status: NEW Version: master Component: Hold requests Product: Koha Add a system for placing academic course reserves. -- You are receiving this mail because: You are watching all bug changes.

1 201

[Bug 7947] New: 440/490 Koha Mapping
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '15

02 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7947 Priority: P5 - low Change sponsored?: --- Bug ID: 7947 Assignee: gmcharlt(a)gmail.com Summary: 440/490 Koha Mapping QA Contact: koha.sekjal(a)gmail.com Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com URL: cgi-bin/koha/admin/koha2marclinks.pl Hardware: All Status: NEW Version: master Component: Cataloging Product: Koha The new Marc standard is that the 490a is the series title, but it's still mapped to 440a here: cgi-bin/koha/admin/koha2marclinks.pl We should probably change the default mapping. Nicole -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 9480] New: Set barcode width and height configurable with system preferences in patron card creator
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '15

01 Aug '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9480 Bug ID: 9480 Summary: Set barcode width and height configurable with system preferences in patron card creator Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt Problem: - barcode width scale is always set to 0.8 of the total width - barcode height scale is always set to 0.01 of total height - happens in 3.8.X, 3.10.X and master code Solution: - create a system preference to control width scale name BarcodeWidthScale (default: 0.8) - create a system preference to control height scale name BarcodeHeightScale (default: 0.01) - change Patroncard.pm to use the variables instead of the default values (if the sysprefs are empty uses the default values). -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 10192] New: Add {ISBN13} as new parameter to OPACSearchForTitleIn
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '15

31 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10192 Bug ID: 10192 Summary: Add {ISBN13} as new parameter to OPACSearchForTitleIn Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de The {ISBN} will only provide you with a ISBN10, never with a ISBN13, even if one is present in the record. This is because we actually force ISBN10 in GetNormalizedISBN. Some newer services need ISBN13 to work correctly, so we should also make that available in the templates and OPACSearchForTitleIn. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 9296] New: overduerules table needs restructuring to allow future extension
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '15

31 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9296 Bug ID: 9296 Summary: overduerules table needs restructuring to allow future extension Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: master Hardware: All URL: http://intranet/cgi-bin/koha/tools/overduerules.pl OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: mjr(a)software.coop Reporter: mjr(a)software.coop The overduerules table almost hard-wired to three standard notices, with fields like delay1, delay2, delay3. I want to expand it in the future, so I plan to change it to the following: CREATE TABLE `overduerules` ( -- overdue notice status and triggers `overduerules_id` mediumint NOT NULL AUTO_INCREMENT, `branchcode` varchar(10) NOT NULL default '', -- foreign key from the branches table to define which branch this rule is for (if blank it's all libraries) `categorycode` varchar(10) NOT NULL default '', -- foreign key from the categories table to define which patron category this rule is for `delay` int(4) default NULL, -- number of days after the item is overdue that this notice is sent `letter` varchar(20) default NULL, -- foreign key from the letter table to define which notice should be sent `debarred` varchar(1) default 0, -- is the patron restricted when this notice is sent (1 for yes, 0 for no) `typecode` varchar(10) NOT NULL default '1', -- 1 2 3 for first second third, may be extended later PRIMARY KEY (`overduerules_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; I think the existing user interface and cronjob can be made to work with this structure pretty easily. Patch to follow. -- You are receiving this mail because: You are watching all bug changes.

1 18