http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15521 Bug ID: 15521 Summary: Make circulation rules backend more granular Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: jweaver@bywatersolutions.com Reporter: jweaver@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, nicole@bywatersolutions.com To allow for more flexible specification of policy, a new table structure will be created. Instead of a single row per branchcode/categorycode/itemtype with columns for each policy value, we’ll have a row for each rule. This row would contain the relevant branchcode/categorycode/itemtype and the name and contents of the rule. The first iteration of this will rewrite GetIssuingRule to fetch all of these rules behind the scenes and return all of the rules for a given situation. The second iteration will identify all code calling the subroutine that fetches circulation rules, and instead of calling GetIssuingRule will fetch only the circulation rules it needs. Once this is complete, the subroutine GetIssuingRule will be removed altogether. To migrate data to this new system, we will create a row for each column of each row of the current schema. That is, each row in issuingrules will become ~20 rows in the new table (for loanlength, fine, etc.). This is less than ideal, but we will develop a new frontend to make this structure more manageable. (See http://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backend_... for more information.) -- You are receiving this mail because: You are watching all bug changes.