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

[Bug 11005] New: Centralize the UseBranchTransferLimits-check under one function
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '14

26 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11005 Bug ID: 11005 Summary: Centralize the UseBranchTransferLimits-check under one function Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Currently the IsBranchTransferAllowed() doesn't take into account multiple different global preferences and the check for IsBranchTransferAllowed() is really messy with multiple if-else statements. Move these global parameter checks to the core IsBranchTransferAllowed()-function to make using the function clearer. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 9703] New: Add optional parameter "as_string" to GetRecordValue subroutine
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '14

26 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9703 Bug ID: 9703 Summary: Add optional parameter "as_string" to GetRecordValue subroutine Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au Currently, the GetRecordValue subroutine returns an array of hashes, which must be looped through to retrieve results. On the template, you write the following code [% FOREACH subtitle %][% subfield %][% END %]. The problem with this is when you're trying to use the Keyword to MARC Mapping to over-write a field in the template that is already written as a single variable (e.g. [% author %]). Of course, you can loop through the array of hashes on the Perl side and pass a string to the template (i.e. opac-detail.tt or detail.tt). However, you're going to have to reproduce this iterator code every time you want to use GetRecordValue to produce a string. So, I figured that it made sense to add an optional parameter to the sub to trigger a condition so as to return a string of concatenated values rather than an array of hashes. --- Note: My ideal goal is to make it so that one can use the Keyword to MARC Mapping to specify any (or almost any) field on the detail pages. At the moment, I'm focusing on author, but I figure physical description will be another good one, as the template shows a bare minimum of the 3xx fields/subfields (in the incorrect order last I looked), --- Note, adding this optional parameter does NOT at all change the existing use of the GetRecordValue sub. The idea is hopefully to eliminate boilerplate by centralizing the "as string" code in this sub. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 10594] New: ability to annotate lists
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10594 Bug ID: 10594 Summary: ability to annotate lists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great if there was a way to annotate lists - kind of like a subject guide versus just a saved list of titles. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 8560] New: renewing lost items
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8560 Priority: P5 - low Change sponsored?: --- Bug ID: 8560 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: renewing lost items Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha I got this report from a library: When items age to long overdue lost, they assess a fee equivalent to the replacement price of the item. That makes sense. When those items are checked in, the fee is removed and the titles no longer display as checked out. The overdue does remain in the patron's history under fines. That also makes sense. However, if we renew one of those items, it assigns a new due date, but does not remove the fee or the long overdue lost designation. And, if we take payment on the item, it balances out the fee, reducing the amount due accordingly, but the title continues to display in the list of items out as long overdue lost. The result of this is that our staff members continue to mention these overdue items to the patron even after they've been taken care of. Other categories of lost - those that are manually set - remove the title from the list of items out. Renewing an item should also remove the fees and the long overdue designation. And paying for the item should remove it from items out and show it only in payment history. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 11330] New: Inconsistent field/subfield descriptions on MARC21 bibliographic frameworks
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11330 Bug ID: 11330 Summary: Inconsistent field/subfield descriptions on MARC21 bibliographic frameworks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: bgkriegel(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There are many inconsistencies on field/subfield descriptions on MARC21 bibliographic frameworks. That fact makes very hard to translate frameworks accurately using an automated procedure -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 9826] New: Missing fields in MARC21 authority framework
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9826 Bug ID: 9826 Summary: Missing fields in MARC21 authority framework Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: bgkriegel(a)gmail.com Reporter: bgkriegel(a)gmail.com CC: m.de.rooy(a)rijksmuseum.nl The default Authority frameworks for MARC21 are missing many tags. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 10488] New: New MARC21 authority tags and subfields should be propagated to non-default frameworks
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10488 Bug ID: 10488 Summary: New MARC21 authority tags and subfields should be propagated to non-default frameworks Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com CC: m.de.rooy(a)rijksmuseum.nl The patch for bug 9826 updated the default MARC21 authority frameworks with new tags and subfields, but new fields were added only to the default framework. Appropriate tags should be added to the non-default frameworks, e.g., PERSO_NAME, TOPIC_TERM, etc. A possible restructuring of authorities_normal_marc21.sql that might make it easier to maintain would be to have it populate each non-default framework by first making a copy of the default tags and subfields, then removing the tags that are not relevant to the authority type. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 7058] New: GetMemberDetails must die!
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7058 Bug #: 7058 Summary: GetMemberDetails must die! 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: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org The GetMemberDetails subroutine is insanely inefficient, and is used throughout Koha's code. In many cases, GetMember is more than sufficient (please see my rant on bug 5179). This report shall serve as the meta-report for all attempts to eliminate unnecessary calls get GetMemberDetails. Please file separate bug reports for specific instances, and list them as "blocking" this report. -- 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 5

[Bug 5179] New: GetMember and GetMemberDetails should be combined
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5179 Summary: GetMember and GetMemberDetails should be combined Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 In Members.pm, GetMember and GetMemberDetails do almost the same thing. This common behaviour should be combined so that changes to this kind of thing don't have to happen in multiple places. Aiming for 3.4. -- 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 7572] New: Add Clubs & Services Feature
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '14

23 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7572 Bug #: 7572 Summary: Add Clubs & Services Feature Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: kyle.m.hall(a)gmail.com QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com Add the clubs and services feature to Koha. This feature has been in production at the Crawford County Federated Library system for a number of years now. This features adds the ability to create clubs and services which patrons may be enrolled in. It is particularly useful for tracking summer reading programs, book clubs and other such clubs. It includes 2 built-in service archetypes: Bestsellers Club : Batch generate a holds list which shuffles the holds queue when new items matching a given title or author are catalogued. New Items Weekly Mailing Lists : Create custom mailing lists to alert subscribers to new items in your library. -- 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 58