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

[Bug 13379] New: authorised_values.category is varchar(16)
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13379 Bug ID: 13379 Summary: authorised_values.category is varchar(16) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org But borrower_attribute_types is varchar(10). So if you try to link a patron attribute type with an AV category with a length > 10, the link won't be done. Also, I propose to extend this field to varchar(32). -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 12486] New: Appendix G (Resetting the Koha Database) using DELETE instead of TRUNCATE
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12486 Bug ID: 12486 Summary: Appendix G (Resetting the Koha Database) using DELETE instead of TRUNCATE Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Manual appendix G, "Resetting the Koha Database"[1] talks about resetting Koha database with TRUNCATE SQL command. As Robin Sheat[2] point me this is a deprecated way. Now, with MySQL >~5.5 the way is just: DELETE FROM biblio; And the constraints will propagate the delete to (ALMOST) all other tables. [1] http://manual.koha-community.org/3.16/en/resetkohadb.html [2] http://lists.katipo.co.nz/public/koha/2014-June/039701.html I'll fill another bug about updating also bulkmarcimport.pl -d option. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 12598] New: Allow tools/import_borrowers.pl to be used from the command line.
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12598 Bug ID: 12598 Summary: Allow tools/import_borrowers.pl to be used from the command line. 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Many libraries have the need to automate the importing of patrons into Koha from external sources. It would be nice if we could use Koha's own import_borrowers.pl to do that from the command line, in the same way as tools/export.pl can be used from both the staff interface and the command line. -- You are receiving this mail because: You are watching all bug changes.

1 72

[Bug 13696] New: Add support for Font Awesome icons in Koha
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13696 Bug ID: 13696 Summary: Add support for Font Awesome icons in Koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Font Awesome is similar to Glyphicons included in Twitter Bootstrap, except better in every way and more Free. -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 10454] New: Failure to lock could generate duplicate card numbers
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10454 Bug ID: 10454 Summary: Failure to lock could generate duplicate card numbers Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In C4::Members.pm there is a function AddMembers_Opac which calls fixup_cardnumber. The problem is there is no locking to ensure that someone else doesn't add a member at the same time and create a duplicate card number. This patch adds the missing locking in. I've left commented wait code in, so that the person testing this can switch tabs or browsers to test that the locking doesn't catastrophically break things. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 11780] New: Need to prevent specific fields from being overwritten with z39.50 import
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11780 Bug ID: 11780 Summary: Need to prevent specific fields from being overwritten with z39.50 import Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In our previous LMS we could associate specific marc fields as "local use" in the configuration. If a marc record was overwritten with another via z39.50 these local use files remained in the new record. (if it was in a field that also contained data in the incoming record, then a 2nd instance for that field was created - e.g. multiple 500 notes, etc e.g. we need to keep our own 001 control numbers as Analytics links from other records get broken if this is replaced with the 001 of a new record say from LC or NLM. At the moment I have to note the existing 001 & put that value in again after replacing the record. There are also local notes fields etc that we would want to keep. It would be useful if this setting is also framework specific. (e.g. to keep certain fields for serials but not for monographs etc) -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 5560] New: pagination option for lists
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5560 Summary: pagination option for lists Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Virtual Shelves AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Right now lists show 20 items per page and this is not changeable. I would like to see an option at list creation that lets me say how many items I want to show per page. -- 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 8

[Bug 12759] New: Add ability to pass list contents to batch item modification/deletion tools
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12759 Bug ID: 12759 Summary: Add ability to pass list contents to batch item modification/deletion tools Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be a great timesaver if the records associated with a particular list can be passed into the Batch item modification and batch item deletion tools. At the moment I have to run a report to extract the item barcode numbers from the list then open the resulting spreadsheet and copy & paste these into the batch modification tool. Ideally the batch modification/deletion tools need another input option to choose a particular list (that you can access), or alternatively have a new option in the list view screen to pass selected records to batch modification/deletion. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 12904] New: Force browser to load new javascript files after upgrade
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12904 Bug ID: 12904 Summary: Force browser to load new javascript files after upgrade Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org A common issue with Koha seems to be that the web browsers continue to use cached js files after an upgrade. If we append the version as a parameter, we can force the browser to update the javascript files. -- You are receiving this mail because: You are watching all bug changes.

1 44

[Bug 11626] New: Cannot receive serial issues after subscription expiry date
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11626 Bug ID: 11626 Summary: Cannot receive serial issues after subscription expiry date Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Some of our serials subscriptions were not renewed after 31/12/2013 but I cannot receive any of the outstanding 2013 issues unless I renew the subscription record (a couple of publishers are about 3 months late with their printing/postage schedules compared to the subscription/cover dates). For a couple of these titles we do not have a 2014 subscription so it is not appropriate to renew the subscription record. We should still be able to receive late issues after the subscription expiry date (the date published for these issues would in most cases be on or before the expiry date) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6