On Wed, Dec 10, 2008 at 10:49 AM, BWS Johnson <span dir="ltr"><<a href="mailto:mhelman@illinoisalumni.org">mhelman@illinoisalumni.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
Salvete!<div class="Ih2E3d"><br>
>That report has been discussed before and was purposefully commented out in 3.0 (I argue should have <br>
>been deleted) becuase it is not reliable in a multi-branch situation. At present, the branch where the <br>
>transaction took place is not logged, so you cannot possibly create a report to extract that information. <br>
><br>
>Developers are fairly aware of this problem and are working to totally overhaul fines data structure. <br>
<br></div>
I don't mean to be abrasive here, but will that overhaul include a solution that is palatable to both single branch Libraries and multi branch? </div></blockquote><div><br>Yes, in particular since the current implementation is neither. A Koha user with a single branch still doesn't want their system to become unreliable just because they add a second branch. <br>
<br>But fines in Koha has enough problematic design flaws that it requires overhaul even for single branch setups. The current model is not reliable, atomic, maintainable, extensible, documented, secure or auditable. The overhaul offers most if not all those characteristics. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>I'd rather not see things tilt towards larger institutions in terms of deleting functions that used to exist.</div>
</blockquote><div><br>I'd rather not provide institutions of <b>any</b> size with functions that are erroneous, unreliable or fundamentally unsound. I am against preserving features that happen to work only in small or single branch setups (unless they are wrapped in the SingleBranch syspref). As a different example, inefficient queries that "work fine" on 4,000 records and crash systems on 100,000 are not the kind of well-designed features worth preserving. Leaving those kinds of landmines for users to step on makes Koha (or Unicorn, or any product) look amateurish. <br>
<br>--Joe Atzberger<br></div></div>