June 2014 - Koha-bugs - lists.koha-community.org

[Bug 6068] New: New feature: capability to blanking subfields in BatchMod
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6068 Bug #: 6068 Summary: New feature: capability to blanking subfields in BatchMod Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: alex.arnaud(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org -- 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 17

[Bug 6688] New: capability to blanking subfields in BatchMod = disable form
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6688 Bug #: 6688 Summary: capability to blanking subfields in BatchMod = disable form Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org I would recommend an improvement that does what Owen suggests in #6068 and make it so that you can't select if the check box is checked -- 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 4944] New: Create separate noItemTypeImages preferences for OPAC and staff client
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4944 Summary: Create separate noItemTypeImages preferences for OPAC and staff client Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 At the moment the noItemTypeImages preference controls only the staff client. If my patch for Bug 4359 is approved it will affect both the staff client and the OPAC. Neither is ideal: There should be separate preferences for OPAC and 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

[Bug 6659] New: show opacnav on the log in page
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6659 Bug #: 6659 Summary: show opacnav on the log in page Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org It would be nice if the opacnav showed on the log in page in the OPAC (there's plenty of room there). -- 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 11251] New: Easier to customize OPACs for Multi-Library set ups
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11251 Bug ID: 11251 Summary: Easier to customize OPACs for Multi-Library set ups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great to have branch specific opac content. So opacmainuserblock, opacnav, opacnavright, opacnavbottom, opacheader, opaccredits could all be branch specific maybe using a different OPAC customization section in Administration instead of system preferences for these things. Of course one could argue that the entire OPAC preferences section could be broken out in to it's own Admin area - but I'll start small in my suggestion. Nicole -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 6253] New: Unified Patron Search subroutine
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6253 Bug #: 6253 Summary: Unified Patron Search subroutine Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Patrons AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 1707, 4340, 4945, 5266, 5595, 5730, 5945, 6127, 6217, 5676 Currently Koha uses two patron search routines, Search() and SearchMember(). SearchMember() is used in most places where a patron search is performed, and does not respect Extended Attributes, branchcode/categorycode limits or paging of results. It does, however, return exact matches for cardnumbers quickly, making it very desirable for Circulation. Search() is only used on members/member.pl to do an in-depth search of patrons. It makes use of SQLHelper.pm, which gives us support for Extended Attributes OR branchcode/categorycode limits (can't have both, it seems) and results paging. It's easy to add new fields from the borrowers table to search. Koha should really only have 1 search routine for searching for patrons. This routine should support Extended Attributes, branchcode/categorycode limits and pagination. Exact matches on cardnumber OR unique, searchable Extended Attributes should return immediately, without having to go through the full search routine. It should also be easy to configure which fields in the borrowers table are searchable. -- 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 52

[Bug 5730] New: Patron search, start_with search now searches within a string, not just the start
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5730 Summary: Patron search, start_with search now searches within a string, not just the start 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: 5575 Estimated Hours: 0.0 Search on start_with does like "% $var%" search (instead of " $var%") Plus a performancement enhancement for C4::SQLHelper -- 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 6511] New: Server-side paging of SQL queries
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6511 Bug #: 6511 Summary: Server-side paging of SQL queries Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org A generic server-side paging solution that could be applied to any SQL query we need would be a huge boon for the system. The query could be passed to a "pagify" subroutine, along with the starting and ending values, and the modified query returned. This would have the advantage of forcing sorts to apply BEFORE paging, so things like patron search results would be sorted globally, not just 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 1

[Bug 6532] New: way to move items in batches
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Bug #: 6532 Summary: way to move items in batches Classification: Unclassified 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: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com It would be nice if we could use the batch item modification to move a batch of items to another bib 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 1

[Bug 5613] New: search by 'on order'
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5613 Summary: search by 'on order' Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Would be great if there was a way to search for on order items (I know we can do this with CCL, I'm saying having it on the advanced search for patrons to see). -- 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