January 2012 - Koha-bugs - lists.koha-community.org

[Bug 6273] New: SIP2 Fee Paid and Fee Paid Response support
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '14

30 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6273 Bug #: 6273 Summary: SIP2 Fee Paid and Fee Paid Response support Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: SIP2 AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org Depends on: 5605 Enable Koha to accept, process and respond to SIP2 'Fee Paid' messages, as per the SIP2 protocol specification defined by 3M. See osdir.com/ml/attachments/pdfLa2ukLu5d7.pdf for full details. Processing 'Fee Paid' messages Koha shall parse the 'Fee Paid' message to extract the following mandatory information: • Transaction date • Fee type • Payment type • Currency • Amount • Institution ID • Patron identifier (barcode) Koha shall also be able to parse the following optional information: • terminal password • patron password • fee identifier (the ID of the fine to which the payment is applied) • Transaction ID (as assigned by the SIP client) Once the message is parsed, a payment line shall be added to Koha's accountlines table. This line shall include the borrowernumber, amount (as a negative), the transaction date, the payment type, and the account against which the payment is made. A note shall also be made to indicate that the payment was made from SIP client, rather than through the Koha staff client. Payments shall be accepted if the borrowernumber and account against which the payment is made are both valid. Otherwise, the payment shall not be accepted, and return an error message (see next section). Responding to 'Fee Paid' messages The Screen Message attribute of the 'Fee Paid Response' Message shall be used to display the details of any error that prevented the payment from being accepted. If the payment is accepted, this attribute shall contain a friendly “thank you for your payment” message. -- 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 5242] New: Simplify the import of members
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '14

29 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5242 Summary: Simplify the import of members Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: Patron Import AssignedTo: gmcharlt(a)gmail.com ReportedBy: pascale.nalon(a)ensmp.fr QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 For instance, to import members into Koha, you must a "clean", csv file. It's not always simple when your start file is an exel one. You must change several things in your file before importing it. In some application (like navicat), you can import directly an exel file, it's easier, and everybody can do it... -- 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

[Bug 6252] New: Patron import tool should let you set messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '14

29 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6252 Bug #: 6252 Summary: Patron import tool should let you set messaging preferences Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: cgi-bin/koha/tools/import_borrowers.pl OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When you do a patron import you can set the values for everything except the messaging preferences. The CSV should have a field for that and the form on the page should also offer the option of setting a blanket default for what's being imported. It's my understanding that this ability is there in the command line script, just not the GUI. -- 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 6255] New: patron import csv includes borrowernumber, but fails
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '14

29 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6255 Bug #: 6255 Summary: patron import csv includes borrowernumber, but fails Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org If you download the CSV file on the patron import page it has a column for borrowernumber, but if you try to import with that column you get a header error. Either we should allow it and use it as a match ... or maybe we should remove it if it's going to cause errors. -- 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 6795] New: Branch-specific OPAC preferences
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '14

29 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6795 Bug #: 6795 Summary: Branch-specific OPAC preferences Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: melia(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org Using the Contextual Preferences Engine, this moves the following preferences out of Sysprefs and down to the per-branch level. LibraryName OPACBaseURL opaccolorstylesheet opaccredits opacheader opaclayoutstylesheet OpacMainUserBlock OpacNav OPACNoResultsFound opacsmallimage opacstylesheet OPACUserCSS opacuserjs -- 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 7125] New: can't change tag in frameworks
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '14

28 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7125 Bug #: 7125 Summary: can't change tag in frameworks Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: major 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 see attached. When I go to edit a framework and change the tag number it looks like I'm able to, but when I hit save my changes aren't saved and no error message is generated. If this tag number isn't editable it shouldn't appear as if it is. -- 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 7327] New: Translation script doesn't like concatenated javascript strings
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '14

26 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7327 Bug #: 7327 Summary: Translation script doesn't like concatenated javascript strings Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: ian.walls(a)bywatersolutions.com I noticed that some alerts are (no longer?) translated. Example: cat-toolbar.inc is_confirmed= alert(_('There are [ '+ count +' ] item(s) attached to this record \n You must delete all items before deleting this record.')); This string doesn't get translated at all now. Also the \n is not good because it causes problems in Pootle. The only solution to make this translatable seems to be: is_confirmed= alert(_("There are [ ") + count + _(" ] item(s) attached to this record.") + "\n" + _("You must delete all items before deleting this record." By splitting it up into several part the sentence is very hard to translate. Also small pieces like "Delete" or "There are" are difficult, because you might want to use different words for it in your translation. It would be better if we can make the translation script deal with those strings and make it put in placeholders. So you would end up with: is_confirmed= alert(_('There are [ '+ count +' ] item(s) attached to this record \n You must delete all items before deleting this record.')); Output in po-file: There are [ %s ] item(s) attached to this record. ... I think this is a bug now, because those alerts don't get translated at all. Splitting them up is one solution, but fixing the translation scripts would be much better. -- 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 6

[Bug 5145] New: Call number in XSLT availability information
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5145 Summary: Call number in XSLT availability information Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2537 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2537 screenshot of result list and availability display The availability information in OPAC's XSLT result list shows the call number only for available items. If the item is checked out, no call number is shown. Our libraries are irritated by that and asked to always show the call number. Another of our libraries has the problem, that the call number shown in availability does not match all their items. To make it worse Koha normally shows the call number of the item that is not for loan in the result list. And the items are located at different locations in the building. So it would be a good enhancement if showing the call number in the result list would be optional and controlled by a sys pref. -- 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 7335] New: Allow custom parameters for sorting in sql reports
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7335 Bug #: 7335 Summary: Allow custom parameters for sorting in sql reports Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports AssignedTo: gmcharlt(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: ian.walls(a)bywatersolutions.com I was trying to find a solution to make it possible to select how a report is sorted before running it. Perhaps we could have a table sorter on tables generated by reports? I tried using the placeholders to provide a pull down with search options, but this didn't work. The replaced text is always in quotes, so the generated sql will not work: select concat(surname, ", ", firstname) as Name, cardnumber from borrowers order by 'cardnumber desc' -- 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 5181] New: Add js to convert units when units are changed on label or card template form
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5181 Summary: Add js to convert units when units are changed on label or card template form Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: cnighswonger(a)foundations.edu QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 This enhancement would add some js to automatically convert existing unit field values to the new unit selected from the Units drop-down. -- 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