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

[Bug 14494] New: Terribly slow checkout caused by DateTime->new in far future
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14494 Bug ID: 14494 Summary: Terribly slow checkout caused by DateTime->new in far future Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org An expiry date of 9999-12-31 for organizations was a nice idea :) But checking out an item to that patron takes 1 minute or longer ! The cause? The following lines in CanBookBeIssued seem to be the main cause: my $expiry_dt = DateTime->new( year => $y, month => $m, day => $d, time_zone => C4::Context->tz, ); This call takes forever with 9999-12-31 when the timezone is not 'floating' or 'UTC', but e.g. Europe/Amsterdam. If the timezone is UTC, it takes 0.0002 seconds. DateTime gives the following advices: === Do not try to use named time zones (like "America/Chicago") with dates very far in the future (thousands of years). The current implementation of DateTime::TimeZone will use a huge amount of memory calculating all the DST changes from now until the future date. Use UTC or the floating time zone and you will be safe. •use UTC for all calculations If you do care about time zones (particularly DST) or leap seconds, try to use non-UTC time zones for presentation and user input only. Convert to UTC immediately and convert back to the local time zone for presentation The results DateTime.pm produces are predictable and correct, and mostly intuitive, but datetime math gets very ugly when time zones are involved ... === We are not doing that currently. We use in C4::Context: DateTime::TimeZone->new(name => 'local') Could we implement the calculation/presentation advice of DateTime in Koha somehow? -- You are receiving this mail because: You are watching all bug changes.

1 50

[Bug 13452] New: Average checkout report always uses biblioitems.itemtype
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13452 Bug ID: 13452 Summary: Average checkout report always uses biblioitems.itemtype Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The average checkout report reports/issues_avg_stats.pl always uses biblioitems.itemtype, regardless to item-level_itypes system preference. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 7045] New: Default-value substitution inconsistent
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7045 Bug #: 7045 Summary: Default-value substitution inconsistent Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: ruth(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com If you supply a default value in a framework field, you may include YYYY, MM, DD, and user, to substitute for the year, month, day, and currently-logged-in username, respectively. The downside of this is that the word "user" cannot be used in a default value for a note! Patch coming shortly, to change the substitution to require USER, and to allow the use of YY to insert the last two digits of the year. -- 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 25

[Bug 10294] New: when the word "user" is included in default in framework, surname of login creating record inserted
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10294 Bug ID: 10294 Summary: when the word "user" is included in default in framework, surname of login creating record inserted Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: drnoe(a)bywatersolutions.com CC: m.de.rooy(a)rijksmuseum.nl When the word "user" is included in a default value in a MARC subfield structure of a tag in a framework, the surname of he user login creating record is inserted in the place of the word "user." Create the deafualt value in the framework -In MARC frameworks. -Select a MARC structure of any framework to edit. -Select the subfields to edit. -Select the Edit Subfields button. -Select Display more constraints of any subfield tab. -Include "user" in the default value. (make sure hidden is st to 0). -Save Changes. Create a new record -In Cataloging, select New Record with the edited framework -Go to the tag with the default value. -The surname of the user with which you create the new record will be in the tag in the place of user. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 11039] New: SIP Server responds to valid CHECKIN to SC but fails to checkin item on Koha
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '15

01 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11039 Bug ID: 11039 Summary: SIP Server responds to valid CHECKIN to SC but fails to checkin item on Koha Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: barry(a)oslo.ie QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com If a patron borrowers an item from Branch_A and attempts to return it in Branch_B, via a selfcheck system, the SIP server will respond with an valid CHECKIN response giving the impression the item has been checked in successfully. However, when the borrower record is viewed via the Staff client the patron still has the item checked out. This only appears to happen if the SysPref "AllowReturnToBranch" is set to "only the library the item is from". Switching this SysPref to "to any library" does apply the checkin. The same item - checked out in Branch_A and checked in at Branch_B - does flag an error on the staff client, dissallowing the checkin. This is not passed correctly to the SIP server. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 11399] New: batch Rebuild Items Tables
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '15

01 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11399 Bug ID: 11399 Summary: batch Rebuild Items Tables 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: stephane.delaune(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org This script rebuilds the non-MARC DB items table from the MARC values (eg. in 995 for unimarc, 952 in marc21). You can/must use it when you change your mapping. This script is similar to batchRebuildBiblioTables(which works on biblio an biblioitems table), but works on items only. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 14149] New: Labels: Make barcode width and height scaling editable
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '15

01 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14149 Bug ID: 14149 Summary: Labels: Make barcode width and height scaling editable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: cnighswonger(a)foundations.edu QA Contact: testopia(a)bugs.koha-community.org Provide an extension of Bug 14107 to apply to barcodes on label layouts as well. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 14359] New: RDA: 700/710/711 display in XSLT Bug fix for Contributors
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '15

01 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14359 Bug ID: 14359 Summary: RDA: 700/710/711 display in XSLT Bug fix for Contributors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: wsalesky(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org 1) Repeated 7xx are not correctly displayed. Example with 3 700: Contributor(s): Wiesflecker, HermannNovotny, Alexander [ed.]Pickl, Othmar [ed.] | Missing separators and spaces between names. 2) There is always a pipe appearing at the end of the "Contributors". 3) Also, the little icon to the authority record is broken by this pat See http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13382#c45. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 11967] New: Add support for RMA notices to Acquisitions.
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '15

30 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11967 Bug ID: 11967 Summary: Add support for RMA notices to Acquisitions. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: fcapovilla(a)live.ca QA Contact: testopia(a)bugs.koha-community.org Created attachment 26466 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=26466&action=edit Add RMA support for Acquisitions. This patch adds the "Return order" option to the acquisitions menu which lets you print CSV file for Manual RMA management. You can also send RMA notices by email using a configurable notice (code: RMA). Preparation : * Create some vendors with baskets of received items. Make sure your vendors have a valid email address that you control so you can receive the emails we will generate. Test case : * Go in the acquisitions section. * Click on the "Return order" menu item. * Search for a vendor which has some orders. * You should see a table containing basket numbers. Clicking on a line of the table should display the items contained in the basket. Select some items by clicking on their checkboxes. * At the bottom of the page, select the option to export the list to a file (CSV), and click on the "Generate RMA" button. * The CSV should contain some informations on all the items you selected and their booksellers. * Select the option to send an email and click on the "Generate RMA" button. * An email should be sent to all appropriate booksellers. The email should have the format defined in the RMA letter. Sponsored-by: CCSR ( http://www.ccsr.qc.ca ) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 14745] New: RDA: RDA Registry metadata
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '15

30 Sep '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14745 Bug ID: 14745 Summary: RDA: RDA Registry metadata Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: hector.hecaxmmx(a)gmail.com Reporter: hector.hecaxmmx(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org RDA Registry is a set of metadata to serialize RDA metadata and MARC records in other formats, using the constrained and uncostrained elements of RDA. You can see examples in turtle (text/turtle) in <http://www.rdaregistry.info/Examples/> -- You are receiving this mail because: You are watching all bug changes.

1 2