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

[Bug 4974] New: process_koc.pl fails to display date and time of return
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4974 Summary: process_koc.pl fails to display date and time of return Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 On a successful return, process_koc.pl displays something like this: Checked in TITLE (BARCODE) from PERSON (PATRONBARCODE): The date and time is supposed to be displayed after the trailing colon. On lines 276, 297, 318 and 344 the script tries to assign datetime to @output: datetime => $circ->{ 'datetime' } but in the function parse_command_line on line 189 the timestamp from the .koc-file is split into $date, $time and $id, and date and time are returned seperately. A couple of solutions spring to mind: - Returning the timestamp from parse_command_line and assigning that to datetime in @output - Concatenating date and time in the assignment to datetime. Not sure which makes most sense... -- 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 1

[Bug 4871] New: Debian packaging should use start-stop-daemon, not daemon
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4871 Summary: Debian packaging should use start-stop-daemon, not daemon Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: lars(a)catalyst.net.nz ReportedBy: lars(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 start-stop-daemon is the canonical tool in Debian for init.d scripts to start and stop server processes. daemon is used less. It would be good for Koha packaging to follow mainstream here. -- 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 2

[Bug 4875] New: koha-remove, koha-restore should have options similar to --request-db
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4875 Summary: koha-remove, koha-restore should have options similar to --request-db Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: lars(a)catalyst.net.nz ReportedBy: lars(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 koha-create has the --request-db option, which allows the part of Koha instance creation that requires administrative database server access to be done outside the script. koha-remove and koha-restore should get a similar option so they, too, do not require administrative database access. This is necessary in situations where the person installing and administering Koha does not have admin access on the db server. -- 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 2

[Bug 4879] New: lint-like tool for Koha database contents
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4879 Summary: lint-like tool for Koha database contents Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: lars(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 It would be really cool to have a tool that checks that the contents of a Koha database are correct. For example, it might check that the MARC records are at least syntactically correct. -- 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 1

[Bug 4855] New: Tools/Export does not tell browser file size
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4855 Summary: Tools/Export does not tell browser file size Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: lars(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When exporting the catalogue via tools/export, the download works fine, but if the catalogue is large, the user does not know how long it will take. Koha does not tell the browser the size of the file (Content-Length HTTP header I assume), so the browser cannot estimate the remaining time. It would be nice if it did. -- 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 1

[Bug 4824] New: Planning showing a -0
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4824 Summary: Planning showing a -0 Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2174 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2174 showing -0 There is no such thing as -0 - but see attached. This happened after I edited the auto-filled amount. -- 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 1

[Bug 9409] New: koha-create --request-db should be able to accept a dbhost option
by bugzilla-daemon＠bugs.koha-community.org 12 Apr '13

12 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9409 Bug ID: 9409 Summary: koha-create --request-db should be able to accept a dbhost option Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: gmcharlt(a)gmail.com Reporter: ibeardslee(a)gmail.com koha-create --request-db should be able to accept a dbhost option and write that to koha-conf.xml When installing koha via the debian packages with the database on a separate host, as per http://wiki.koha-community.org/wiki/Install_Koha_3.6_on_Debian_squeeze_usin…, it is suggested that you run .. koha-create --request-db mylibrary This creates a text file with the appropriate details to use to create the mysql database, it also writes the database name, user and password into the /etc/koha/sites/mylibrary/koha-conf.xml file. But this process leaves the <hostname> unpopulated, essentially defaulting to 'localhost'. That config option has to be manually entered for a remote database host. Ideally one should be able to use .. koha-create --request-db mylibrary --dbhost databaseserver koha-create should also return details on where to change the hostname of the database server (whether the --dbhost option is used or not). -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 8844] New: UNIMARC_sync_date_created_with_marc_biblio.pl creates a modification log
by bugzilla-daemon＠bugs.koha-community.org 12 Apr '13

12 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8844 Priority: P5 - low Change sponsored?: --- Bug ID: 8844 Assignee: gmcharlt(a)gmail.com Summary: UNIMARC_sync_date_created_with_marc_biblio.pl creates a modification log Severity: normal Classification: Unclassified OS: All Reporter: fridolyn.somers(a)biblibre.com Hardware: All Status: NEW Version: master Component: Command-line Utilities Product: Koha When using UNIMARC_sync_date_created_with_marc_biblio.pl script with CataloguingLog on, you get a modification log on all catalog. Script should not call ModBiblio() when dates are already synchronized. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 9185] New: Duplicate barcode check broken on order receive
by bugzilla-daemon＠bugs.koha-community.org 12 Apr '13

12 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9185 Bug ID: 9185 Summary: Duplicate barcode check broken on order receive Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de Settings: AcqCreateItem = on receive UniqueItemFields = barcode 1) Create a new order with one or more order lines 2) Close basket 3) Create a new invoice/shipment 4) Receive one item, use existing barcode Problem: - on saving, no warning appears - item creation silently fails Log: ... [Sat Dec 01 23:11:05 2012] [error] [client 127.0.0.1] [Sat Dec 1 23:11:05 2012] finishreceive.pl: Indicator in 952 is empty at /home/katrin/kohaclone/C4/Biblio.pm line 2285., referer: http://localhost:8080/cgi-bin/koha/acqui/orderreceive.pl?ordernumber=25&inv… [Sat Dec 01 23:11:05 2012] [error] [client 127.0.0.1] [Sat Dec 1 23:11:05 2012] finishreceive.pl: DBD::mysql::st execute failed: Duplicate entry '3' for key 'itembarcodeidx' at /home/katrin/kohaclone/C4/Items.pm line 2105., referer: http://localhost:8080/cgi-bin/koha/acqui/orderreceive.pl?ordernumber=25&inv… [Sat Dec 01 23:11:05 2012] [error] [client 127.0.0.1] [Sat Dec 1 23:11:05 2012] finishreceive.pl: DBD::mysql::st execute failed: Column 'itemnumber' cannot be null at /home/katrin/kohaclone/C4/Acquisition.pm line 1094., referer: http://localhost:8080/cgi-bin/koha/acqui/orderreceive.pl?ordernumber=25&inv… ... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 9534] New: No way to get back to bib detail from edit record screen
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '13

11 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9534 Bug ID: 9534 Summary: No way to get back to bib detail from edit record screen Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz CC: m.de.rooy(a)rijksmuseum.nl If we are advising our librarians to not use the "back" button (which many do), there needs to be a way to get back to a bib detail view from the "edit record" screen. Without using the browser back button, the only way to do it currently is to search for the item again and click through from the results. -- You are receiving this mail because: You are watching all bug changes.

1 14