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

[Bug 6435] New: False "no items" in search results [intranet]
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '14

07 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6435 Bug #: 6435 Summary: False "no items" in search results [intranet] Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: eb(a)efdss.org QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com This applies only to things catalogued since upgrading to 3.4 The search results for these new records show no items in the hit list. But if you click on the title to bring up the normal view, the items are there, and are fully functional. The OPAC seems unaffected. The records created before we moved to 3.4 are also unaffected. -- 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 72

[Bug 5958] New: Availability Limit with icu
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '14

04 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5958 Bug #: 5958 Summary: Availability Limit with icu Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: ayousef(a)kwareict.com QAContact: koha-bugs(a)lists.koha-community.org Hi all As an extension of availability limit we noticed that the option of limit into currently available items is working only if we don't use icu but when using the icu this option is useless Plz, have you any idea about getting rid of this and what is the relationship between icu & Availability limit. thanks alot Abdou Yousuf. -- 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 3

[Bug 5827] New: Cloning Circ rules does not clone hold policies
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '14

18 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5827 Bug #: 5827 Summary: Cloning Circ rules does not clone hold policies Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com I set up circ rules for the main branch, including Hold Policies by Item type, and then cloned the NEKLS rules to another branch. The Hold policies by Item type were not cloned as expected. -- 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 6226] New: Returning a misrouted item twice causes transit to correct receiving library to disappear
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '14

18 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6226 Bug #: 6226 Summary: Returning a misrouted item twice causes transit to correct receiving library to disappear Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Hold requests AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Scenario: Library A transferred a book to Library B, but accidentally sent it to Library C What happens when Library C checks in the item? They get a reminder that there is a HOLD and to send the item to Library B. That’s good. (Return 1) However, if Library C returns that item a second time the transfer Goes Away. (Return 2) Also, if Library C goofs up and sends the book to Library D, when they return it, the transfer Goes Away (essentially the 2nd return that isn't the receiving branch). -- 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 6288] New: Check-in table could show reserve information
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '14

18 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6288 Bug #: 6288 Summary: Check-in table could show reserve information Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com When checking in items, it might be nice for the table at the bottom of the screen to show reserve and transit information on previously checked in items. This would be in case a staff member missed a confirmation box or forgot to print a slip, the information would be right there on the return screen. -- 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 5184] New: Upgrade to support jQuery 1.4.2
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '14

16 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5184 Summary: Upgrade to support jQuery 1.4.2 Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 We accidentally upgraded the jQuery to 1.4.2, from the 1.3.2 bundled with Koha. This broke the background processing code, in particular with the bulk modification functions. This ticket is to track the handling of workarounds and fixes dealing with this, in particular fixing the bits that are broken with newer jQuery versions. -- 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 43

[Bug 6331] New: Obsolete marc column in deleteditems
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '14

03 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6331 Bug #: 6331 Summary: Obsolete marc column in deleteditems Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: fridolyn.somers(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org There is a difference between "items" and "deleteditems" tables in "kohastructure.sql" : "deleteditems" has a field "marc" not existing in "items". This columns appears to be obsolete. -- 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 5031] New: CSV export profile form doesn't indicate that profile marcfields are required
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '13

13 Dec '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5031 Summary: CSV export profile form doesn't indicate that profile marcfields are required Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 If you try to save a CSV export profile without filling in profile marcfields, the page refreshes without saving any data and without showing any warnings. The form should at least indicate that it is a required field. A proper fix would display warnings if the profile was not saved because of missing data. -- 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 21

[Bug 5725] New: Batch modifications for Biblios
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '13

13 Dec '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5725 Summary: Batch modifications for Biblios Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Blocks: 5574 Estimated Hours: 0.0 New feature of batch biblio modifications, it allows you to select biblios from your basket and perform batch modifications on them -- 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 93

[Bug 5887] New: Add a link to batch modification of biblios from the Staff client
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '13

12 Dec '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5887 Bug #: 5887 Summary: Add a link to batch modification of biblios from the Staff client Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Staff Client AssignedTo: paul.poulain(a)biblibre.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 5725 -- 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