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

[Bug 6595] New: Add German translation for purchase suggestion mails
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6595 Bug #: 6595 Summary: Add German translation for purchase suggestion mails Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Translate purchase suggestion mails in sample_notices.sql -- 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 10

[Bug 5568] New: Upgrade Amazon module to support Product Advertising API
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '12

02 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5568 Summary: Upgrade Amazon module to support Product Advertising API Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: jeremy(a)bicha.net QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Amazon reviews no longer display in OPAC because Amazon has changed the API again. More information can be found in the documentation: http://aws.amazon.com/archives/Product%20Advertising%20API === Dear Developer, On November 8, 2010 the Reviews response group of the Product Advertising API will no longer return customer reviews content and instead will return a link to customer reviews content hosted on Amazon.com. You will be able to display customer reviews on your site using that link. Please refer to the Product Advertising API Developer guide found here for more details. The Reviews response group will continue to function as before until November 8 and the new link to customer reviews is available to you now through the Product Advertising API as well. We are introducing efficiency guidelines for high volume users related to API usage. These guidelines are designed to promote efficient use of the API while providing the most effective advertising functionality and feature-set for application developers like you. Starting October 15 all usage will be subject to the efficiency guidelines. In addition, due to low usage, we plan to deprecate a subset of API operations and response groups. Please refer to the "Efficiency Guidelines" and "API Changes" sections below for details on the efficiency guidelines and API operations/response groups slated for deprecation. The efficiency guidelines will be phased in over a period of three months, starting July 15, and by October 15 all usage will be subject to these guidelines. The Product Advertising API Team. Efficiency Guidelines The purpose of the Product Advertising API is to advertise Amazon Products and thereby enable Associates to make money by creating Amazon advertisements and sending traffic back to Amazon. A small number of users are requesting very large amounts of product data while generating a very small amount of product sales. The Product Advertising API efficiency guidelines are designed to promote efficient use of the API. Each account used to access the Product Advertising API will be allowed an initial usage limit of 2,000 requests per hour. Each account will receive an additional 500 requests per hour (up to a maximum of 25,000 requests per hour) for every $1 of shipped item revenue driven per hour in a trailing 30-day period. Usage thresholds are recalculated daily based on revenue performance. To ensure that each account qualifies for the additional threshold increase, the URLs served by the Product Advertising API must be used when linking back to Amazon and the Associate tags used must belong to the account owner. API Changes Due to low usage, the Product Advertising API operations and response groups listed below will not be supported after October 15, 2010: Operations: CustomerContentLookup, CustomerContentSearch, Help, ListLookup, ListSearch, TagLookup, TransactionLookup, VehiclePartLookup, VehiclePartSearch, VehicleSearch. Response Group: ListmaniaLists, MerchantItemAttributes, PromotionDetails, Subjects, Tags, TagsSummary, VariationMinimum Additionally, due to low usage, we will be discontinuing Multiple Operation Requests and the TextStream search parameter. === -- 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 6907] New: remove unused 'borrowers.checkhist' column
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '12

01 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6907 Bug #: 6907 Summary: remove unused 'borrowers.checkhist' column Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: mtj(a)kohaaloha.com QAContact: koha-bugs(a)lists.koha-community.org remove unused 'borrowers.checkhist' column, in files... ./koha-tmpl/intranet-tmpl/prog/en/columns.def ./koha-tmpl/intranet-tmpl/prog/fr-FR/columns.def -- 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 5889] New: Allow message names to be translatable
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '12

01 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5889 Bug #: 5889 Summary: Allow message names to be translatable Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: julian.maurice(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Actually, message names are not translatable. Will submit a patch that makes it possible. -- 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 16

[Bug 5646] New: translated message names on sql level break messaging
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '12

01 Apr '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5646 Summary: translated message names on sql level break messaging Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 If you tranlate the message names in the installer sql files your messages will stop working, because the code relies on those have a specific value. - advance_notices.pl - C4/Members/Messaging.pm - C4/Form/MessagingPreferences.pm ... In C4/Members/Messaging.pm I found following lines: 47 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { borrowernumber => $borrower->{'borrowernumber'}, 48 message_name => 'DUE' } ); 50 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { categorycode => 'LIBRARY', 51 message_name => 'DUE' } ); We don't have DUE as a message name in the en file. Bug? Patch will undo my translation and other people's translations of those values. This means message names in borrower category and borrower account are not translatable at the moment. I think we need to change the templates to make them translatable? -- 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 16

