June 2015 - Koha-bugs - lists.koha-community.org

[Bug 14039] New: Add patron title to checkout screen
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '15

05 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14039 Bug ID: 14039 Summary: Add patron title to checkout screen Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When checking out an item to a user, it sounds more professional if the patron can be addressed as Mr / Mrs / Miss etc, but this information doesn't display to the staff member, who has to click on the details tab in order to find out how the patron should be addressed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 14340] New: 773x ISSN Index
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '15

05 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14340 Bug ID: 14340 Summary: 773x ISSN Index Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org 773$x should be an ISSN index. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 10636] New: patronimage should have borrowernumber as PK, not cardnumber
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '15

05 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10636 Bug ID: 10636 Summary: patronimage should have borrowernumber as PK, not cardnumber Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The patronimage table currently has cardnumber as its primary key rather than borrowernumber. patronimage.cardnumber in turn has a FK constraint referencing borrowers.cardnumber. This is less than ideal for a couple reasons: [1] DBIX::Class (see bug 8798) complains about it. In particular, any code that loads Koha::Database would litter the Apache logs with the following: DBIx::Class::Carp::__ANON__(): "might_have/has_one" must not be on columns with is_nullable set to true (Koha::Schema::Result::Borrower/cardnumber). This might indicate an incorrect use of those relationship helpers instead of belongs_to. at /usr/share/perl5/DBIx/Class/Relationship/HasOne.pm line 96 [2] Every other table that has an FK to borrowers uses borrowernumber as the referent. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 14336] New: SCO: Move embebbed Jscript code from sco-main.tt to new sco.js file
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '15

05 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14336 Bug ID: 14336 Summary: SCO: Move embebbed Jscript code from sco-main.tt to new sco.js file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org SCO: Move embebbed Jscript code from sco-main.tt to new sco.js file -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 1626] Trim whitespace from barcode inputs
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '15

05 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1626 Mason James <mtj(a)kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.koha-community. | |org/bugzilla3/show_bug.cgi? | |id=14335 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14335] New: SCO fails to strip leading/trailing whitespace in 'barcode' input field
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '15

05 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14335 Bug ID: 14335 Summary: SCO fails to strip leading/trailing whitespace in 'barcode' input field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org SCO fails to strip leading/trailing whitespace in 'barcode' input field -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 13354] New: z3950 admin: strip leading/training whitespace in fields, when saving Z39 entry
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '15

05 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13354 Bug ID: 13354 Summary: z3950 admin: strip leading/training whitespace in fields, when saving Z39 entry Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We have been bumping into a few problems recently, with users creating z39 entries with accidential hidden space ' ' characters in various field, which cause difficult to detect failures :/ it would be a good thing to strip leading/training whitespace in fields, when saving Z39 entries - to avoid this problem -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 14331] New: Order Records from staged file
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '15

04 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14331 Bug ID: 14331 Summary: Order Records from staged file Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: ed.veal(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using the "from staged file" option in acquisitions to order a batch of order records from a vendor there is no currency choice. The feature automatically uses the default currency. This can be a problem when a library is ordering from a vendor that is using different currency than the libraries default because what is recorded against the fund/budget is the default value and this would be incorrect due to exchange rates. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 14024] New: add reports to action logs
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '15

04 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14024 Bug ID: 14024 Summary: add reports to action logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Lately I've seen a lot of people deleting reports they shouldn't. I'd love it if there were a log for reports. So when you create it the action log keeps a record of what the SQL was and if you delete it it tracks who did the deleting. That way I can recover old SQL from the logs if need be. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 3206] OAI repositry deleted record support
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '15

04 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3206 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de --- Comment #16 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hm, I think initially including the deleted records when creating a set seems to go to far - you might probably not want those at this point. But once the set is created you want to inform about records removed from it. So changing the cronjob might not be necessary? -- You are receiving this mail because: You are watching all bug changes.

1 0