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

[Bug 4887] New: "Default value" option missing for Authority records
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '13

17 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4887 Summary: "Default value" option missing for Authority records Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: s.bolelli(a)libercoop.it QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 In the Authorities frameworks (Administration, Authority types) managing the subfield definitions is not possible to set a "default value" as for subfield definition of the MARC Bibliographic framework (Administration, MARC Bibliographic framework). It would be useful to have the option to specify a default value that is the same for every authority record -- 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 8757] New: Longer size text for authorised values "lib"
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '13

17 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8757 Priority: P5 - low Change sponsored?: --- Bug ID: 8757 Assignee: adrien.saurat(a)biblibre.com Summary: Longer size text for authorised values "lib" Severity: enhancement Classification: Unclassified OS: All Reporter: adrien.saurat(a)biblibre.com Hardware: All Status: ASSIGNED Version: master Component: Database Product: Koha Authorised Values have many uses, and, among others things, store in SUGGEST the potential "reasons" (then stored in the "suggestions" table) for which a suggestion can be refused. To give better informations to borrowers, some librairies would like to see longer "lib_opac" fields (the "lib" field should follow the movement, of course). Knowing the many uses of AV, and the fact that some languages may need more words than others ton convey a message, the length of these lib fields could be made longer (maybe 200 or 250 chars). -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 6281] New: Bug in LCC sort routine
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '13

17 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6281 Bug #: 6281 Summary: Bug in LCC sort routine Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: PC OS/Version: Windows Status: NEW Severity: normal Priority: P5 Component: Staff Client AssignedTo: paul.poulain(a)biblibre.com ReportedBy: flanagan(a)ucar.edu QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com While doing some work in the Inventory Tool, I notice that Koha is ordering things strangely. It seems to be trying to order things, albeit unsuccessful, according to Dewey rules. I have my DefaultClassificationSource set to Library of Congress. I'm not sure what the problem is, but it's doing things like putting QC145.45 .H4 D65 1998 before QC145 .A57 V.12 1980 and QC995 .E29 1997 before QC100 .U57 NO. 555 1986 And when I give it a range between, say, QC150 and QC 250, it gives me QC2 and QC 20 as well. Galen: "Fortunately, it will be easy for me to fix, as there is another open-source LCC sort routine that we can use as a replacement, it just needs to be wired in." -- 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 28

[Bug 8884] New: opacheader is not in the header on CCSR
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '13

16 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8884 Priority: P5 - low Change sponsored?: --- Bug ID: 8884 Assignee: oleonard(a)myacpl.org Summary: opacheader is not in the header on CCSR Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: OPAC Product: Koha Created attachment 12720 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=12720&action=edit opacheader to the right of search In CCSR the opacheader preference isn't really in the header it's to the right of the search box (see attached). I'm okay with a customizable region over there, but we should have a new preference for that and header should be above the search box as it implies -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 7240] New: Cleaning up import tables and action_log
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '13

16 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7240 Bug #: 7240 Summary: Cleaning up import tables and action_log Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities AssignedTo: gmcharlt(a)gmail.com ReportedBy: m.de.rooy(a)rijksmuseum.nl QAContact: ian.walls(a)bywatersolutions.com I already asked on dev list: > Is anyone of you using code to periodically purge records from > import_records, import_biblios, import_batches and/or action_logs ? > > If so, would it be an idea to include such code into > cleanup_database.pl in misc/cronjobs ? Response of Paul on dev list: +1 Sounds a very good idea. We have already made a dirty mysql "truncate xxx" on some setups IIRC. Would be better to have it in cleanup_database. I also agree it should be driven by a parameter, like the number in days to keep/clean. Something like cleanup_database --import 90 --action_logs 180 (90 days for import_* tables and 180 for action logs in this example) And if no parameter are given, either do nothing or remove after a default duration (30 for import ? 90 for action_logs ?) Will be sending a proposed patch. -- 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 13

[Bug 6793] New: imported and cleaned basket should be regularly deleted
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '13

16 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6793 Bug #: 6793 Summary: imported and cleaned basket should be regularly deleted Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: dev_patches(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org imported baskets should be deleted on a regular base. -- 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 4

[Bug 7110] New: Renewal messages still displays in OPAC if OpacRenewalAllowed is disabled.
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '13

16 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7110 Bug #: 7110 Summary: Renewal messages still displays in OPAC if OpacRenewalAllowed is disabled. Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: thatcher.rea(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org When OpacRenewalAllowed is set to "Don't Allow," Patron messages in the OPAC regarding renewals should probably not be displayed. (ie, "Since you have more than XXX.XX in fines, you cannot renew your books online. Please pay your fines if you wish to renew your books.") :T -- 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 32

[Bug 6763] New: sorting for funds
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '13

15 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6763 Bug #: 6763 Summary: sorting for funds Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Are the funds displaying in any particular order? Both on the Acquisitions page and on the New Order screen, the funds don't seem to be in any order. Alphabetical would be helpful. -- 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 7438] New: After attaching an item, clicking Cataloging breadcrumb results in 404 Error
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '13

15 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7438 Bug #: 7438 Summary: After attaching an item, clicking Cataloging breadcrumb results in 404 Error Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: hbraum(a)nekls.org QAContact: ian.walls(a)bywatersolutions.com When you click on the Cataloging breadcrumb after using the attach an item action, the system gives a 404 error. Steps to recreate: 1) Pull up any bib record. Go to Edit--> Attach an Item. Type in/scan a barcode of an item already in the catalog and click OK. 2) Click on the cataloging breadcrumb. See this screenshot: http://screencast.com/t/6TA7j16DUh 3) 404 error occurs. [Link is cgi-bin/koha/cataloging/addbooks.pl] Expected behavior: Click on the cataloging breadcrumb and it resolves to cgi-bin/koha/cataloguing/addbooks.pl -- 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 1

[Bug 5764] New: not for loan message in staff client repeated
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '13

15 Jul '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5764 Summary: not for loan message in staff client repeated Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When you're in the staff client if an item has a not for loan reason of 'not for loan' you see "Not for Loan (Not for Loan)" in the status. In the OPAC you just see the reason or the value, can we do that in the staff client? -- 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