[Bug 7090] New: Add "AllowItemsOnHandCheckout" syspref to allow issue to the patron regardless of hold status
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '12

28 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7090 Bug #: 7090 Summary: Add "AllowItemsOnHandCheckout" syspref to allow issue to the patron regardless of hold status Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Self checkout AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: srdjan(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org an item scanned at a self check station connected to Koha over SIP2 should issue regardless of whether there is a hold on the item. If the patron has the book in hand, they should be allowed to check it out; otherwise, what's to stop them from just taking it? This also prevents patrons from self-checking out holds that are waiting for THEM. Work To Be Done: - Add new system preference that asks whether self-check blocks checkout if the material in hand is on hold for someone else - Controls checkouts using Koha’s SCO - Controls checkouts over SIP2 How to test: - Set preference to allow checkouts of items in hand - Checkout a book with a hold on it for another via SIP. Checkout should proceed, hold should still exist - Checkout a book with a hold on it for another via SCO. Checkout should proceed, hold should still exist - Check out a book with a hold on it for yourself via SIP. Checkout should proceed, hold should be marked filled. - Check out a book with a hold on it for yourself via SCO. Checkout should proceed, hold should be marked filled. - Set preference to not allow checkouts of items in hand if hold is on them - Checkout a book with a hold on it for another via SIP. Checkout should not proceed, hold should still exist - Checkout a book with a hold on it for another via SCO. Checkout should not proceed, hold should still exist - Check out a book with a hold on it for yourself via SIP. Checkout should proceed, hold should be marked filled. - Check out a book with a hold on it for yourself via SCO. Checkout should proceed, hold should be marked filled. -- 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 6199] New: Allow bulkmarcimport to blank duplicate barcodes rather than skipping items
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '12

28 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6199 Bug #: 6199 Summary: Allow bulkmarcimport to blank duplicate barcodes rather than skipping items Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org If bulkmarcimport.pl sees a duplicate barcode, it throws away the whole item. The forthcoming patch allows it to optionally blank out the barcode of any duplicates found. This is useful when migrating from software that may have created duplicates. -- 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 34

[Bug 5354] New: Partial duplication of a subscription
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '12

28 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5354 Summary: Partial duplication of a subscription Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Partial_duplicatin g_serials_RFC OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Deadline: 2011-05-01 A syspref will be added that contains the list of fields to duplicate when duplicating a subscription. The library will be able to define that, for example, the internal note should not be duplicated -- 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 23

[Bug 6853] New: branch set wrong in fast add
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '12

27 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6853 Bug #: 6853 Summary: branch set wrong in fast add Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: critical 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 We discovered that when you create a Fast Add/Temp record from Cataloging > New Record > Fast Add the Set Library defaults to Atchison (the first branchcode in the table), rather than the Set Library for that session. When you create a Fast Add/Temp record for Circulation, the Set Library defaults correctly. When you create any other kind of framework record from Cataloging, the Set Library defaults correctly. Looks like addbiblio.pl was modified to take the branch in from the circulation page (according to the new Fast Add at barcode scan dev we reimplemented from Harley), but that parameter is absent if you come at Fast Add from Circulation -> Fast Add or Cataloging. I think this can be fixed with a simple "default" value set on these lines: addbiblio.pl line 862 additems.pl line 592 -- 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 4903] New: OAI doesn't work out of the box - XSL path
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '12

23 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4903 Summary: OAI doesn't work out of the box - XSL path Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Z39.50 / SRU / OpenSearch Servers AssignedTo: gmcharlt(a)gmail.com ReportedBy: tomascohen(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 In opac/oai.pl, the /koha-tmpl/intranet-tmpl/prog/en/xslt/ path is not available in a normal install: OAI harvesting fails and koha-opac-error.log says: "oai.pl: Could not create file parser context for file "/usr/share/koha_ffyh/intranet/cgi-bin/koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2OAIDC.xsl": No such file or directory" I'm not sure this xsl should be on intranet dir thou. To+ -- 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 14