https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34231 Bug ID: 34231 Summary: Allow different input formats for monetary values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs@lists.koha-community.org Reporter: katrin.fischer@bsz-bw.de QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, jonathan.druart+koha@gmail.com, michaela.sieber@kit.edu, tomascohen@gmail.com There are several bugs already about this, but after discussing with Joubu and Tomas today I think it deserves a fresh start. On bug 30718 Jonathan wrote:

"Show the user a readable date (as per altFormat), but return something totally different to the server."

It's actually an option we want to use for all our dates, that will reduce a lot the overhead in our controllers.

And we should use the same approach for dealing with monetary amounts in patrons/account and in the acquisition module. Using a client side solution we avoid having to touch the .pl scripts and it will also make it easier to work with the API. We'd have 2 input fields, one hidden, with the 'raw' data in the expected database format, and one visible input field for entering and displaying the 'formatted' data. When sending the data to the server, only the 'raw' data will be processed. To explain the need/use case: At the moment we don't have any validation on input fields in the acquisition module and that leads to input errors that can have dire consequences. 1,00 might be turned into 100 or 1000 or just end up as an empty field. We also only allow the 'US' format with decimal dot, but not the French/German format of decimal comma. This is also a usability issue as keyboard with German layout don't have a . in the number block, only a comma. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.